Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Help with nasty Rootkit virus


  • This topic is locked This topic is locked
3 replies to this topic

#1 slamzee

slamzee

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:08:17 AM

Posted 18 January 2010 - 02:51 PM

Hello -

I spent most of Friday trying to get rid of a rootkit virus, and thought it was gone. But this morning my computer will not boot - the windows logo comes up, but then there is just an endless black screen and the hard drive purrs away - but i can't see anything.

I use ComboFix to remove the virus Friday after GMER it said the iastor.dll driver was infected. It was keeping browser redirects anytime i clicked on a google search result about the TDDSKiller.

So here is my current log from GMER - hopefully someone can point me in the right direction. This is after booting using the Windows 7 install disk (which shows up as drive X:) and runner gmer off a usb drive (G:)

GMER 1.0.15.15281 - http://www.gmer.net
Rootkit scan 2010-01-18 13:40:02
Windows 6.1.7600
Running: zerby.exe; Driver: X:\windows\TEMP\kgliqkod.sys


---- System - GMER 1.0.15 ----

INT 0x51 ? 90003058
INT 0x92 ? 90003CD8
INT 0xB0 ? 90037A58
INT 0xB2 ? 90003558

---- Devices - GMER 1.0.15 ----

Device \Driver\ACPI_HAL \Device\00000002 halmacpi.dll (Hardware Abstraction Layer DLL/Microsoft Corporation)

AttachedDevice \Driver\volmgr \Device\HarddiskVolume1 fvevol.sys (BitLocker Drive Encryption Driver/Microsoft Corporation)
AttachedDevice \Driver\volmgr \Device\HarddiskVolume2 fvevol.sys (BitLocker Drive Encryption Driver/Microsoft Corporation)
AttachedDevice \Driver\volmgr \Device\HarddiskVolume3 fvevol.sys (BitLocker Drive Encryption Driver/Microsoft Corporation)
AttachedDevice \Driver\volmgr \Device\HarddiskVolume4 fvevol.sys (BitLocker Drive Encryption Driver/Microsoft Corporation)
AttachedDevice \FileSystem\fastfat \Fat fltmgr.sys (Microsoft Filesystem Filter Manager/Microsoft Corporation)

INT 0x1F \SystemRoot\system32\halmacpi.dll (Hardware Abstraction Layer DLL/Microsoft Corporation) 8BA1EAF8
INT 0x37 \SystemRoot\system32\halmacpi.dll (Hardware Abstraction Layer DLL/Microsoft Corporation) 8BA1E104
INT 0xC1 \SystemRoot\system32\halmacpi.dll (Hardware Abstraction Layer DLL/Microsoft Corporation) 8BA1E3F4
INT 0xD1 \SystemRoot\system32\halmacpi.dll (Hardware Abstraction Layer DLL/Microsoft Corporation) 8BA06634
INT 0xD2 \SystemRoot\system32\halmacpi.dll (Hardware Abstraction Layer DLL/Microsoft Corporation) 8BA06898
INT 0xDF \SystemRoot\system32\halmacpi.dll (Hardware Abstraction Layer DLL/Microsoft Corporation) 8BA1E1DC
INT 0xE1 \SystemRoot\system32\halmacpi.dll (Hardware Abstraction Layer DLL/Microsoft Corporation) 8BA1E958
INT 0xE3 \SystemRoot\system32\halmacpi.dll (Hardware Abstraction Layer DLL/Microsoft Corporation) 8BA1E6F8
INT 0xFD \SystemRoot\system32\halmacpi.dll (Hardware Abstraction Layer DLL/Microsoft Corporation) 8BA1EF2C
INT 0xFE \SystemRoot\system32\halmacpi.dll (Hardware Abstraction Layer DLL/Microsoft Corporation) 8BA1F1A8

---- Registry - GMER 1.0.15 ----

