News for hackers. Stuff that matters.
Re:Writing a Tiny x86 Bootloader by tr1ck5t3r on Wednesday December 28, 2016 @03:47AM (#13269324)
If you read this article, you'll understand just how easy it is to compromise so many computers. What I have seen infecting my own systems works on computers built in 2004 as well as new machines, so its exploiting the design and implementation of various international standards. The way it works, is the bios loads the malware irrespective of the boot drive order specified in the bios, and then it seems to rewrite the make and model of the hard drives and cd/dvd devices which you can only see by pausing the bios boot process on old machines. New pc's with SATA are too quick to even pause the part of the bios boot process which shows the hard ware make and model has been rewritten.

In ubuntu for example, whilst booting, ubuntu starts loading more of the malware from the metacache which suggest the hard drive cache may have been filled by the initial boot loader for the malware, again helping to hide the malware from detection. When booting different OS's, it works with XP, Ubuntu, Parted Magic, Kali, Tails and others. The OS's seem to actively hide the malware if you use a hex editor to scan the drive or infected files, so over time, some of that open source code has become compromised, and lets not forget the Dirty Cow exploit has been around since 2007 potentially making it possible to hack many different packages that make up the core Linux OS. It also seems to use SNMP to hack into managed switches, so whether this is getting into the Stuxnet/DuQu/DuQu2 territory, remains to be seen, but I would suggest it is, this then narrows it down to one country, because in maths its possible to calculate unknowns.

Remember, software always does what its told, unlike Humans and here in lies its weakness!

Re:Writing a Tiny x86 Bootloader by rasz_pl on Wednesday December 28, 2016 @10:05AM (#13270901)
>bios loads the malware irrespective of the boot drive order specified in the bios

>rewrite the make and model of the hard drives

ummm, no

[dead]
Re:Writing a Tiny x86 Bootloader by dang on Wednesday December 28, 2016 @11:34AM (#13271603)
If you're going to respond empathetically to someone who you think needs help, it's important to distinguish that from a personal attack. This comment doesn't do that—indeed it almost seems like you're invoking "psychiatric help" as ammunition in an argument, which would be bannable offence here.
Re:Writing a Tiny x86 Bootloader by duskwuff on Wednesday December 28, 2016 @02:12PM (#13272800)
It's almost a moot point. Given the underlying pathology, any attempt at all to discredit this type of delusion* will necessarily be seen as a part of the conspiracy, and hence as an attack. No amount of empathy will help.

But I certainly see what you mean; I was probably too quick to use that stock phrase. My intent here wasn't to argue, because I know that's impossible; it was more to identify the pathology to others. Would my comment have been fine without the last line? (I'm assuming that you were the one to flag it.)

*: and I mean that in the psychiatric sense, not as an insult

Re:Writing a Tiny x86 Bootloader by dang on Wednesday December 28, 2016 @03:40PM (#13273426)
I think you'd need both to drop the last line and reword the first line, because otherwise it's too easy to read as invoking a psychiatric category as snark.

There's probably a way of making this point that's fine, but it would require pre-emptively distinguishing your comment from the obvious misinterpretations. Which is tedious, but such is the way communication on a large forum needs to work, or else people just react and attack.

Re:Writing a Tiny x86 Bootloader by tr1ck5t3r on Wednesday December 28, 2016 @05:53AM (#13269754)
Except I have isolated the code and can reproduce it on demand, and have the photo's & video's as evidence so nice try.

However having just read this https://www.facebook.com/dragosr/posts/10151655183445588 I can see he has explained much of what I was witnessing on some systems as well.

Cant rule out a modern day version of one of these https://en.wikipedia.org/wiki/Phoebus_cartel considering the Windows MSR partition I have copies of which effectively stripes the Windows Partition as well.

Some people are desperate to keep this quiet though, so perhaps suggesting what you have is your way to introduce doubt into an argument which is after all a valid debating technique.

Re:Writing a Tiny x86 Bootloader by kbart on Wednesday December 28, 2016 @09:11AM (#13270527)
With all due respect, everything you said sounds like some kind of conspiracy theory. If you have isolated this case, write a blog post of how to reproduce it, post said photos & videos, so people might at least take their time to read it. I'm sure with all the experts here on HN somebody would provide an explanation. There are hell lots of processes happening at modern system boot time, if it does something you don't understand, it doesn't necessarily mean malware.

" The OS's seem to actively hide the malware if you use a hex editor to scan the drive or infected files, so over time, some of that open source code has become compromised"

This part, in particular, I find hard to believe. You can inspect open source system and compile everything yourself. Did you try to reproduce this behavior on minimal systems (i.e. BeagleBone) or QEMU?