Hacker News Reader

Testing doesn't actually tell you anything. Were I designing this fan, I would only activate the attack payload if the fan was connected X number of times, or after some specific date in the future to defeat this kind of analysis.

I think you need to just tear one down and see what's connected. It should be trivial to identify if only the power connectors are hooked up, or if the data connectors are also hooked up.

View on HN

Unless I am missing something, even if the code has latent features, you should still be able to discover the "fan" in-fact has files and those files have code, which would be a red flag right?

My point is that instead of doing any investigative journalist work; "journalist" just decided to take to Twitter and proclaim the fan as hostile. The lack of facts and reason over emotion is my frustration. A recurring theme lately.

If I was trying to attack somebody through this route, I wouldn't just release all of them containing malware. Rather, I would target 2 or 3 journalists who I wanted to monitor and hope that they wouldn't be wise enough to consider the security implications. Most fans would check out as being okay, which would lessen the suspicion.

The only way you could definitively tell that these fans are compromised is to consequently check every fan out of the bunch.

Reply on news.ycombinator.com