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

Had a bunch of viruses-- need to know if they're gone


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

#1 cccv

cccv

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:04:42 AM

Posted 12 November 2009 - 03:48 PM

I use Windows XP home edition. Long story short, I got slammed with viruses. Vundo was one, as well as a virut that latched on to everything (even my calculator), and some rootkit stuff (no specific names, just "rootkit, rootkit agent," etc). scariest thing to happen-- someone used it to their advantage to steal my credit card number and buy something in Ho Chi Minh, Vietnam. Needless to say, I want to be absolute sure that I'm safe before doing much on the comp again. However, I don't think I'm 100% out of the woods yet.

I'll start with what I have done.
First, I used Dr Web, which cleaned up most of the virut. AVG still finds it here and there, but at least my desktop loads again.
I used malwarebytes, which got rid of vundo. I just ran it yesterday and it picked up more stuff (a backdoor bot, a trojan agent-- sorry if it sounds like I'm not being specific, but that's all it says. "backdoor.bot," "trojan.agent," "trojan.dropper," etc. They don't have specific names that I know of), so obviously I'm not totally clean. However, it fixed my problem with having my google links redirected. I THINK. Thing is, let's say I do a google search for Timberland then click on the sponsored result for timberland.com. That takes me to a site with this in the address bar:
Removed link-MG

...and spysweeper comes up saying it blocked access to the site (which it did). My next attempt will take me to the timberland site like I wanted. I'm HOPING that spysweeper is just being overprotective or something, I'm not sure. I have tried baiting the virus into redirecting me by searching for "free antivirus" and clicking on the links for AVG, PC Tools, and Avira, but it no longer seems to try to redirect me from those searches (before it would do it all the time). So again, not sure if I'm safe or not.

I also ran combofix-- I didn't do anything with it other than what it did automatically, and that seemed to fix a lot.
And I use AVG version 9, PC Tools, and Webroot spysweeper.

I just need to know if there's still anything terrible lurking around in my comp, especially before I use my new credit card (once I get it). Like I said, I still find stuff here and there when I scan (again, sorry I can't be more specific about it, they all seem to have generic names), and I don't know if I still have anything major that will result in another credit card theft. Can anyone help me? I'll be happy to post any combofix or malwarebytes logs if that would be helpful. Thank you for reading.

Edited by garmanma, 12 November 2009 - 08:11 PM.


BC AdBot (Login to Remove)

 


#2 garmanma

garmanma

    Computer Masochist


  • Members
  • 27,809 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cleveland, Ohio
  • Local time:05:42 AM

Posted 14 November 2009 - 08:48 PM

:trumpet:
We Need to check for Rootkits with RootRepeal
  • Download RootRepeal from the following location and save it to your desktop.
  • Extract RootRepeal.exe from the archive (If you did not use the "Direct Download" mirror).
  • Open Posted Image on your desktop.
  • Click the Posted Image tab.
  • Click the Posted Image button.
  • Check all seven boxes: Posted Image
  • Push Ok
  • Check the box for your main system drive (Usually C:), and press Ok.
  • Allow RootRepeal to run a scan of your system. This may take some time.
  • Once the scan completes, push the Posted Image button. Save the log to your desktop, using a distinctive name, such as RootRepeal.txt. Include this report in your next reply, please.

----------------------------------

Please note: If Rootrepeal fails to run, try this step: Click Settings - Options. Set the Disk Access slider to High

Also try: right-click on rootrepeal.exe and rename it to tatertot.scr

=========================

:flowers:
Please download Win32kDiag.exe by AD and save it to your desktop.
alternate download 1
alternate download 2
  • This tool will create a diagnostic report
  • Double-click on Win32kDiag.exe to run and let it finish.
  • When it states Finished! Press any key to exit..., press any key on your keyboard to close the program.
  • A file called Win32kDiag.txt should be created on your Desktop.
  • Open that file in Notepad and copy/paste the entire contents (from Starting up... to Finished! Press any key to exit...) in your next reply.
--------------------------------------


