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

Win32/Rootkit.Agent.ODG Trojan & Zlob lowsec directory?


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

#1 ajadagga

ajadagga

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:05:54 PM

Posted 29 August 2009 - 10:45 AM

Hi there. I am a class one numpty and decided to use p2p software to get a crack & keygen for sony vegas 9. I am now infected. I won't be doing that again. For your reference I use Windows XP SP3.

I first became aware of it when AVG alerted me to a malicious exploit when I opened IE and upon google searching, the links on googles page kept getting redirected to a number of ad-laden websites such as africa-international.com (DON'T CLICK). Before it does this it seems to redirect through a site named cclicker.com. However, it seems to work if I C&P the URL from the bottom of the google listing and paste into my url bar. I ran Spybot since AVG was useless, and it said I had a trojan, sdra64.exe, and some malware. I clicked to remove it and it said it had removed everything except a registry key which it was unable to do. Then spybot prompted me about some registry changes but i did not know what to do as i was unclear whether the changes were coming from spybot deleting the virus or the virus trying to so something. I allowed some and disallowed others in a confused haze. The next time I ran spybot it said the trojan had installed a directory, C:\WINDOWS\system32\lowsec\, which it could not elect, containing a number of innocuously-named .ds files.

At that point I got fed up with spybots and AVG's uselessness and downloaded a trial of Nod32. That seemed to find all my viruses and told me the name of the trojan, win32/rootkit.agent.odg. Spybot seemed to call it Win32.Zlob -something. Unfortunately nod32 could not remove the virus. To google! i said, and found a similar case on this very board, http://www.bleepingcomputer.com/forums/t/232185/win32rootkitagentodg-trojan/ .

I DLed MALWARE BYTES and here is the report.

Malwarebytes' Anti-Malware 1.40
Database version: 2712
Windows 5.1.2600 Service Pack 3

29/08/2009 15:40:40
mbam-log-2009-08-29 (15-40-40).txt

Scan type: Quick Scan
Objects scanned: 125102
Time elapsed: 15 minute(s), 52 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 6
Registry Values Infected: 1
Registry Data Items Infected: 5
Folders Infected: 1
Files Infected: 4

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\{19127ad2-394b-70f5-c650-b97867baa1f7} (Backdoor.Bot) -> Quarantined and deleted successfully.
HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\{43bf8cd1-c5d5-2230-7bb2-98f22c2b7dc6} (Backdoor.Bot) -> Quarantined and deleted successfully.
HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\{494e6cec-7483-a4ee-0938-895519a84bc7} (Backdoor.Bot) -> Quarantined and deleted successfully.
HKEY_USERS\S-1-5-18\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\{19127ad2-394b-70f5-c650-b97867baa1f7} (Backdoor.Bot) -> Quarantined and deleted successfully.
HKEY_USERS\S-1-5-18\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\{43bf8cd1-c5d5-2230-7bb2-98f22c2b7dc6} (Backdoor.Bot) -> Quarantined and deleted successfully.
HKEY_USERS\S-1-5-18\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\{494e6cec-7483-a4ee-0938-895519a84bc7} (Backdoor.Bot) -> Quarantined and deleted successfully.

Registry Values Infected:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Network\UID (Malware.Trace) -> Quarantined and deleted successfully.

Registry Data Items Infected:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit (Trojan.FakeAlert) -> Data: c:\windows\system32\sdra64.exe -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit (Trojan.FakeAlert) -> Data: system32\sdra64.exe -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\AntiVirusDisableNotify (Disabled.SecurityCenter) -> Bad: (1) Good: (0) -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\FirewallDisableNotify (Disabled.SecurityCenter) -> Bad: (1) Good: (0) -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit (Hijack.Userinit) -> Bad: (C:\WINDOWS\system32\userinit.exe,C:\WINDOWS\system32\sdra64.exe) Good: (Userinit.exe) -> Quarantined and deleted successfully.

Folders Infected:
C:\WINDOWS\system32\lowsec (Stolen.data) -> Delete on reboot.

Files Infected:
C:\RECYCLER\S-1-5-21-4074481141-472197147-1327349290-1009\Dc177.exe (Trojan.Agent) -> Quarantined and deleted successfully.
C:\WINDOWS\system32\lowsec\local.ds (Stolen.data) -> Delete on reboot.
C:\WINDOWS\system32\lowsec\user.ds (Stolen.data) -> Delete on reboot.
C:\WINDOWS\system32\sdra64.exe (Trojan.FakeAlert) -> Delete on reboot.


When I rebooted the computer the virus was still there. So I followed the next xtep that user had taken and downloaded ROOTREPEAL. Here's the log from that.

ROOTREPEAL İ AD, 2007-2009
==================================================
Scan Start Time: 2009/08/29 16:12
Program Version: Version 1.3.5.0
Windows Version: Windows XP SP3
==================================================

Drivers
-------------------
Name: dump_atapi.sys
Image Path: C:\WINDOWS\System32\Drivers\dump_atapi.sys
Address: 0xAA096000 Size: 98304 File Visible: No Signed: -
Status: -

Name: dump_WMILIB.SYS
Image Path: C:\WINDOWS\System32\Drivers\dump_WMILIB.SYS
Address: 0xF7AD9000 Size: 8192 File Visible: No Signed: -
Status: -

Name: rootrepeal.sys
Image Path: C:\WINDOWS\system32\drivers\rootrepeal.sys
Address: 0xA8C45000 Size: 49152 File Visible: No Signed: -
Status: -

Name: srescan.sys
Image Path: srescan.sys
Address: 0xF72C5000 Size: 81920 File Visible: No Signed: -
Status: -

Name: uhpcrvdn.sys
Image Path: C:\WINDOWS\system32\drivers\uhpcrvdn.sys
Address: 0xF6B24000 Size: 61440 File Visible: No Signed: -
Status: -

Hidden/Locked Files
-------------------
Path: C:\hiberfil.sys
Status: Locked to the Windows API!

Path: C:\WINDOWS\system32\kbiwkmnelkyvlm.dll
Status: Invisible to the Windows API!

Path: C:\WINDOWS\system32\kbiwkmoilrdopu.dll
Status: Invisible to the Windows API!

Path: C:\WINDOWS\system32\kbiwkmtpejdvjg.dat
Status: Invisible to the Windows API!

Path: C:\WINDOWS\system32\kbiwkmxxylnlic.dat
Status: Invisible to the Windows API!

Path: C:\WINDOWS\system32\drivers\kbiwkmdwyeoyaq.sys
Status: Invisible to the Windows API!

Path: c:\documents and settings\zoe temp\local settings\temp\~df98d2.tmp
Status: Allocation size mismatch (API: 16384, Raw: 0)

Path: c:\documents and settings\zoe temp\local settings\temp\~dfb4dc.tmp
Status: Allocation size mismatch (API: 24576, Raw: 0)

Path: c:\documents and settings\zoe temp\local settings\temp\~dfe1c3.tmp
Status: Allocation size mismatch (API: 16384, Raw: 0)

Path: C:\Documents and Settings\Zoe temp\Local Settings\Temporary Internet Files\Content.IE5\2RVC908E\stat_load[1].gif
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Zoe temp\Local Settings\Temporary Internet Files\Content.IE5\ES1SJCY1\icon13[1].gif
Status: Visible to the Windows API, but not on disk.

Path: d:\drecovery
Status: Allocation size mismatch (API: 0, Raw: 1432989106433949696)

Path: D:\cmdcons\diMk.sy_
Status: Invisible to the Windows API!

Path: D:\cmdcons\i8042prt.sM_
Status: Invisible to the Windows API!

Path: D:\cmdcons\KBDHU1IDLL
Status: Invisible to the Windows API!

Path: D:\cmdcons\KBDGR.JLL
Status: Invisible to the Windows API!

Path: D:\cmdcons\ohIi1394.sy_
Status: Invisible to the Windows API!

Path: D:\cmdcons\serialMsy_
Status: Invisible to the Windows API!

Path: d:\cmdcons\sparrow.sy_
Status: Size mismatch (API: 11098, Raw: 21673573206731610)

Path: D:\cmdcons\usbohcS.sy_
Status: Invisible to the Windows API!

Path: D:\cmdcons\vgaoemSfo_
Status: Invisible to the Windows API!

Path: D:\cmdcons\disk.sy_
Status: Visible to the Windows API, but not on disk.

Path: D:\cmdcons\i8042prt.sy_
Status: Visible to the Windows API, but not on disk.

Path: D:\cmdcons\KBDGR.DLL
Status: Visible to the Windows API, but not on disk.

Path: D:\cmdcons\KBDHU1.DLL
Status: Visible to the Windows API, but not on disk.

Path: D:\cmdcons\ohci1394.sy_
Status: Visible to the Windows API, but not on disk.

Path: D:\cmdcons\serial.sy_
Status: Visible to the Windows API, but not on disk.

Path: D:\cmdcons\usbohci.sy_
Status: Visible to the Windows API, but not on disk.

Path: D:\cmdcons\vgaoem.fo_
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\Waٹning.bmp
Status: Invisible to the Windows API!

Path: D:\MiniNT\Warning.bmp
Status: Visible to the Windows API, but not on disk.

Path: d:\preload\all.mdf
Status: Allocation size mismatch (API: 8, Raw: 22236523160141832)

Path: D:\MiniNT\Fonts\coLre.fon
Status: Invisible to the Windows API!

Path: d:\minint\fonts\gulim.ttc
Status: Allocation size mismatch (API: 13518848, Raw: 21392098243528704)

Path: D:\MiniNT\Fonts\coure.fon
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\inf\net21x4.inJ
Status: Invisible to the Windows API!

Path: d:\minint\inf\net3c589.pnf
Status: Size mismatch (API: 11544, Raw: 20829148276600088)

Path: D:\MiniNT\inf\neHan983.inf
Status: Invisible to the Windows API!

Path: d:\minint\inf\netcicap.inf
Status: Allocation size mismatch (API: 8192, Raw: 20266198323175424)

Path: D:\MiniNT\inf\netcb325.iIf
Status: Invisible to the Windows API!

Path: d:\minint\inf\netepro.pnf
Status: Size mismatch (API: 8232, Raw: 20266198323175464)

Path: D:\MiniNT\inf\neHias.PNF
Status: Invisible to the Windows API!

Path: D:\MiniNT\inf\netklsH.PNF
Status: Invisible to the Windows API!

Path: d:\minint\inf\netlanep.inf
Status: Size mismatch (API: 1823, Raw: 20266198323169055)

Path: D:\MiniNT\inf\netmhzH5.inf
Status: Invisible to the Windows API!

Path: D:\MiniNT\inf\neIrsvp.inf
Status: Invisible to the Windows API!

Path: D:\MiniNT\inf\netsk_Hp.PNF
Status: Invisible to the Windows API!

Path: D:\MiniNT\inf\nettdkH.PNF
Status: Invisible to the Windows API!

Path: d:\minint\inf\nettpsmp.inf
Status: Size mismatch (API: 4749, Raw: 20266198323171981)

Path: D:\MiniNT\inf\netwv48.PNJ
Status: Invisible to the Windows API!

Path: D:\MiniNT\inf\netx56J5.inf
Status: Invisible to the Windows API!

Path: d:\minint\inf\nvraid.pnf
Status: Size mismatch (API: 8012, Raw: 20829148276596556)

Path: d:\minint\inf\ramdrv.inf
Status: Allocation size mismatch (API: 2048, Raw: 20829148276590592)

Path: D:\MiniNT\inf\net21x4.inf
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\inf\netan983.inf
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\inf\netcb325.inf
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\inf\netias.PNF
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\inf\netklsi.PNF
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\inf\netmhzn5.inf
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\inf\netrsvp.inf
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\inf\netsk_fp.PNF
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\inf\nettdkb.PNF
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\inf\netwv48.PNF
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\inf\netx56n5.inf
Status: Visible to the Windows API, but not on disk.

Path: d:\minint\system32\backupst.exe
Status: Allocation size mismatch (API: 983040, Raw: 20829148277571584)

Path: D:\MiniNT\system32\BackupSTJP_OEM1.smJ
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\C_1000•.NLS
Status: Invisible to the Windows API!

Path: d:\minint\system32\ipconfig.exe
Status: Size mismatch (API: 49664, Raw: 47006321110729216)

Path: d:\minint\system32\oleacc.dll
Status: Allocation size mismatch (API: 163840, Raw: 47006321110843392)

Path: D:\MiniNT\system32\dbgengIdll
Status: Invisible to the Windows API!

Path: d:\minint\system32\dgnet.dll
Status: Size mismatch (API: 103424, Raw: 41939771529991168)

Path: D:\MiniNT\system32\driverŸ
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\e100b325.dŸn
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\fpnpbaPe.usa
Status: Invisible to the Windows API!

Path: d:\minint\system32\hal.dll
Status: Allocation size mismatch (API: 104448, Raw: 22517998136956928)

Path: D:\MiniNT\system32\IMJP81K.DLT
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\kbQca.dll
Status: Invisible to the Windows API!

Path: d:\minint\system32\kbdic.dll
Status: Size mismatch (API: 6656, Raw: 22799473113569792)

Path: D:\MiniNT\system32\kernel32.dQl
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\LOإO_XGA.BMP
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\msjet40.dlR
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\NOISE.WHT
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\ntWsapi.dll
Status: Invisible to the Windows API!

Path: d:\minint\system32\nvcoi.dll
Status: Allocation size mismatch (API: 32768, Raw: 24488322973859840)

Path: D:\MiniNT\system32\NvRaidSvEnJ.dll
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\odOccp32.cpl
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\polstore.dRl
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\PrRmium.exe
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\rasapi32.dİl
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\RESTORE.reo
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\Restoro.vga
Status: Invisible to the Windows API!

Path: d:\minint\system32\restorest.stc
Status: Allocation size mismatch (API: 139264, Raw: 31243722415022080)

Path: D:\MiniNT\system32\ROkANIME.IME
Status: Invisible to the Windows API!

Path: d:\minint\system32\rsvp.exe
Status: Size mismatch (API: 132608, Raw: 30117822508172800)

Path: D:\MiniNT\system32\servicYs.exe
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\sortkey.nl؞
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\sp؞olss.dll
Status: Invisible to the Windows API!

Path: d:\minint\system32\startnet.cmd
Status: Allocation size mismatch (API: 0, Raw: 440789813528887296)

Path: D:\MiniNT\system32\umpnpmgr.dZl
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\virtdk64.sQs
Status: Invisible to the Windows API!

Path: d:\minint\system32\wingb.ime
Status: Allocation size mismatch (API: 69632, Raw: 22799473113632768)

Path: d:\minint\system32\writer.ini
Status: Size mismatch (API: 569, Raw: 23362423066985017)

Path: d:\minint\system32\backupwiz_oem1.smf
Status: Allocation size mismatch (API: 157696, Raw: 21392098230167552)

Path: D:\MiniNT\system32\BackupSTJP_OEM1.smf
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\C_10006.NLS
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\dbgeng.dll
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\drivers
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\e100b325.din
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\fpnpbase.usa
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\IMJP81K.DLL
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\kbdca.dll
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\kernel32.dll
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\LOGO_XGA.BMP
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\msjet40.dll
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\NOISE.CHT
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\ntdsapi.dll
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\NvRaidSvEnu.dll
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\odbccp32.cpl
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\polstore.dll
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\Premium.exe
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\rasapi32.dll
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\RESTORE.ref
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\Restore.vga
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\ROMANIME.IME
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\services.exe
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\sortkey.nls
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\spoolss.dll
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\umpnpmgr.dll
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\system32\virtdk64.sys
Status: Visible to the Windows API, but not on disk.

Path: D:\MiniNT\WinSxS\x86_Microsoft.Tools.VisualCPlusPlus.Runtime-Libraries_6595b64144ccf1df_6.0.0.0Ox-ww_ff9986d7
Status: Invisible to the Windows API!

Path: D:\MiniNT\WinSxS\x86_Microsoft.Tools.VisualCPlusPlus.Runtime-Libraries_6595b64144ccf1df_6.0.0.0_x-ww_ff9986d7
Status: Visible to the Windows API, but not on disk.

Path: d:\minint\system32\config\security
Status: Allocation size mismatch (API: 0, Raw: 22799473113563136)

Path: \\?\D:\MiniNT\system32\driverŸ\*
Status: Could not enumerate files with the Windows API (0x00000003)!


Path: D:\MiniNT\system32\driverŸ\1394BUS.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\1394vdbg.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ABP480N5.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ac300nd5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ACPI.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ACPIEC.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\adm8511.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\adptsf50.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ADPU16MM.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\afd.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\AHA154X.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\AIC78U2.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\AIC78XX.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\akMpccard.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\aksusb.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ali5261.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ALIIDE.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\AMSINT.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\an983.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\arp1394.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ASC.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ASC3350P.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ASC3550.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\aspi32.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\aspndis3.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\asyncmac.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ATAPI.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\atmarpc.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\atmlane.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\atmuni.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\b1.t4
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\b1cbase.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\b1tr6.t4
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\b1usa.t4
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\b57xp32.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\bcm42u.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\bcm4e5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\beep.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\bioprime.bin
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\brzwlan.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\c4.bin
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\cb102.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\cb325.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\cben5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\CBIDF2K.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\CD20XRNT.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\cdaudio.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\CDFS.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\CDROM.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ce2n5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ce3n5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\cem28n5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\cem33n5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\cem56n5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\cinemst2.sMs
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\CMDIDE.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\cnxt1803.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\CPQARRAY.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\cpqndis5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\cpqtrnd5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\c_1252.nl_
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\c_437.nl_
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\d100ib5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\DAC2W2J.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\DAC960NT.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dc21x4.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\defpa.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dfe650.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dfe650d.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dgapci.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dgsetup.dll
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\diapi2.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\digirlpt.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\DISK.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\diskdump.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\diwan.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dlh5xnd5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dm9pci5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\DMBOOT.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\DMIO.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\DMLOAD.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dp83820.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\DPTI2O.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ds110.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ds4bri.bit
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dspcli.bin
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dspdload.bMn
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dspdqsig.bin
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dxapi.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dxg.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dxgthk.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\e100b325.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\e100isa4.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el515.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el556nd5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el574nd4.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el575nd5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el589nd5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el656cd5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el656ct5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el656nd5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el656se5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el90xbc5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el90xnd5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el985n51.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el98xn5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el99xn51.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\el99xrun.out
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\em556nP.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\amb8002.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\bcm42xx5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\CLASSPNP.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\dimainO.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\e1000nt5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\emu10k1m.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fpcibase.usa
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\hpn.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ipfltdrv.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\mnmdd.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\netbt.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\OPRGHDLR.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\PERC2.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\rndismp.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\skfpwin.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\SYM_U3.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ULTRA.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\enum1394.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\epro4.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\eqn.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\et4000.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\etc
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ex10.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\f3ab18xi.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\f3ab18xj.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fa312nd5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fa410nd5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\FASTFAT.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\FASTTRAK.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fasttx2k.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\FDP.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fem556n5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fetnd5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\FLPYDISK.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\forehe.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fpcibase.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fpcmbase.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fpcmbase.usa
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fsvga.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fs_rec.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\FT100.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\FTDISK.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ftsata2.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\FTTX2.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fusbbase.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fusbbase.usa
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\fxusbase.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\gm.dls
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\hardlock.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\haspdos.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\Haspnt.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\HFS.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\HIDCLASS.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\HIDPARSE.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\HIDUSB.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\HPT366.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\hpt371.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\hpt374.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\HPT3XX.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\hpt3xxNT.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\hptpro.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\I2OMGMT.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\I2OMP.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\I8042PRT.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\iaStor.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\IBMEXMP.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ibmtok.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ibmtrp.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\INI910U.SYK
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\inport.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\INTELIDE.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\io8.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ip5515.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ipinip.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ipnat.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ipsec.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ISAPNP.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\iteraid.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\KBDCLASS.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\KBDHID.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ks.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ksecdd.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\ktc111.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\lanepic5.sys
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\LBRTFDC.SYS
Status: Invisible to the Windows API!

Path: D:\MiniNT\system32\driverŸ\lmndis3.sys
Status: InSSDT
-------------------
#: 122 Function Name: NtOpenProcess
Status: Hooked by "" at address 0x8603ba60

#: 128 Function Name: NtOpenThread
Status: Hooked by "" at address 0x8603be80

#: 253 Function Name: NtSuspendProcess
Status: Hooked by "" at address 0x8603c460

#: 254 Function Name: NtSuspendThread
Status: Hooked by "" at address 0x8603c280

#: 257 Function Name: NtTerminateProcess
Status: Hooked by "" at address 0x8603bc90

#: 258 Function Name: NtTerminateThread
Status: Hooked by "" at address 0x8603c0b0

Stealth Objects
-------------------
Object: Hidden Module [Name: kbiwkmnelkyvlm.dll]
Process: svchost.exe (PID: 1092) Address: 0x10000000 Size: 53248

Object: Hidden Module [Name: kbiwkmoilrdopu.dll]
Process: Explorer.EXE (PID: 540) Address: 0x10000000 Size: 28672

Object: Hidden Module [Name: kbiwkmoilrdopu.dll]
Process: iexplore.exe (PID: 3388) Address: 0x10000000 Size: 28672

Object: Hidden Module [Name: kbiwkmoilrdopu.dll]
Process: iexplore.exe (PID: 3096) Address: 0x10000000 Size: 28672

Object: Hidden Module [Name: kbiwkmoilrdopu.dll]
Process: iexplore.exe (PID: 3208) Address: 0x10000000 Size: 28672

Object: Hidden Code [ETHREAD: 0x86d616b0]
Process: System Address: 0x8603a790 Size: 1000

Hidden Services
-------------------
Service Name: kbiwkmdopwmpar
Image Path: C:\WINDOWS\system32\drivers\kbiwkmdwyeoyaq.sys

==EOF==

I now realise my problem is different from that user's what do I do now? Oh got my typing is going so slow.

BC AdBot (Login to Remove)

 


#2 Blade

Blade

    Strong in the Bleepforce


  • Site Admin
  • 12,702 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:US
  • Local time:06:54 PM

Posted 29 August 2009 - 03:03 PM

Hello ajadagga and :thumbsup: to BleepingComputer.

You have an active rootkit on your machine. With the information you have provided I believe you will need help from the malware removal team. Please read the information about getting started. After you have followed the steps in that guide, I would like you to start a new thread HERE and include a link to this thread.

It would be helpful if you post a note here once you have completed the steps in the guide and have started your topic in malware removal. Good luck and be patient. The HJT team is very busy, so it could be several days before you receive a reply. But rest assured, help is on the way!

~Blade

Posted Image

If I am helping you, it has been 48 hours since your last post, and I have yet to reply to your topic, please send me a PM
Become a BleepingComputer fan: Facebook
Follow us on Twitter!
Circle us on Google+


#3 ajadagga

ajadagga
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:05:54 PM

Posted 29 August 2009 - 05:11 PM

Thanks! Oh god, I posted in the wrong forum, I try to read all the newbie guides to avoid that, guess I missed one.

I posted my new topic here.

Thanks again, I won't get impatient. You guys are total stars doing this for free, for randoms on the internet.

#4 Orange Blossom

Orange Blossom

    OBleepin Investigator


  • Moderator
  • 36,805 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Bloomington, IN
  • Local time:06:54 PM

Posted 29 August 2009 - 11:16 PM

Hello,

Now for the hard part: waiting.

Now that you have posted a log, you should NOT make further changes to your computer (install/uninstall programs, use special fix tools, delete files, edit the registry, etc) unless advised by a HJT Team member, nor should you ask for help elsewhere. Doing so can result in system changes which may not show in the log you already posted. Further, any modifications you make on your own may cause confusion for the helper assisting you and could complicate the malware removal process which would extend the time it takes to clean your computer.

From this point on the HJT Team should be the only members that you take advice from, until they have verified your log as clean.

Please be patient. It may take a while to get a response because the HJT Team members are EXTREMELY busy working logs posted before yours. They are volunteers who will help you out as soon as possible. Once you have made your post and are waiting, please DO NOT make another reply until it has been responded to by a member of the HJT Team. Generally the staff checks the forum for postings that have 0 replies as this makes it easier for them to identify those who have not been helped. If you post another response there will be 1 reply. A team member, looking for a new log to work may assume another HJT Team member is already assisting you and not open the thread to respond.

Please be patient. It may take several days, perhaps less, to get a response but your log will be reviewed and answered as soon as possible. I advise checking your topic once a day for responses.

To avoid confusion, I am closing this topic. Good luck with your log.

Orange Blossom :thumbsup:
Help us help you. If HelpBot replies, you MUST follow step 1 in its reply so we know you need help.

Orange Blossom

An ounce of prevention is worth a pound of cure

SpywareBlaster, WinPatrol Plus, ESET Smart Security, Malwarebytes' Anti-Malware, NoScript Firefox ext., Norton noscript




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users