Ramblings of an old Doc

 

“Nemesis” infect Windows computers before your security software loads. It’s a ‘rootkit’ – so it will infect your computer’s core components (hardware and software) while often disguising its actions.

“In this case, the Nemesis malware goes a step further and infects the hard drive boot record, which is the very first piece of code which executes when a computer is switched on. It's this code which launches an operating system such as Windows; such an infection is also known as a "bootkit" (boot + rootkit).”- John Lister

The only good news (insert sarcastic tone) here is that it’s currently being deployed against banks and financial firms…not home computers. Yet.

My guess? Won’t be long…and it may get coupled with ransomware…

Source:

https://www.infopackets.com/news/9737/new-bootkit-malware-sidesteps-security-software


Comments
on Dec 09, 2015

I was waiting for this one Doc. Saw the article but was unable to completely read it. Thanks for the heads up.

on Dec 09, 2015

preventive measures for home PC users?

on Dec 09, 2015

Thanks for the post.

The article you've linked has another article linked within it that is certainly worth the read as well.  The link is subtle, it's at the end of the next to last paragraph "Source:fireeye.com".  It's well worth the read as well and goes into more detail regarding the behavior and characteristics of the bootkit:

https://www.fireeye.com/blog/threat-research/2015/12/fin1-targets-boot-record.html

 

on Dec 09, 2015

Let's hope home users don't get targeted. There's always something... sigh.

on Dec 09, 2015

ElanaAhova

preventive measures for home PC users?

None as of yet...

on Dec 09, 2015

Looks like DBAN and OS re-install would be an option.  Perhaps the only one at present.

Such a purveyor of Holiday Cheer you are, Doc.

on Dec 10, 2015

surely things like those linux based cd/dvd scans can find it?

on Dec 10, 2015

Surely they don't...they implement during boot BEFORE you security software.

on Dec 10, 2015

Apparently a new addition to the NEMESIS malware suite called Bootrash, at present the only solution is to completely wipe the hard disk then reload the OS.

Hopefully the AV software companies like FireEye can get on top of this very quickly. Incidentally this is only one of a line of several previous Bootkit virus attacks, fortunately (or unfortunately) aimed mainly at financial institutions.

on Dec 10, 2015

DrJBHL

Surely they don't...they implement during boot BEFORE you security software.

Booting to DVD is implemented at BIOS level...before the HD boot record is accessed...so it 'should' precede a 'bootkit' ...

on Dec 10, 2015

i would have thought booting to linux via cd/dvd shouldn't be reading off the hdd/mounting them until after the os is loaded?

(obviously... whether the scans will then find the rootkit, etc depends on the signature/heuristics of the scans)

on Dec 10, 2015

Couple points:

- It doesn't work on disks using GPT. Which most newer systems should be using (it's required if you have UEFI and aren't running it in BIOS compatibility mode).

- I'd be surprised if booting to the repair console (via windows install disc) and running /fixmbr (assuming it still exists in newer versions of windows) didn't take care of it, since it rewrites the MBR.

- Booting from an optical disc will most definitely bypass it.

- It's only an extension of an APT ecosystem targeted at a specific bank. You won't be seeing it on your desktop, though of course someone else could come out with a bootkit malware targeted at consumers. They aren't a novel technique, and will still rely on some other malware, vulnerability, or social engineering to get themselves installed.

on Dec 11, 2015

... oddly my boot ssd uses mbr not gpt. no idea why (maybe i selected the wrong thing during install ). clean win10 install on it. (new machine with uefi)

also read that it doesn't matter performance wise due to small size (256 gb)... so not going to be bothered about that.

on Dec 11, 2015

Probably running in BIOS mode.

on Dec 11, 2015

wonder why... i did have problems (before installing anything) to get video to display anything at all until that fixed itself eventually somehow. (after a few reboots... only empty drives and win10 dvd connected)

.. guess i'll fiddle with that when i have to wipe everything and clean install... hopefully not for years!