:thumbsup: Go to Posted Image > Run..., then copy and paste this command into the open box: cmd
Click OK.
At the command prompt C:\>, copy and paste the following command and press Enter:
DIR /a/s %windir%\scecli.dll %windir%\netlogon.dll %windir%\eventlog.dll >Log.txt & START notepad Log.txt
A file called log.txt should be created on your Desktop.
Open that file and copy/paste the contents in your next reply.
Mark
Posted Image
why won't my laptop work?

Having grandkids is God's way of giving you a 2nd chance because you were too busy working your butt off the 1st time around
Do not send me PMs with problems that should be posted in the forums. Keep it in the forums, so everyone benefits
Become a BleepingComputer fan: Facebook and Twitter

#3 cccv

cccv
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:04:42 AM

Posted 15 November 2009 - 06:58 PM

Thanks for the reply. Here's the rootrepeal report:

ROOTREPEAL AD, 2007-2009
==================================================
Scan Start Time: 2009/11/15 17:16
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: 0xF5805000 Size: 98304 File Visible: No Signed: -
Status: -

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

Name: mchInjDrv.sys
Image Path: C:\WINDOWS\system32\Drivers\mchInjDrv.sys
Address: 0xF83F4000 Size: 2560 File Visible: No Signed: -
Status: -

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

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