Reg HKLM\SOFTWARE\Classes\CLSID\{093FF999-1EA0-4079-9525-9614C3504B74}\InProcServer32@ X:\Windows\System32\wshom.ocx
Reg HKLM\SOFTWARE\Classes\CLSID\{72C24DD5-D70A-438B-8A42-98424B88AFB8}\InProcServer32@ X:\Windows\System32\wshom.ocx
Reg HKLM\SOFTWARE\Classes\CLSID\{F935DC22-1CF0-11D0-ADB9-00C04FD58A0B}\InProcServer32@ X:\Windows\System32\wshom.ocx
Reg HKLM\SOFTWARE\Classes\CLSID\{F935DC26-1CF0-11D0-ADB9-00C04FD58A0B}\InProcServer32@ X:\Windows\System32\wshom.ocx
Reg HKLM\SOFTWARE\Classes\Interface\{0AB5A3D0-E5B6-11D0-ABF5-00A0C90FFFC0}\TypeLib@ {420B2830-E718-11CF-893D-00A0C9054228}
Reg HKLM\SOFTWARE\Classes\Interface\{2A0B9D10-4B87-11D3-A97A-00104B365C9F}\TypeLib@ {420B2830-E718-11CF-893D-00A0C9054228}
Reg HKLM\SOFTWARE\Classes\Interface\{53BAD8C1-E718-11CF-893D-00A0C9054228}\TypeLib@ {420B2830-E718-11CF-893D-00A0C9054228}
Reg HKLM\SOFTWARE\Classes\Interface\{C7C3F5A0-88A3-11D0-ABCB-00A0C90FFFC0}\TypeLib@ {420B2830-E718-11CF-893D-00A0C9054228}
Reg HKLM\SOFTWARE\Classes\Interface\{C7C3F5A1-88A3-11D0-ABCB-00A0C90FFFC0}\TypeLib@ {420B2830-E718-11CF-893D-00A0C9054228}
Reg HKLM\SOFTWARE\Classes\Interface\{C7C3F5A2-88A3-11D0-ABCB-00A0C90FFFC0}\TypeLib@ {420B2830-E718-11CF-893D-00A0C9054228}
Reg HKLM\SOFTWARE\Classes\Interface\{C7C3F5A3-88A3-11D0-ABCB-00A0C90FFFC0}\TypeLib@ {420B2830-E718-11CF-893D-00A0C9054228}
Reg HKLM\SOFTWARE\Classes\Interface\{C7C3F5A4-88A3-11D0-ABCB-00A0C90FFFC0}\TypeLib@ {420B2830-E718-11CF-893D-00A0C9054228}
Reg HKLM\SOFTWARE\Classes\Interface\{C7C3F5A5-88A3-11D0-ABCB-00A0C90FFFC0}\TypeLib@ {420B2830-E718-11CF-893D-00A0C9054228}
Reg HKLM\SOFTWARE\Classes\TypeLib\{F935DC20-1CF0-11D0-ADB9-00C04FD58A0B}\1.0\0\win32@ X:\Windows\System32\wshom.ocx
Reg HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion@CurrentType Multiprocessor Checked
Reg HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion@SystemRoot X:\Windows
Reg HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon@Userinit userinit.exe
Reg HKLM\SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName@ComputerName MINWINPC
Reg HKLM\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\GenDisk@ClassGUID {4D36E967-E325-11CE-BFC1-08002BE10318}
Reg HKLM\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\HID_DEVICE_SYSTEM_KEYBOARD@ClassGUID {4D36E96B-E325-11CE-BFC1-08002BE10318}
Reg HKLM\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\STORAGE#Volume@ClassGUID {71A27CDD-812A-11D0-BEC7-08002BE2092F}
Reg HKLM\SYSTEM\CurrentControlSet\Control\IDConfigDB@CurrentConfig 0
Reg HKLM\SYSTEM\CurrentControlSet\services\Dhcp@DependOnService nsi?tcpip?NetBT?
Reg HKLM\SYSTEM\CurrentControlSet\services\HidBatt@ImagePath \SystemRoot\system32\DRIVERS\HidBatt.sys
Reg HKLM\SYSTEM\CurrentControlSet\services\HidUsb@ImagePath \SystemRoot\system32\DRIVERS\hidusb.sys
Reg HKLM\SYSTEM\CurrentControlSet\services\IKEEXT@Start 3
Reg HKLM\SYSTEM\CurrentControlSet\services\kbdclass@ImagePath \SystemRoot\system32\DRIVERS\kbdclass.sys
Reg HKLM\SYSTEM\CurrentControlSet\services\kbdhid@ImagePath \SystemRoot\system32\DRIVERS\kbdhid.sys
Reg HKLM\SYSTEM\CurrentControlSet\services\lmhosts@DependOnService Afd?
Reg HKLM\SYSTEM\CurrentControlSet\services\lmhosts@ImagePath %SystemRoot%\System32\svchost.exe -k LocalServiceNetworkRestricted
Reg HKLM\SYSTEM\CurrentControlSet\services\lmhosts@Start 3
Reg HKLM\SYSTEM\CurrentControlSet\services\NetBT@Start 3
Reg HKLM\SYSTEM\CurrentControlSet\services\Tcpip@DisplayName @%SystemRoot%\system32\drivers\tcpip.sys,-10001
Reg HKLM\SYSTEM\CurrentControlSet\services\tdx@DependOnService tcpip?
Reg HKLM\SYSTEM\CurrentControlSet\services\tdx@DisplayName tdx
Reg HKLM\SYSTEM\CurrentControlSet\services\tdx@ImagePath %SystemRoot%\System32\drivers\tdx.sys
Reg HKLM\SYSTEM\CurrentControlSet\services\USBSTOR@ImagePath \SystemRoot\system32\DRIVERS\USBSTOR.SYS
Reg HKLM\SYSTEM\CurrentControlSet\services\Winmgmt@Start 2
Reg HKLM\SYSTEM\CurrentControlSet\services\WinSock2\Parameters\NameSpace_Catalog5@Num_Catalog_Entries 1
Reg HKLM\SYSTEM\CurrentControlSet\services\WinSock2\Parameters\NameSpace_Catalog5@Serial_Access_Num 1
Reg HKLM\SYSTEM\CurrentControlSet\services\WinSock2\Parameters\NameSpace_Catalog5\Catalog_Entries\000000000001@DisplayString Tcpip
Reg HKLM\SYSTEM\CurrentControlSet\services\WinSock2\Parameters\NameSpace_Catalog5\Catalog_Entries\000000000001@LibraryPath X:\Windows\system32\mswsock.dll
Reg HKLM\SYSTEM\CurrentControlSet\services\WinSock2\Parameters\Protocol_Catalog9@Next_Catalog_Entry_ID 1001
Reg HKLM\SYSTEM\CurrentControlSet\services\WinSock2\Parameters\Protocol_Catalog9@Num_Catalog_Entries 0
Reg HKLM\SYSTEM\CurrentControlSet\services\WinSock2\Parameters\Protocol_Catalog9@Serial_Access_Num 1
Reg HKLM\SYSTEM\Setup@SetupType 1

