Rootkit-gen problem - help needed

Forums › Microsoft Windows › Rootkit-gen problem - help needed

falcott

29 posts

Geek

#54899 22-Dec-2009 20:18

Hi geeks,
on my wife's laptop, Avast has picked up the following rootkit:

File name C:\WINDOWS\System32\Drivers\jrikd.sys
Malware name Win32:Rootkit-gen [Rtk]

We've tried getting Avast to delete it, but it just pops back. Also, Spybot won't detect it.

Any suggestions on what it is and instructions for how to get rid of it?

Is there any chance that ESET Smart Security would get rid of it if I installed it?

Cheers!

1 | 2

BDFL - Memuneh
65598 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

#284698 22-Dec-2009 20:32

Have you tried http://free.antivirus.com? You can run it without having to uninstall you current AV software.

CYaBro

3233 posts

Uber Geek

Subscriber

#284744 23-Dec-2009 00:15

Turn off System Restore then boot into safe mode and run a scan.
Also try malwarebytes antimalware.

Ragnor

8035 posts

Uber Geek

Trusted

#284871 23-Dec-2009 17:00

I've had good success with Malware Bytes
http://www.malwarebytes.org/

askelon

647 posts

Ultimate Geek

Subscriber

#284876 23-Dec-2009 17:31

Try malwarebytes and combofix (http://www.bleepingcomputer.com/combofix/how-to-use-combofix)

kontonnz

137 posts

Master Geek

#284882 23-Dec-2009 17:58

personally I would reinstall the OS; once the system is compromised you can spend hrs trying to clean out the malware, where as a reinstall might take less time; but that all depends on your setup, and how you backup data etc (huzzah for 1tb external drives for backup storage)

oh yes I would also look at installing MS Security Essentials http://www.microsoft.com/Security_Essentials/ which does not test all that bad against all the other free av; (I like the UI as well)

falcott

29 posts

Geek

#284896 23-Dec-2009 19:27

Thanks for all the helpful advice! I'll start working my way through the suggestions

I've been using ESET on my computer for the last year or so, and haven't had any probs. Seems pretty good.

falcott

29 posts

Geek

#284911 23-Dec-2009 21:21

Okay:

I tried free.antivirus.com's HouseCall software, but it didn't detect anything.

Next I tried malwarebytes which did detect the rootkit in question. I deleted and rebooted. Avast promptly reported the rootkit again

I may have to take Mr Kontonnz' advice yet...

CYaBro

3233 posts

Uber Geek

Subscriber

#284933 23-Dec-2009 23:22

Did you disable system restore and run the scan in safe mode?

falcott

29 posts

Geek

#284935 23-Dec-2009 23:32

Yes, just have, and it seems we may have snuffed it

Thanks for your help!

Tarq57

156 posts

Master Geek

#285032 24-Dec-2009 18:05

What's the chance you could post the MBAM log, please?
Run a quick scan also (using MBAM) but not in safe mode. MBAM is designed to work best in normal mode. If it detects something that is locked by Windows in normal, it will ask for a reboot to complete removal.

falcott

29 posts

Geek

#285053 24-Dec-2009 22:12

Malwarebytes' Anti-Malware 1.42
Database version: 3414
Windows 5.1.2600 Service Pack 3
Internet Explorer 8.0.6001.18702

24/12/2009 9:57:24 p.m.
mbam-log-2009-12-24 (21-57-24).txt

Scan type: Quick Scan
Objects scanned: 109070
Time elapsed: 4 minute(s), 59 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 0

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)

~~~~~~~

Earlier, when I deleted the file using Malwarebytes and rebooted, perhaps Avast picked up the dying gasp. After Avast said it was there again, I allowed Avast to scan in safe mode. It picked up a trojan or 2, but not the rootkit. So unless it's hiding under a rock, it seems to be gone.

I'll keep you posted if the problem rears its head again any time soon!

Thanks everyone for your help

Tarq57

156 posts

Master Geek

#285056 24-Dec-2009 22:26

Loverly, but I was hoping for the earlier one that nabbed it, before it was later (apparently) re-created.
On the main MBAM GUI, click on the "logs" tab.
Shouldn't be hard to find.
The file name is rare, (C:\WINDOWS\System32\Drivers\jrikd.sys) and thus very suspicious.
I wouldn't trust that computer 100% until you know it's clean.

kontonnz

137 posts

Master Geek

#285066 24-Dec-2009 23:06

the problem with malware/rootkits is that they are extremely tenacious and overall can be a pain to be removed;
personally if a system has been infected with a rootkit I would rebuild, and with malware depending on type I would clean.

Tarq57

156 posts

Master Geek

#285068 24-Dec-2009 23:28

Some can be, for sure, but antirootkit technology has made pretty big steps in the past year or two, so it's not always the "death sentence" it was considered to be not so long ago.
A problem with this sort of malware is it can be difficult, without expert help, to know that the system is clean. This might involve posting in a dedicated removal forum, and using tools/fixes as directed by trained volunteers.
Given the choice I'd rather try to fix a computer affected by a rootkit, than some of the buggy file infectors around, such as Vitro/Virut, or Sality.

The fact that Avast re-detected this after MBAM detected and removed it is reason for concern. If Avast detected it in MBAM's quarantine, not so much of a worry. But if something is re-spawning it, that's a big concern, because it means the spawning agent is still there, hidden and undetected.

Ragnor

8035 posts

Uber Geek

Trusted

#285081 25-Dec-2009 00:53

falcott:

I allowed Avast to scan in safe mode. It picked up a trojan or 2, but not the rootkit. So unless it's hiding under a rock, it seems to be gone.

Those other trojans could easily have re-installed the rootkit.

1 | 2