#SecChat $1 million guarantee 12 Scams of Christmas access to live fraud resolution agents Acquisition Alex Thurber Android antivirus Apple botnet Channel Partners cloud security Compliance Consumer counter identity theft credit card fraud and protection credit fraud alerts credit monitoring credit monitoring and resolution critical infrastructure Cyber Security Mom cyberbullying Cybercrime cybermom data breach data center data center security Data Protection Dave DeWalt DLP Email & Web Security embedded encryption Endpoint Protection enterprise facebook fake anti-virus software Family Safety Friday Security Highlights global threat intelligence google government Hacktivism how to talk to kids how to talk to teens identity fraud identity fraud scams identity protection identity protection $1 million guarantee identity protection fraud identity protection surveillance identity surveillance identity theft identity theft expert identity theft fraud identity theft protection identity theft protection product Identity thieves and cybercriminals intel iphone kids online behavior lost wallet protection malware McAfee McAfee Channel McAfee Family Protection McAfee Identity Protection McAfee Initiative to Fight Cybercrime McAfee Labs McAfee security products Mid-Market Mobile mobile malware mobile security monitor credit and personal information Network Security online personal data protection online safety Operation Aurora PCI personal identity theft fraud personal information loss personal information protection phishing privacy proactive identity protection proactive identity surveillance Public Sector restore credit and personal identity Risk and Compliance scam scams scareware security smartphones social media social networking social networks spam Stuxnet twitter vulnerability Web 2.0 work with victim restore identity
|
|
These days Malware authors are using cutting-edge and blended attack vectors for infection and spreading to avoid AV detection. These are often difficult to detect and clean.
We had seen MBR (Master Boot Record) viruses during the DOS age while rootkit use has been growing in recent years. In Jan 2008 McAfee came across a new threat, a blend of rootkit and MBR infection functionality named StealthMBR.
It gets installed on a victim’s machine when visiting malicious websites using browser exploits. During infection, it copies itself to the %temp% folder and starts as a service. This service overwrites the MBR with its own code and keeps a backup of original MBR in sector 62. It also overwrites sector 60 and 61 with rootkit loader code and rootkit components in the last sectors of the active partition. Later it restarts the system.

Picture showing infected MBR
Upon reboot, the infected MBR takes control of the system and gives control to the rootkit loader code. The loader code then patches the kernel to load and start its rootkit component.
The rootkit module hooks IRP_MJ_READ & IRP_MJ_WRITE in the IRP table of \\driver\Disk and protects itself from being modified. When the MBR is read, it returns the original MBR code from sector 62. This technique prevents many security tools from detecting and cleaning the malware.

Picture showing a part of rootkit loader module in sector 61
Given the nature of this threat (Rootkit & MBR infection), it needs a complex cleaning routine that can be difficult to achieve using regular AV techniques.
So far ‘Windows Recovery Console’ was the recommended solution to clean this threat. We at Avert Labs have developed a new cleaning method for this threat and incorporated it into DAT 5212 and above (VSE 8.5 and VSO having rootkit scanning option enabled as well). The cleaning involves unhooking the IRP_MJ_READ and IRP_MJ_WRITE entries of \\driver\Disk IRP table in memory and then restoring the original MBR from Sector 62 to Sector 0.

Picture showing MBR restored from sector 62 after cleaning.
Kudos to Harinath Ramachetty and Rachit Mathur for providing a solution for this nasty threat!!!
|
|
Hi there, I was infected, fixed by the mbrfix in Console, BUT, GMER still reports malicious code in sector 61, I know it is a dead code but is there a way to remove it too? Tx in advance.
Would you guys expect to see more of these kinds of rootkits? It seems like everyone has been focusing on kernel mode rootkits and the splashy VM rootkits, but things like this look more practical and easier to implement.
Very nice blog & absolutely informative
Submit your own comments / message for this post