Hacker News new | past | comments | ask | show | jobs | submit login

Operating system doesn't matter much when the malware is in BIOS or firmware code.



The 'malware' used a Windows misfeature that allows the BIOS to supply an executable that is run during startup. So the malware was in the firmware but only runs on Windows.


>Operating system doesn't matter much when the malware is in BIOS or firmware code.

Are you insinuating that was the case here? Source please, I'd be interested to read about that.


Here are three news articles on what happened:

http://arstechnica.com/information-technology/2015/08/lenovo...

http://www.techrepublic.com/article/windows-and-uefi-anti-th...

http://www.pcworld.com/article/2969365/security/lenovos-serv...

This should really only affect Windows systems as far as I know -- Windows is running an executable stored in the firmware at boot (a rather dubious feature, in my opinion, but it's intended as an anti-theft measure). Lenovo used that feature to try to circumvent removal of their crapware when someone reinstalls the OS.


For example SMM (system management mode) code is certainly loaded and executed under any operating system. You have to just trust the mainboard vendor.

https://en.wikipedia.org/wiki/System_Management_Mode

I'm not insinuating anything. All I know is that Lenovo broke our collective trust before, thinking they can get away with it.



It gets copied from the firmware and runs pre OS. But the executable only runs on windows from what I can tell, so its technically its cross platform but it wont run on both platforms.


The executable runs on Windows because Windows loads it and runs it. The executable doesn't force itself on Windows.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: