Thus the attack surface is far greater.
For example, in MacOS it would be extremely hard to "sniff the display" as in this attack, unless you take obvious steps to authorize screen access.
To continue with your example, "display sniffing" could be done by infecting trusted software or software presented as trustworthy (fake or infected Zoom binaries, Xcode binaries, etc.) or injected through open source dependencies like npm packages.
Yes, you or I might be paranoid enough to check the checksum hash to make sure the open source code matches the build. But every time, for everything?
The less connected it is, the safer. The less software it runs, the safer.
There are so many hoops to go through to pull something like that off, it's basically impossible. It would be a "the great train robbery" kind of effort. I also don't think an npm package could alter an existing app or obtain screen access otherwise, unless you're running `sudo npm install` routinely.
Some form of phishing would be way more likely to succeed, luckily you can use your own brain to protect against those attacks.
Fake zoom updates: https://www.malwarebytes.com/blog/scams/2026/02/fake-zoom-me...
NPM supply chain attack targeting cryptowallets: https://www.paloaltonetworks.com/blog/cloud-security/npm-sup...
More software means more complexity means more pathways to losing.
Can you do it? Sure. I'm sure there are millions of dollars in private keys stored on internet connected laptops somewhere out there. But the best practices remain the same: as little internet as possible, as little software as possible.
But now you need to generate a public key to send to someone so you can receive coins. How are you sending that key to your friend? Are you going to read character by character and manually type up the string?
It's all tradeoffs.
Sounds kinda clunky.