---- Kernel code sections - GMER 1.0.15 ----

.text ntkrnlpa.exe!KiDispatchInterrupt + 5A2 8BAA2F52 19 Bytes [E0, 0F, BA, F0, 07, 73, 09, ...] {LOOPNZ 0x11; MOV EDX, 0x97307f0; MOV CR4, EAX; OR AL, 0x80; MOV CR4, EAX; RET ; MOV ECX, CR3}
.text ntkrnlpa.exe!ZwSaveKeyEx + 13AD 8BA7E579 1 Byte [06]

---- EOF - GMER 1.0.15 ----

Edited by slamzee, 18 January 2010 - 02:53 PM.


BC AdBot (Login to Remove)

 


#2 slamzee

slamzee
  • Topic Starter

  • Members
  • 17 posts
  • OFFLINE
  •  
  • Local time:08:17 AM

Posted 18 January 2010 - 04:23 PM

Finally got to boot in safe mode after using the windows 7 install disk to do a repair.

Here is the new gmer log

Attached Files



#3 sempai

sempai

    noypi


  • Malware Response Team
  • 5,288 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:3 stars and a sun
  • Local time:08:17 PM

Posted 25 January 2010 - 08:03 AM

Hello and welcome to Bleeping Computer

We apologize for the delay in responding to your request for help. Here at Bleeping Computer we get overwhelmed at times, and we are trying our best to keep up. Please note that your topic was not intentionally overlooked. Our mission is to help everyone in need, but sometimes it takes just a little longer to get to every request for help. No one is ignored here.

If you have since resolved the original problem you were having, we would appreciate you letting us know. If not please perform the following steps below so we can have a look at the current condition of your machine.  

If you have not done so, include a clear description of the problems you're having, along with any steps you may have performed so far.

Upon completing the steps below another staff member will review and take the steps necessary with you to get your machine back in working order clean and free of malware.

If you have already posted a DDS log, please do so again, as your situation may have changed.
Use the 'Add Reply' and add the new log to this thread.


Thanks and again sorry for the delay.

We need to see some information about what is happening in your machine.  Please perform the following scan:
  • Download DDS by sUBs from one of the following links.  Save it to your desktop.
  • Double click on the DDS icon, allow it to run.
  • A small box will open, with an explanation about the tool.  No input is needed, the scan is running.
  • Notepad will open with the results.
  • Follow the instructions that pop up for posting the results.
  • Close the program window, and delete the program from your desktop.
Please note:  You may have to disable any script protection running if the scan fails to run.  After downloading the tool, disconnect from the internet and disable all antivirus protection.  Run the scan, enable your A/V and reconnect to the internet.  

Information on A/V control HERE

~Semp

btn_donate_LG.gif
You can help me continue the fight against malware by making a donation, Thank you.

If I am helping you and I didn't reply within 48 hours... Please send me a private message.
Topics that are not replied within 5 days will be close. Please don't PM asking for support, post on the Forums instead.

Member of UNITE (Unified Network of Instructors and Trained Eliminators) 


#4 schrauber

schrauber

    Mr.Mechanic


  • Malware Response Team
  • 24,794 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Munich,Germany
  • Local time:01:17 PM

Posted 31 January 2010 - 07:39 AM

Due to the lack of feedback, this topic is now closed.
If you need this topic reopened, please PM a staff member and we will reopen it for you (include the address of this thread in your request). This applies to the original topic starter only. Everyone else with similar problems, please start a new topic.
regards,
schrauber

Posted Image
Posted Image

If I've not posted back within 48 hrs., feel free to send a PM with your topic link. Thank you!

If I have helped you then please consider donating to continue the fight against malware Posted Image




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users