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

Rootkit removal notice


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

#1 lazyvista

lazyvista

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:01:52 PM

Posted 27 September 2009 - 09:16 AM

My McAfee virus scanner has logged that it has removed a Generic Rootki.d!rootkit (Trojan) for two scheduled scans in a row.

Nobody in the family used this machine between scans.

Other than this message, I have not noticed anything going on with the machine.

I'm thinking the virus scanner is catching the virus, but not what is 'putting' it on the machine.

What can I do verify if everything is okay?

Machine is executing Windows 2000 - Sp4

Thanks
Steve

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 72,760 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:52 PM

Posted 27 September 2009 - 12:47 PM

Hi Steve, let's run these and see if anything is left behind.
Next run MBAM (MalwareBytes):

NOTE: Before saving MBAM please rename it to zztoy.exe....now save it to your desktop.

Please download Malwarebytes Anti-Malware and save it to your desktop.

alternate download link

MBAM may "make changes to your registry" as part of its disinfection routine. If using other security programs that detect registry changes (ie Spybot's Teatimer), they may interfere or alert you. Temporarily disable such programs or permit them to allow the changes.
  • Make sure you are connected to the Internet.
  • Double-click on mbam-setup.exe to install the application.
  • When the installation begins, follow the prompts and do not make any changes to default settings.
  • When installation has finished, make sure you leave both of these checked:
    • Update Malwarebytes' Anti-Malware
    • Launch Malwarebytes' Anti-Malware
  • Then click Finish.
MBAM will automatically start and you will be asked to update the program before performing a scan.
  • If an update is found, the program will automatically update itself. Press the OK button to close that box and continue.
  • If you encounter any problems while downloading the definition updates, manually download them from here and just double-click on mbam-rules.exe to install.
On the Scanner tab:
  • Make sure the "Perform Quick Scan" option is selected.
  • Then click on the Scan button.
  • If asked to select the drives to scan, leave all the drives selected and click on the Start Scan button.
  • The scan will begin and "Scan in progress" will show at the top. It may take some time to complete so please be patient.
  • When the scan is finished, a message box will say "The scan completed successfully. Click 'Show Results' to display all objects found".
  • Click OK to close the message box and continue with the removal process.
Back at the main Scanner screen:
  • Click on the Show Results button to see a list of any malware that was found.
  • Make sure that everything is checked, and click Remove Selected.
  • When removal is completed, a log report will open in Notepad.
  • The log is automatically saved and can be viewed by clicking the Logs tab in MBAM.
  • Copy and paste the contents of that report in your next reply. Be sure to post the complete log to include the top portion which shows MBAM's database version and your operating system.
  • Exit MBAM when done.
Note: If MBAM encounters a file that is difficult to remove, you will be asked to reboot your computer so MBAM can proceed with the disinfection process. If asked to restart the computer, please do so immediately. Failure to reboot normally (not into safe mode) will prevent MBAM from removing all the malware.


***********************
Next run ATF and SAS:
Note.. SAS doesn't open the registry hives for other user accounts on the system, so scans should be done from each user account.

Note: On Vista, "Windows Temp" is disabled. To empty "Windows Temp" ATF-Cleaner must be "Run as an Administrator".

From your regular user account..
Download Attribune's ATF Cleaner and then SUPERAntiSpyware , Free Home Version. Save both to desktop ..
DO NOT run yet.
Open SUPER from icon and install and Update it
Under Scanner Options make sure the following are checked (leave all others unchecked):
Close browsers before scanning.
Scan for tracking cookies.
Terminate memory threats before quarantining
.
Click the "Close" button to leave the control center screen and exit the program. DO NOT run yet.

Now reboot into Safe Mode: How to enter safe mode(XP)
Using the F8 Method
Restart your computer.
When the machine first starts again it will generally list some equipment that is installed in your machine, amount of memory, hard drives installed etc. At this point you should gently tap the F8 key repeatedly until you are presented with a Windows XP Advanced Options menu.
Select the option for Safe Mode using the arrow keys.
Then press enter on your keyboard to boot into Safe Mode
.

Double-click ATF-Cleaner.exe to run the program.
Under Main "Select Files to Delete" choose: Select All.
Click the Empty Selected button.

If you use Firefox or Opera browser click that browser at the top and choose: Select All
Click the Empty Selected button.
If you would like to keep your saved passwords, please click No at the prompt.
Click Exit on the Main menu to close the program
.

NOW Scan with SUPER
Open from the desktop icon or the program Files list
On the left, make sure you check C:\Fixed Drive.
Perform a Complete scan. After scan,Verify they are all checked.
Click OK on the summary screen to quarantine all found items.
If asked if you want to reboot, click "Yes" and reboot normally.

To retrieve the removal information after reboot, launch SUPERAntispyware again.
Click Preferences, then click the Statistics/Logs tab.
Under Scanner Logs, double-click SUPERAntiSpyware Scan Log.
If there are several logs, click the current dated log and press View log.
A text file will open in your default text editor.
Please copy and paste the Scan Log results in your next reply.
Click Close to exit the program.


Please ask any needed questions,post 2 logs and Let us know how the PC is running now.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#3 lazyvista

lazyvista
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:01:52 PM

Posted 27 September 2009 - 08:12 PM

I was unable to execute the SuperAniSpyware program in safemode.

I'm running Windows 2000.

I'm still not seeing anything that tells me a virus is on the machine. McAfee is scheduled to execute again over night so I'll see if the RootKit is not found.

Here are the logs:

Malwarebytes' Anti-Malware 1.41
Database version: 2866
Windows 5.0.2195 Service Pack 4

9/27/2009 4:05:29 PM
mbam-log-2009-09-27 (16-05-29).txt

Scan type: Quick Scan
Objects scanned: 102413
Time elapsed: 5 minute(s), 46 second(s)

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

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
\\?\globalroot\systemroot\system32\gasfkypbbhheko.dll (Rootkit.TDSS) -> Delete on reboot.

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:
\\?\globalroot\systemroot\system32\gasfkypbbhheko.dll (Rootkit.TDSS) -> Quarantined and deleted successfully.
C:\Documents and Settings\Steve.DADS2800\Favorites\Online Security Test.url (Rogue.Link) -> Quarantined and deleted successfully.

***********************************************************************************************************************

SUPERAntiSpyware Scan Log
http://www.superantispyware.com

Generated 09/27/2009 at 04:53 PM

Application Version : 4.29.1002

Core Rules Database Version : 4102
Trace Rules Database Version: 2065

Scan type : Complete Scan
Total Scan Time : 00:25:37

Memory items scanned : 425
Memory threats detected : 0
Registry items scanned : 4664
Registry threats detected : 9
File items scanned : 16582
File threats detected : 1

Trojan.Media-Codec
HKLM\Software\Classes\CLSID\{0D045BAA-4BD3-4C94-BE8B-21536BD6BD9F}
HKCR\CLSID\{0D045BAA-4BD3-4C94-BE8B-21536BD6BD9F}
HKCR\CLSID\{0D045BAA-4BD3-4C94-BE8B-21536BD6BD9F}
HKCR\CLSID\{0D045BAA-4BD3-4C94-BE8B-21536BD6BD9F}\Implemented Categories
HKCR\CLSID\{0D045BAA-4BD3-4C94-BE8B-21536BD6BD9F}\Implemented Categories\{00021493-0000-0000-C000-000000000046}
HKCR\CLSID\{0D045BAA-4BD3-4C94-BE8B-21536BD6BD9F}\InprocServer32
HKCR\CLSID\{0D045BAA-4BD3-4C94-BE8B-21536BD6BD9F}\InprocServer32#ThreadingModel
C:\PROGRAM FILES\VIDEO ACTIVEX OBJECT\IESPLUGIN.DLL
HKLM\Software\Microsoft\Internet Explorer\Toolbar#{0D045BAA-4BD3-4C94-BE8B-21536BD6BD9F}
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\explorer\run#isamonitor.exe [ C:\Program Files\Video ActiveX Object\isamonitor.exe ]

#4 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 72,760 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:52 PM

Posted 28 September 2009 - 01:47 PM

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.

How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#5 lazyvista

lazyvista
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:01:52 PM

Posted 29 September 2009 - 07:00 AM

Recevied this error when executing rootrepeal

DeviceIoControl Error! Error Code = 0x0

#6 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 72,760 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:52 PM

Posted 29 September 2009 - 09:25 AM

It looks like there is a rootkit variant in this log. The rootkit itself is a protection module used to terminate a variety of security tools by changing the permissions on targeted programs so that they cannot run or complete scans. There are some new variants of rootkits in the wild right now that will require custom scripts to remove the infection, the process must be completed by HJT team members or above.

Failure to follow the proper removal process can and will cause serious damage to a machine. Recovery of the machine may be difficult, if not impossible.


Download this Utility and save it to your Desktop.
Double-click the Utility to run it and and let it finish.
When it states Finished! Press any key to exit, press any key to close the program.
It will save a .txt file to your desktop automatically. Double-click on the Win32kDiag.txt file that is located on your Desktop and post the entire contents of that log as part of the reply in the topic you will create below..

Next please go here HijackThis Logs and Virus/Trojan/Spyware/Malware Removal ,click New Topic,give it a relevant Title and post the above Win32kDiag.exe log.

Let me know how that went.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#7 lazyvista

lazyvista
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:01:52 PM

Posted 29 September 2009 - 05:38 PM

I executed Win32KDiag.exe and posted the log.

This is the [post="http://www.bleepingcomputer.com/forums/t/261161/possible-variant-of-rootkit/"]Thread[/post]

#8 lazyvista

lazyvista
  • Topic Starter

  • Members
  • 33 posts
  • OFFLINE
  •  
  • Local time:01:52 PM

Posted 29 September 2009 - 05:42 PM

I retried Rootrepeal.exe. I still got the error, but did a 'Save Report' anyway. Here is the output.

ROOTREPEAL © AD, 2007-2009
==================================================
Scan Start Time: 2009/09/29 17:39
Program Version: Version 1.3.5.0
Windows Version: Windows 2000 SP4
==================================================

Drivers
-------------------
Name: ACPI.sys
Image Path: ACPI.sys
Address: 0xBFFD8000 Size: 163840 File Visible: - Signed: -
Status: -

Name: afd.sys
Image Path: C:\WINNT\System32\drivers\afd.sys
Address: 0xBCACE000 Size: 122880 File Visible: - Signed: -
Status: -

Name: AFS2K.SYS
Image Path: C:\WINNT\System32\Drivers\AFS2K.SYS
Address: 0xEB470000 Size: 57344 File Visible: - Signed: -
Status: -

Name: ALCXSENS.SYS
Image Path: C:\WINNT\system32\drivers\ALCXSENS.SYS
Address: 0xBF684000 Size: 393216 File Visible: - Signed: -
Status: -

Name: ALCXWDM.SYS
Image Path: C:\WINNT\system32\drivers\ALCXWDM.SYS
Address: 0xBF729000 Size: 532480 File Visible: - Signed: -
Status: -

Name: atapi.sys
Image Path: atapi.sys
Address: 0xBFF83000 Size: 90112 File Visible: - Signed: -
Status: -

Name: audstub.sys
Image Path: C:\WINNT\System32\DRIVERS\audstub.sys
Address: 0xEB9EE000 Size: 4096 File Visible: - Signed: -
Status: -

Name: Beep.SYS
Image Path: C:\WINNT\System32\Drivers\Beep.SYS
Address: 0xEBA09000 Size: 4096 File Visible: - Signed: -
Status: -

Name: BOOTVID.dll
Image Path: C:\WINNT\System32\BOOTVID.dll
Address: 0xEB810000 Size: 12288 File Visible: - Signed: -
Status: -

Name: Cdfs.SYS
Image Path: C:\WINNT\System32\Drivers\Cdfs.SYS
Address: 0xBCB5C000 Size: 65536 File Visible: - Signed: -
Status: -

Name: Cdr4_2K.SYS
Image Path: C:\WINNT\System32\Drivers\Cdr4_2K.SYS
Address: 0xEB9DA000 Size: 4096 File Visible: - Signed: -
Status: -

Name: Cdralw2k.SYS
Image Path: C:\WINNT\System32\Drivers\Cdralw2k.SYS
Address: 0xEB9DE000 Size: 4096 File Visible: - Signed: -
Status: -

Name: cdrom.sys
Image Path: C:\WINNT\System32\DRIVERS\cdrom.sys
Address: 0xEB6B0000 Size: 28672 File Visible: - Signed: -
Status: -

Name: CLASSPNP.SYS
Image Path: C:\WINNT\System32\DRIVERS\CLASSPNP.SYS
Address: 0xEB420000 Size: 36864 File Visible: - Signed: -
Status: -

Name: disk.sys
Image Path: disk.sys
Address: 0xEB690000 Size: 32768 File Visible: - Signed: -
Status: -

Name: Diskperf.sys
Image Path: Diskperf.sys
Address: 0xEB900000 Size: 8192 File Visible: - Signed: -
Status: -

Name: dmio.sys
Image Path: dmio.sys
Address: 0xBFFB6000 Size: 139264 File Visible: - Signed: -
Status: -

Name: dmload.sys
Image Path: dmload.sys
Address: 0xEB902000 Size: 8192 File Visible: - Signed: -
Status: -

Name: dump_diskdump.sys
Image Path: C:\WINNT\System32\Drivers\dump_diskdump.sys
Address: 0xBF651000 Size: 16384 File Visible: No Signed: -
Status: -

Name: dump_viasraid.sys
Image Path: C:\WINNT\System32\Drivers\dump_viasraid.sys
Address: 0xBD239000 Size: 77824 File Visible: No Signed: -
Status: -

Name: Dxapi.sys
Image Path: C:\WINNT\system32\DRIVERS\Dxapi.sys
Address: 0xBCAA6000 Size: 12288 File Visible: - Signed: -
Status: -

Name: EFS.SYS
Image Path: C:\WINNT\System32\Drivers\EFS.SYS
Address: 0xEB750000 Size: 28672 File Visible: - Signed: -
Status: -

Name: Fastfat.SYS
Image Path: C:\WINNT\System32\Drivers\Fastfat.SYS
Address: 0xBD24C000 Size: 143360 File Visible: - Signed: -
Status: -

Name: fdc.sys
Image Path: C:\WINNT\System32\DRIVERS\fdc.sys
Address: 0xEB720000 Size: 28672 File Visible: - Signed: -
Status: -

Name: fetnd5bv.sys
Image Path: C:\WINNT\system32\DRIVERS\fetnd5bv.sys
Address: 0xEB490000 Size: 45056 File Visible: - Signed: -
Status: -

Name: Fips.SYS
Image Path: C:\WINNT\System32\Drivers\Fips.SYS
Address: 0xEB5F0000 Size: 36864 File Visible: - Signed: -
Status: -

Name: flpydisk.sys
Image Path: C:\WINNT\System32\DRIVERS\flpydisk.sys
Address: 0xEB730000 Size: 20480 File Visible: - Signed: -
Status: -

Name: fltmgr.sys
Image Path: fltmgr.sys
Address: 0xBFF3B000 Size: 139264 File Visible: - Signed: -
Status: -

Name: Fs_Rec.SYS
Image Path: C:\WINNT\System32\Drivers\Fs_Rec.SYS
Address: 0xEB910000 Size: 8192 File Visible: - Signed: -
Status: -

Name: ftdisk.sys
Image Path: ftdisk.sys
Address: 0xBFF99000 Size: 118784 File Visible: - Signed: -
Status: -

Name: GEARAspiWDM.sys
Image Path: C:\WINNT\System32\Drivers\GEARAspiWDM.sys
Address: 0xEB6B8000 Size: 28672 File Visible: - Signed: -
Status: -

Name: hal.dll
Image Path: C:\WINNT\System32\hal.dll
Address: 0x80062000 Size: 82176 File Visible: - Signed: -
Status: -

Name: HIDCLASS.SYS
Image Path: C:\WINNT\System32\DRIVERS\HIDCLASS.SYS
Address: 0xEB7B0000 Size: 24576 File Visible: - Signed: -
Status: -

Name: HIDPARSE.SYS
Image Path: C:\WINNT\System32\DRIVERS\HIDPARSE.SYS
Address: 0xEB778000 Size: 24576 File Visible: - Signed: -
Status: -

Name: hidusb.sys
Image Path: C:\WINNT\System32\DRIVERS\hidusb.sys
Address: 0xEB8E0000 Size: 16384 File Visible: - Signed: -
Status: -

Name: ipfltdrv.sys
Image Path: C:\WINNT\System32\DRIVERS\ipfltdrv.sys
Address: 0xEB540000 Size: 36864 File Visible: - Signed: -
Status: -

Name: ipsec.sys
Image Path: C:\WINNT\System32\DRIVERS\ipsec.sys
Address: 0xBBF82000 Size: 81920 File Visible: - Signed: -
Status: -

Name: isapnp.sys
Image Path: isapnp.sys
Address: 0xEB410000 Size: 49152 File Visible: - Signed: -
Status: -

Name: kbdclass.sys
Image Path: C:\WINNT\System32\DRIVERS\kbdclass.sys
Address: 0xEB798000 Size: 24576 File Visible: - Signed: -
Status: -

Name: kbdhid.sys
Image Path: C:\WINNT\System32\DRIVERS\kbdhid.sys
Address: 0xEB8F4000 Size: 16384 File Visible: - Signed: -
Status: -

Name: kmixer.sys
Image Path: C:\WINNT\system32\drivers\kmixer.sys
Address: 0xB9FA9000 Size: 151552 File Visible: - Signed: -
Status: -

Name: KS.SYS
Image Path: C:\WINNT\system32\drivers\KS.SYS
Address: 0xBF6E4000 Size: 131072 File Visible: - Signed: -
Status: -

Name: KSecDD.sys
Image Path: KSecDD.sys
Address: 0xBFF29000 Size: 73728 File Visible: - Signed: -
Status: -

Name: Lbd.sys
Image Path: Lbd.sys
Address: 0xEB430000 Size: 61440 File Visible: - Signed: -
Status: -

Name: mfeavfk.sys
Image Path: C:\WINNT\system32\drivers\mfeavfk.sys
Address: 0xBBEA8000 Size: 73728 File Visible: - Signed: -
Status: -

Name: mfebopk.sys
Image Path: C:\WINNT\system32\drivers\mfebopk.sys
Address: 0xEB770000 Size: 28672 File Visible: - Signed: -
Status: -

Name: mfehidk.sys
Image Path: C:\WINNT\system32\drivers\mfehidk.sys
Address: 0xBD297000 Size: 208896 File Visible: - Signed: -
Status: -

Name: mferkdk.sys
Image Path: C:\WINNT\system32\drivers\mferkdk.sys
Address: 0xEB700000 Size: 28672 File Visible: - Signed: -
Status: -

Name: mfesmfk.sys
Image Path: C:\WINNT\system32\drivers\mfesmfk.sys
Address: 0xBBD68000 Size: 36864 File Visible: - Signed: -
Status: -

Name: mnmdd.SYS
Image Path: C:\WINNT\System32\Drivers\mnmdd.SYS
Address: 0xEBA13000 Size: 4096 File Visible: - Signed: -
Status: -

Name: mouclass.sys
Image Path: C:\WINNT\System32\DRIVERS\mouclass.sys
Address: 0xEB788000 Size: 24576 File Visible: - Signed: -
Status: -

Name: mouhid.sys
Image Path: C:\WINNT\System32\DRIVERS\mouhid.sys
Address: 0xEB8EC000 Size: 12288 File Visible: - Signed: -
Status: -

Name: MountMgr.sys
Image Path: MountMgr.sys
Address: 0xEB688000 Size: 32768 File Visible: - Signed: -
Status: -

Name: Mpfp.sys
Image Path: C:\WINNT\System32\Drivers\Mpfp.sys
Address: 0xBD45C000 Size: 159744 File Visible: - Signed: -
Status: -

Name: mrxsmb.sys
Image Path: C:\WINNT\System32\DRIVERS\mrxsmb.sys
Address: 0xBD2CA000 Size: 417792 File Visible: - Signed: -
Status: -

Name: Msfs.SYS
Image Path: C:\WINNT\System32\Drivers\Msfs.SYS
Address: 0xEB7C8000 Size: 24576 File Visible: - Signed: -
Status: -

Name: msgpc.sys
Image Path: C:\WINNT\System32\DRIVERS\msgpc.sys
Address: 0xEB530000 Size: 36864 File Visible: - Signed: -
Status: -

Name: Mup.sys
Image Path: Mup.sys
Address: 0xBFE6B000 Size: 90112 File Visible: - Signed: -
Status: -

Name: NDIS.sys
Image Path: NDIS.sys
Address: 0xBFE81000 Size: 172032 File Visible: - Signed: -
Status: -

Name: ndistapi.sys
Image Path: C:\WINNT\System32\DRIVERS\ndistapi.sys
Address: 0xEB894000 Size: 12288 File Visible: - Signed: -
Status: -

Name: ndiswan.sys
Image Path: C:\WINNT\System32\DRIVERS\ndiswan.sys
Address: 0xBF66D000 Size: 94208 File Visible: - Signed: -
Status: -

Name: NDProxy.SYS
Image Path: C:\WINNT\System32\Drivers\NDProxy.SYS
Address: 0xEB500000 Size: 40960 File Visible: - Signed: -
Status: -

Name: netbios.sys
Image Path: C:\WINNT\System32\DRIVERS\netbios.sys
Address: 0xEB550000 Size: 36864 File Visible: - Signed: -
Status: -

Name: netbt.sys
Image Path: C:\WINNT\System32\DRIVERS\netbt.sys
Address: 0xBD431000 Size: 176128 File Visible: - Signed: -
Status: -

Name: Npfs.SYS
Image Path: C:\WINNT\System32\Drivers\Npfs.SYS
Address: 0xEB520000 Size: 36864 File Visible: - Signed: -
Status: -

Name: Ntfs.sys
Image Path: Ntfs.sys
Address: 0xBFEAB000 Size: 516096 File Visible: - Signed: -
Status: -

Name: ntoskrnl.exe
Image Path: C:\WINNT\System32\ntoskrnl.exe
Address: 0x80400000 Size: 1690880 File Visible: - Signed: -
Status: -

Name: Null.SYS
Image Path: C:\WINNT\System32\Drivers\Null.SYS
Address: 0xEBA07000 Size: 4096 File Visible: - Signed: -
Status: -

Name: nv4_disp.dll
Image Path: C:\WINNT\System32\nv4_disp.dll
Address: 0xBCC48000 Size: 5693440 File Visible: - Signed: -
Status: -

Name: nv4_mini.sys
Image Path: C:\WINNT\system32\DRIVERS\nv4_mini.sys
Address: 0xBF7CD000 Size: 6807552 File Visible: - Signed: -
Status: -

Name: parallel.sys
Image Path: C:\WINNT\System32\DRIVERS\parallel.sys
Address: 0xEB4C0000 Size: 61440 File Visible: - Signed: -
Status: -

Name: parport.sys
Image Path: C:\WINNT\System32\DRIVERS\parport.sys
Address: 0xEB740000 Size: 28672 File Visible: - Signed: -
Status: -

Name: PartMgr.sys
Image Path: PartMgr.sys
Address: 0xEB814000 Size: 12288 File Visible: - Signed: -
Status: -

Name: ParVdm.SYS
Image Path: C:\WINNT\System32\Drivers\ParVdm.SYS
Address: 0xEB91E000 Size: 8192 File Visible: - Signed: -
Status: -

Name: pci.sys
Image Path: pci.sys
Address: 0xEB400000 Size: 61440 File Visible: - Signed: -
Status: -

Name: pciide.sys
Image Path: pciide.sys
Address: 0xEB9C9000 Size: 4096 File Visible: - Signed: -
Status: -

Name: PCIIDEX.SYS
Image Path: C:\WINNT\System32\DRIVERS\PCIIDEX.SYS
Address: 0xEB680000 Size: 24576 File Visible: - Signed: -
Status: -

Name: portcls.sys
Image Path: C:\WINNT\system32\drivers\portcls.sys
Address: 0xBF704000 Size: 151552 File Visible: - Signed: -
Status: -

Name: ptilink.sys
Image Path: C:\WINNT\System32\DRIVERS\ptilink.sys
Address: 0xEB800000 Size: 20480 File Visible: - Signed: -
Status: -

Name: PxHelper.sys
Image Path: C:\WINNT\system32\drivers\PxHelper.sys
Address: 0xEB878000 Size: 12288 File Visible: - Signed: -
Status: -

Name: rasacd.sys
Image Path: C:\WINNT\System32\DRIVERS\rasacd.sys
Address: 0xEB918000 Size: 8192 File Visible: - Signed: -
Status: -

Name: rasl2tp.sys
Image Path: C:\WINNT\System32\DRIVERS\rasl2tp.sys
Address: 0xEB4A0000 Size: 53248 File Visible: - Signed: -
Status: -

Name: raspptp.sys
Image Path: C:\WINNT\System32\DRIVERS\raspptp.sys
Address: 0xEB4B0000 Size: 49152 File Visible: - Signed: -
Status: -

Name: raspti.sys
Image Path: C:\WINNT\System32\DRIVERS\raspti.sys
Address: 0xEB6A0000 Size: 20480 File Visible: - Signed: -
Status: -

Name: rdbss.sys
Image Path: C:\WINNT\System32\DRIVERS\rdbss.sys
Address: 0xBD342000 Size: 172032 File Visible: - Signed: -
Status: -

Name: rootrepeal1.sys
Image Path: C:\WINNT\system32\drivers\rootrepeal1.sys
Address: 0xBC0CE000 Size: 49152 File Visible: No Signed: -
Status: -

Name: SASDIFSV.SYS
Image Path: C:\Program Files\SUPERAntiSpyware\SASDIFSV.SYS
Address: 0xEB7E0000 Size: 24576 File Visible: - Signed: -
Status: -

Name: SASENUM.SYS
Image Path: C:\Program Files\SUPERAntiSpyware\SASENUM.SYS
Address: 0xEB6D8000 Size: 20480 File Visible: - Signed: -
Status: -

Name: SASKUTIL.sys
Image Path: C:\Program Files\SUPERAntiSpyware\SASKUTIL.sys
Address: 0xBD36C000 Size: 151552 File Visible: - Signed: -
Status: -

Name: SCSIPORT.SYS
Image Path: C:\WINNT\system32\drivers\SCSIPORT.SYS
Address: 0xBFF5D000 Size: 77824 File Visible: - Signed: -
Status: -

Name: serenum.sys
Image Path: C:\WINNT\System32\DRIVERS\serenum.sys
Address: 0xEB888000 Size: 16384 File Visible: - Signed: -
Status: -

Name: serial.sys
Image Path: C:\WINNT\System32\DRIVERS\serial.sys
Address: 0xEB480000 Size: 65536 File Visible: - Signed: -
Status: -

Name: srv.sys
Image Path: C:\WINNT\System32\DRIVERS\srv.sys
Address: 0xBC879000 Size: 241664 File Visible: - Signed: -
Status: -

Name: swenum.sys
Image Path: C:\WINNT\System32\DRIVERS\swenum.sys
Address: 0xEB9F8000 Size: 4096 File Visible: - Signed: -
Status: -

Name: sysaudio.sys
Image Path: C:\WINNT\system32\drivers\sysaudio.sys
Address: 0xEB670000 Size: 49152 File Visible: - Signed: -
Status: -

Name: tcpip.sys
Image Path: C:\WINNT\System32\DRIVERS\tcpip.sys
Address: 0xBD4AB000 Size: 323584 File Visible: - Signed: -
Status: -

Name: TDI.SYS
Image Path: C:\WINNT\System32\DRIVERS\TDI.SYS
Address: 0xEB8A4000 Size: 16384 File Visible: - Signed: -
Status: -

Name: uhcd.sys
Image Path: C:\WINNT\System32\DRIVERS\uhcd.sys
Address: 0xEB6C8000 Size: 32768 File Visible: - Signed: -
Status: -

Name: update.sys
Image Path: C:\WINNT\System32\DRIVERS\update.sys
Address: 0xBF61A000 Size: 176128 File Visible: - Signed: -
Status: -

Name: USBD.SYS
Image Path: C:\WINNT\System32\DRIVERS\USBD.SYS
Address: 0xEB6E0000 Size: 20480 File Visible: - Signed: -
Status: -

Name: usbehci.sys
Image Path: C:\WINNT\System32\DRIVERS\usbehci.sys
Address: 0xEB6F0000 Size: 20480 File Visible: - Signed: -
Status: -

Name: usbhub.sys
Image Path: C:\WINNT\System32\DRIVERS\usbhub.sys
Address: 0xEB4D0000 Size: 40960 File Visible: - Signed: -
Status: -

Name: usbhub20.sys
Image Path: C:\WINNT\System32\DRIVERS\usbhub20.sys
Address: 0xEB4E0000 Size: 53248 File Visible: - Signed: -
Status: -

Name: USBPORT.SYS
Image Path: C:\WINNT\System32\DRIVERS\USBPORT.SYS
Address: 0xBF7AB000 Size: 139264 File Visible: - Signed: -
Status: -

Name: vga.sys
Image Path: C:\WINNT\System32\drivers\vga.sys
Address: 0xEB8D8000 Size: 16384 File Visible: - Signed: -
Status: -

Name: viaagp1.sys
Image Path: viaagp1.sys
Address: 0xEB698000 Size: 28672 File Visible: - Signed: -
Status: -

Name: viaide.sys
Image Path: viaide.sys
Address: 0xEB904000 Size: 8192 File Visible: - Signed: -
Status: -

Name: viasraid.sys
Image Path: viasraid.sys
Address: 0xBFF70000 Size: 77824 File Visible: - Signed: -
Status: -

Name: VIDEOPRT.SYS
Image Path: C:\WINNT\system32\DRIVERS\VIDEOPRT.SYS
Address: 0xEB460000 Size: 53248 File Visible: - Signed: -
Status: -

Name: wanarp.sys
Image Path: C:\WINNT\System32\DRIVERS\wanarp.sys
Address: 0xEB708000 Size: 32768 File Visible: - Signed: -
Status: -

Name: wdmaud.sys
Image Path: C:\WINNT\system32\drivers\wdmaud.sys
Address: 0xBC9A4000 Size: 73728 File Visible: - Signed: -
Status: -

Name: win32k.sys
Image Path: C:\WINNT\system32\win32k.sys
Address: 0xA0000000 Size: 1646592 File Visible: - Signed: -
Status: -

Name: WMILIB.SYS
Image Path: C:\WINNT\System32\DRIVERS\WMILIB.SYS
Address: 0xEB9C8000 Size: 4096 File Visible: - Signed: -
Status: -

#9 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 72,760 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:02:52 PM

Posted 29 September 2009 - 07:39 PM

Hello,that log is corrupt. But you did get the other posted and they will clean this.
Now that your log is properly posted, 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 continue to ask for help elsewhere. Doing so can result in system changes which may not show it 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 very 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.

To avoid confusion, I am closing this topic.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users