Some XP Users Get BSOD After Patch Tuesday, Malware Blamed

Terry Olaes

I Used to be the [H] News Guy
2FA
Joined
Nov 27, 2006
Messages
4,646
Microsoft pulled the MS10-015 update out of circulation last week due to user complaints that the patch caused their XP build to BSOD. After investigation, MS said that the issue is due to the TDSS rootkit and issued a statement that users have to remove the malware before patching. Yeah, good luck with that.

Because TDSS uses crafty techniques to hide itself on the operating system, many antivirus programs have a hard time detecting it, said Roel Schouwenberg, a Kaspersky antivirus researcher. "The more I look into it, the more plausible it becomes that this is indeed the (main) issue behind the BSOD. MS10-015 is a kernel update with atapi.sys containing the extremely advanced TDSS kernel rootkit," he said via instant message. "Microsoft pulling the patch obviously says something about how widespread this thing is."
 
Is TDSS a commercially made rootkit like Sony's was or is it an independently made virus?
 
I'd love to know what this TDSS thing is; I just installed a machine last week from an MSDN .iso, with no extra software installed but the in-box drivers and all Windows updates...it's on a network by itself behind a firewall, and it had the same problem after Tuesdays updates...
 
I'd love to know what this TDSS thing is; I just installed a machine last week from an MSDN .iso, with no extra software installed but the in-box drivers and all Windows updates...it's on a network by itself behind a firewall, and it had the same problem after Tuesdays updates...

As the article states in the 2nd or 3rd graph:

On Friday, Microsoft offered a preliminary conclusion, saying that malicious software may be to blame. "Malware on the system can cause the behavior," wrote Microsoft spokesman Jerry Bryant on a company blog. "We are not yet ruling out other potential causes at this time and are still investigating."

MS has gone as far as going to customers houses and going through the logs to determine what is happening. Anyone who's ever worked on system issues can tell you that as you investigate, evidence can point to a root cause that is not, in fact, the root cause. Sometimes it's a different problem with a similar result.

All they're saying is that looking for certain strains of malware, and removing them may solve the problem.
 
I've seen the rootkit (which hooks into the primary controller driver, e.g. atapi.sys) cause BSODs/stop codes long before the patch came out. In fact, I've had 3 this month I've had to replace the controller driver file on (2 atapi, 1 iastor). While the rootkit certainly does cause problems, that it's been happening since before the patch and happening to fresh installs (as from above) indicates that something's not right with the patch on some systems.
 
I've seen it at work once already and I fear there will be more. McAfee detected it as Downloader-CFA, which is in the DATs since 2/9/10.
 
I actually saw a fix that replaced atapi.sys with the version from installation media. ATAPI.Sys is an old IDE driver left over from the NT days. I hope people don't start running out and just deleting it thinking they've solved the problem.

This could be another case of legacy components in an OS being hijacked by malware.
 
Had several machines in the shop this week with BSODs after installing MS10-015. All of them had the TDSS rootkit, all of them were fixed with a few simple short steps.

1) Boot off of a Windows XP CD, and go into the Recovery Console. NOT A REPAIR INSTALL.
2) CD into $NtUninstallKB977165$\spuninst (you should already be in C:\WINDOWS)
3) Run the following command: BATCH spuninst.txt
4) Run the following command: systemroot
5) Reboot normally, you should now be able to get into Windows.
6) Download and run TDSSKiller from Kaspersky Labs.

That should clean out the TDSS rootkit. You'll still want to do a full anti-malware pass on the machine (Combofix, MBAM, Super) as there's prolly other evil on the machine too.

Cobbled this together from a ton of other threads and fora, and it does the trick. Quick, too.
 
There are trillions of infections on XP, it's been on the market for quite some time. Good luck to Microsoft if they do find a solution to the issue. Even if they do though, the virus shouldn't remain on users systems either way and they should find a way to remove it. There are just so many exploits, back door infections, malware, spyware, trojans that affect XP though, as well as the rootkit they mention that only god knows what can be done about just one of the infections that affect XP screwing up a 'security update' patch. Even when XP first came out though there were already 1000's of infections that were rampant back then that could affect the Operating System. Used Linux for quite a long while back then anytime I wanted to do any type of web surfing or shopping on-line. XP never was all that secure of a system.
 
I agree. Dual boot with Linux. Do everything with Linux, and stuff you can't do in Linux, do in XP (such as gaming) That's a lot safer than having a ton of AV and AS programs.

Or upgrade to Windows 7.
 
Microsoft should just leave the patch out there and to make everyone upgrade from their old operating systems.
 
I agree. Dual boot with Linux. Do everything with Linux, and stuff you can't do in Linux, do in XP (such as gaming) That's a lot safer than having a ton of AV and AS programs.

Or upgrade to Windows 7.

:rolleyes:
 
i believe the stop code on this was a 0x07e stop code. i had a suspicion that the BSOD from that patch was storage driver related as i have seen virus repairs throw up 0x07b stops fairly commonly.

interesting stuff.
 
Are they saying that the rootkit already existed on the machine, or that it was distributed in the patch? The article isn't very clear.
 
The rootkit was already on the system pre-patch. The patch puts in a new ATAPI.SYS, which breaks the rootkit and the system with it.
 
I had two rigs at my work go down with this....one a laptop, took the drive out and sure enough, it was "infected" (atapi.sys) when I scanned it from an external usb adaptor. The other rig I just did a clean install, it was faster than any fix since the particular machine mostly did access to an invoicing program on a server. Nothing to lose really except an hour to rebuild.

Nasty, I am glad I did not have even more at my work, out of 25+ rigs, only two got it.

Thanks for the easy fix above...filed!
 
Makes sense why the infection attacks the ATAPI system ,you can't toss a disk in to install anti-virus.
 
The rootkit maker has patched their rootkit so you can put MS10-015 now. Then again, I'm not sure why anyone would want to keep malware on their machines.
 
The rootkit maker has patched their rootkit so you can put MS10-015 now. Then again, I'm not sure why anyone would want to keep malware on their machines.

They enjoy helping spammers and people stealing bank account info.
 
Back
Top