Path: C:\Documents and Settings\Owner\Application Data\Mozilla\Firefox\Profiles\qzmovqk1.default\sessionstore.js
Status: Could not get file information (Error 0xc0000008)

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\11\11-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v11-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v11-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\12\12-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v12-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v12-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\13\13-{13452DD2-9A43-4D83-A08A-5EC9627E11AA}-v13-{13452DD2-9A43-4D83-A08A-5EC9627E11AA}-v13-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\13\13-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v13-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v13-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\14\14-{13452DD2-9A43-4D83-A08A-5EC9627E11AA}-v14-{13452DD2-9A43-4D83-A08A-5EC9627E11AA}-v14-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\14\14-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v14-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v14-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\15\15-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v15-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v15-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\16\16-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v16-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v16-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\30\31-{597DD5A4-510B-4135-847C-FAEDD12F8B28}-v30-{597DD5A4-510B-4135-847C-FAEDD12F8B28}-v31-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\32\32-{59~2.FRX:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\33\33-{597DD5A4-510B-4135-847C-FAEDD12F8B28}-v33-{597DD5A4-510B-4135-847C-FAEDD12F8B28}-v33-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\34\34-{597DD5A4-510B-4135-847C-FAEDD12F8B28}-v34-{597DD5A4-510B-4135-847C-FAEDD12F8B28}-v34-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\35\35-{597DD5A4-510B-4135-847C-FAEDD12F8B28}-v35-{597DD5A4-510B-4135-847C-FAEDD12F8B28}-v35-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\36\36-{597DD5A4-510B-4135-847C-FAEDD12F8B28}-v36-{597DD5A4-510B-4135-847C-FAEDD12F8B28}-v36-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\37\37-{597DD5A4-510B-4135-847C-FAEDD12F8B28}-v37-{597DD5A4-510B-4135-847C-FAEDD12F8B28}-v37-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\40\40-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v40-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v40-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\41\41-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v41-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v41-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\42\42-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v42-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v42-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\43\43-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v43-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v43-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\43\43-{59~2.FRX:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\44\44-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v44-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v44-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\45\45-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v45-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v45-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\46\46-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v46-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v46-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

Path: C:\Documents and Settings\Owner\Desktop\Ins\Owner\Local Settings\Application Data\Microsoft\Messenger\removed\SharingMetadata\removed\DFSR\Staging\CS{C4387EAF-74BE-0E65-BD59-471DCD19E23D}\48\48-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v48-{1B76D6E9-F776-4CCD-8643-4F4213D4B998}-v48-Downloaded.frx:{59828bbb-3f72-4c1b-a420-b51ad66eb5d3}.XPRESS
Status: Visible to the Windows API, but not on disk.

SSDT
-------------------
#: 017 Function Name: NtAllocateVirtualMemory
Status: Hooked by "<unknown>" at address 0x835e1308

#: 041 Function Name: NtCreateKey
Status: Hooked by "PCTCore.sys" at address 0xf7b40d72

#: 047 Function Name: NtCreateProcess
Status: Hooked by "PCTCore.sys" at address 0xf7b219a6

#: 048 Function Name: NtCreateProcessEx
Status: Hooked by "PCTCore.sys" at address 0xf7b21b98

#: 053 Function Name: NtCreateThread
Status: Hooked by "<unknown>" at address 0x835e15d8

#: 063 Function Name: NtDeleteKey
Status: Hooked by "PCTCore.sys" at address 0xf7b41568

#: 065 Function Name: NtDeleteValueKey
Status: Hooked by "PCTCore.sys" at address 0xf7b41820

#: 119 Function Name: NtOpenKey
Status: Hooked by "PCTCore.sys" at address 0xf7b3fa80

#: 180 Function Name: NtQueueApcThread
Status: Hooked by "<unknown>" at address 0x835e1380

#: 186 Function Name: NtReadVirtualMemory
Status: Hooked by "<unknown>" at address 0x835e1218

#: 192 Function Name: NtRenameKey
Status: Hooked by "PCTCore.sys" at address 0xf7b41c8a

#: 213 Function Name: NtSetContextThread
Status: Hooked by "<unknown>" at address 0x835e1470

#: 226 Function Name: NtSetInformationKey
Status: Hooked by "<unknown>" at address 0x835b01b8

#: 228 Function Name: NtSetInformationProcess
Status: Hooked by "<unknown>" at address 0x835d5a60

#: 229 Function Name: NtSetInformationThread
Status: Hooked by "<unknown>" at address 0x835e14e8

#: 247 Function Name: NtSetValueKey
Status: Hooked by "PCTCore.sys" at address 0xf7b41036

#: 253 Function Name: NtSuspendProcess
Status: Hooked by "<unknown>" at address 0x835d59e8

#: 254 Function Name: NtSuspendThread
Status: Hooked by "<unknown>" at address 0x835e13f8

#: 257 Function Name: NtTerminateProcess
Status: Hooked by "PCTCore.sys" at address 0xf7b21656

#: 258 Function Name: NtTerminateThread
Status: Hooked by "<unknown>" at address 0x835e1560

#: 277 Function Name: NtWriteVirtualMemory
Status: Hooked by "<unknown>" at address 0x835e1290

Stealth Objects
-------------------
Object: Hidden Code [Driver: Tcpip, IRP_MJ_CREATE]
Process: System Address: 0x82ffbfa8 Size: 88

Object: Hidden Code [Driver: Tcpip, IRP_MJ_CREATE_NAMED_PIPE]
Process: System Address: 0x82ffbcb0 Size: 635

Object: Hidden Code [Driver: Tcpip, IRP_MJ_CLOSE]
Process: System Address: 0x82ffbb68 Size: 963

Object: Hidden Code [Driver: Tcpip, IRP_MJ_READ]
Process: System Address: 0x82ffb9f8 Size: 1331

Object: Hidden Code [Driver: Tcpip, IRP_MJ_WRITE]
Process: System Address: 0x82ffb7a8 Size: 1923

Object: Hidden Code [Driver: Tcpip, IRP_MJ_QUERY_INFORMATION]
Process: System Address: 0x82ffb590 Size: 2459

Object: Hidden Code [Driver: Tcpip, IRP_MJ_SET_INFORMATION]
Process: System Address: 0x82ff6c10 Size: 1009

Object: Hidden Code [Driver: Tcpip, IRP_MJ_QUERY_EA]
Process: System Address: 0x82ff69f8 Size: 1545

Object: Hidden Code [Driver: Tcpip, IRP_MJ_SET_EA]
Process: System Address: 0x82ff6838 Size: 1993

Object: Hidden Code [Driver: Tcpip, IRP_MJ_FLUSH_BUFFERS]
Process: System Address: 0x82ff66f0 Size: 2321

Object: Hidden Code [Driver: Tcpip, IRP_MJ_QUERY_VOLUME_INFORMATION]
Process: System Address: 0x82ff65e0 Size: 2593

Object: Hidden Code [Driver: Tcpip, IRP_MJ_SET_VOLUME_INFORMATION]
Process: System Address: 0x82ff6470 Size: 2961

Object: Hidden Code [Driver: Tcpip, IRP_MJ_DIRECTORY_CONTROL]
Process: System Address: 0x82ff63a8 Size: 3161

Object: Hidden Code [Driver: Tcpip, IRP_MJ_FILE_SYSTEM_CONTROL]
Process: System Address: 0x82ff6260 Size: 3489

Object: Hidden Code [Driver: Tcpip, IRP_MJ_DEVICE_CONTROL]
Process: System Address: 0x82ff5fa8 Size: 88

Object: Hidden Code [Driver: Tcpip, IRP_MJ_INTERNAL_DEVICE_CONTROL]
Process: System Address: 0x82ff4f58 Size: 168

Object: Hidden Code [Driver: Tcpip, IRP_MJ_SHUTDOWN]
Process: System Address: 0x82ff4e80 Size: 384

Object: Hidden Code [Driver: Tcpip, IRP_MJ_LOCK_CONTROL]
Process: System Address: 0x82ff4d18 Size: 744

Object: Hidden Code [Driver: Tcpip, IRP_MJ_CLEANUP]
Process: System Address: 0x82ff4ba8 Size: 1112

Object: Hidden Code [Driver: Tcpip, IRP_MJ_CREATE_MAILSLOT]
Process: System Address: 0x82fedc90 Size: 737

Object: Hidden Code [Driver: Tcpip, IRP_MJ_QUERY_SECURITY]
Process: System Address: 0x82fedb10 Size: 266

Object: Hidden Code [Driver: Tcpip, IRP_MJ_SET_SECURITY]
Process: System Address: 0x82fed410 Size: 2058

Object: Hidden Code [Driver: Tcpip, IRP_MJ_POWER]
Process: System Address: 0x83013180 Size: 1377

Object: Hidden Code [Driver: Tcpip, IRP_MJ_SYSTEM_CONTROL]
Process: System Address: 0x830125f8 Size: 166

Object: Hidden Code [Driver: Tcpip, IRP_MJ_DEVICE_CHANGE]
Process: System Address: 0x83012490 Size: 526

Object: Hidden Code [Driver: Tcpip, IRP_MJ_QUERY_QUOTA]
Process: System Address: 0x83012320 Size: 894

Object: Hidden Code [Driver: Tcpip, IRP_MJ_SET_QUOTA]
Process: System Address: 0x83012210 Size: 1166

Object: Hidden Code [Driver: Tcpip, IRP_MJ_PNP]
Process: System Address: 0x83010bf8 Size: 889

Shadow SSDT
-------------------
#: 307 Function Name: NtUserAttachThreadInput
Status: Hooked by "<unknown>" at address 0x82f9cf08

#: 383 Function Name: NtUserGetAsyncKeyState
Status: Hooked by "<unknown>" at address 0x82c21420

#: 414 Function Name: NtUserGetKeyboardState
Status: Hooked by "<unknown>" at address 0x82fc66e8

#: 416 Function Name: NtUserGetKeyState
Status: Hooked by "<unknown>" at address 0x832944b0

#: 460 Function Name: NtUserMessageCall
Status: Hooked by "<unknown>" at address 0x82f9b618

#: 475 Function Name: NtUserPostMessage
Status: Hooked by "<unknown>" at address 0x82f750c8

#: 476 Function Name: NtUserPostThreadMessage
Status: Hooked by "<unknown>" at address 0x82fdc540

#: 549 Function Name: NtUserSetWindowsHookEx
Status: Hooked by "<unknown>" at address 0x8340b0c8

#: 552 Function Name: NtUserSetWinEventHook
Status: Hooked by "<unknown>" at address 0x82ea60c8

==EOF==

Here's the diagnostic report:

Running from: C:\Documents and Settings\Owner\Desktop\Win32kDiag.exe

Log file at : C:\Documents and Settings\Owner\Desktop\Win32kDiag.txt

WARNING: Could not get backup privileges!

Searching 'C:\WINDOWS'...





Finished!


And here's the log...

Volume in drive C has no label.
Volume Serial Number is 587B-2287

Directory of C:\WINDOWS\$hf_mig$\KB968389\SP2QFE

02/06/2009 12:46 PM 408,064 netlogon.dll
1 File(s) 408,064 bytes

Directory of C:\WINDOWS\$hf_mig$\KB975467\SP2QFE

02/06/2009 12:46 PM 408,064 netlogon.dll
1 File(s) 408,064 bytes

Directory of C:\WINDOWS\$NtServicePackUninstall$

08/04/2004 01:00 PM 180,224 scecli.dll

Directory of C:\WINDOWS\$NtServicePackUninstall$

08/04/2004 01:00 PM 407,040 netlogon.dll

Directory of C:\WINDOWS\$NtServicePackUninstall$

08/04/2004 01:00 PM 55,808 eventlog.dll
3 File(s) 643,072 bytes

Directory of C:\WINDOWS\ERDNT\cache

04/13/2008 06:12 PM 181,248 scecli.dll

Directory of C:\WINDOWS\ERDNT\cache

04/13/2008 06:12 PM 407,040 netlogon.dll

Directory of C:\WINDOWS\ERDNT\cache

04/13/2008 06:11 PM 56,320 eventlog.dll
3 File(s) 644,608 bytes

Directory of C:\WINDOWS\ServicePackFiles\i386

04/13/2008 06:12 PM 181,248 scecli.dll

Directory of C:\WINDOWS\ServicePackFiles\i386

04/13/2008 06:12 PM 407,040 netlogon.dll

Directory of C:\WINDOWS\ServicePackFiles\i386

04/13/2008 06:11 PM 56,320 eventlog.dll
3 File(s) 644,608 bytes

Directory of C:\WINDOWS\system32

04/13/2008 06:12 PM 181,248 scecli.dll

Directory of C:\WINDOWS\system32

04/13/2008 06:12 PM 407,040 netlogon.dll

Directory of C:\WINDOWS\system32

04/13/2008 06:11 PM 56,320 eventlog.dll
3 File(s) 644,608 bytes

Total Files Listed:
14 File(s) 3,393,024 bytes
0 Dir(s) 7,661,658,112 bytes free

Edited by Orange Blossom, 17 November 2009 - 05:27 PM.


#4 garmanma

garmanma

    Computer Masochist


  • Members
  • 27,809 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cleveland, Ohio
  • Local time:05:42 AM

Posted 16 November 2009 - 06:34 PM

Path: C:\Documents and Settings\Owner\Application Data\Mozilla\Firefox\Profiles\qzmovqk1.default\sessionstore.js
Hooked by "" at address 0x82f9cf08
Status: Hooked by "PCTCore.sys" at address 0xf7b40d72


You still have serious issues

Now that you were successful in creating those two logs you need to post them in our HJT forum There they will help you with the removal through some custom scripts and programs that we cannot run here in this forum

First, try to run a DDS / HJT log as outlined in our preparation guide:
http://www.bleepingcomputer.com/forums/t/34773/preparation-guide-for-use-before-using-malware-removal-tools-and-requesting-help/

If it won't run, don't worry, just give a brief description and tell them that these logs were all you could get to run successfully

Post them here:
http://www.bleepingcomputer.com/forums/f/22/virus-trojan-spyware-and-malware-removal-logs/

The HJT team is extremely busy, so be patient and good luck
Mark
Posted Image
why won't my laptop work?

Having grandkids is God's way of giving you a 2nd chance because you were too busy working your butt off the 1st time around
Do not send me PMs with problems that should be posted in the forums. Keep it in the forums, so everyone benefits
Become a BleepingComputer fan: Facebook and Twitter

#5 cccv

cccv
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:04:42 AM

Posted 16 November 2009 - 09:46 PM

Alright, thanks. Going to work on that tomorrow. Sorry to ask another favor, but could a mod delete that block of data related to msn messenger in the rootrepeal log under hidden/locked files? I assumed I'd be able to go in and edit it myself when you were done looking at it, but it doesn't look like I can. I'd rather not have the email address of me and my correspondent posted online. Thanks again.

#6 Orange Blossom

Orange Blossom

    OBleepin Investigator


  • Moderator
  • 36,993 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Bloomington, IN
  • Local time:05:42 AM

Posted 17 November 2009 - 05:18 PM

Hello,

I'll remove the e-mail addresses.

Now that you have posted a log here: http://www.bleepingcomputer.com/forums/t/272164/i-have-something/ 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, up to two weeks 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 as the e-mail notification system is unreliable.

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