alt Hacker NewsUsing a consumer pc, risk wouldn't come from hardware hack implementations, it would be mostly software.
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.
> fake or infected Zoom binaries, Xcode binaries, etc.
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.