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

Malwarebytes won't/open run after finding mutiplie infections and rebooting


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

#1 Ghostchase

Ghostchase

  • Members
  • 45 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 14 June 2011 - 01:23 PM

I just to start off with saying I'm a very resourceful person and when I come to these sort of things, I use google find what others having the same problem do. Anyways, I researched many articles on Google and tried my best to solve this problem on my own for 2 and a half days without any progress. Please if anyone could help me out here.

Windows XP Home SP3

Couple days ago Malware found a whole slew off things on my system only to reboot with my desktop in active recovery, suspecting a major problem ran it again only to get:

"Run-time error '372'

Failed to load 'vbalGrid' from vbalsgrid6.ocx. Your version of vbalgrid6.ocx may be outdated. Make sure your are using the version of control that was provided with your application"

After reading up on some topic that I found on this site about Rkill, I tried running Rkill to zap these processes that keep my Anti-virus and malware programs from starting, with only my desktop to flicker back to my original wallpaper for a couple seconds and then return to "active deskstop recovery"... AND MALWAREBYTES HAS YET TO RUN AT ALL WITHOUT THAT RUN-TIME ERROR.

Also tried going to Safe Mode, and trying Rkill and running programs with no such luck, but Norton could scan in Safe Mode but found nothing.

Used Kaspersky Online scan, and their TDSS Rootkit Removing tool (found a Rootkit I think and some other things) both found problems a "fixed and removed" these problems but still the system remains the same after many reboots. I forget to save the reports and write what I hell they found, sorry. That was a big mistake, since now both scans find nothing. (Can't copy and paste? won't work)

Please if anyone could help me outta this hole I'm in that would be great.

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,323 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:09:05 PM

Posted 22 June 2011 - 06:39 PM

Hello,Run-time error '372':Failed to load control 'vbalGrid' from vbalsgrid6.ocx. Your version of vbalsgrid6.ocx may be outdated. Make sure you are using the version of the control that was provided with your application.

Download MSFT Visual Basic from here
http://www.microsoft.com/downloads/details.aspx?familyid=9EF9BF70-DFE1-42A1-A4C8-39718C7E381D&displaylang=en

Instructions


Before starting the download, create a download directory on your computer. If your internet connection is less than 300K, it is recommended that you run the multi-part download by following the "More Information" link at the upper right, then clicking "Download Now."

Click "Download" to begin downloading the single download. When prompted by the download software, choose the option "Save this program to disk" and click OK. Then select the directory you created on your computer.

Run the file from the download directory. When prompted, select the same directory you created on your computer. You will be expanding the contents of the EXE into this directory.

Run SetupSP6.exe from the download directory. When you accept the terms of the electronic End User License Agreement (EULA) the setup software will replace the appropriate files in your Visual Basic 6.0 installation.




Reboot into Safe Mode with Networking
How to enter safe mode(XP/Vista)
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 with Networking using the arrow keys.
Then press enter on your keyboard to boot into Safe Mode
.


>>>> Download this file and doubleclick on it to run it. Allow the information to be merged with the registry.

RKill....

Download and Run RKill
  • Please download RKill by Grinler from one of the 4 links below and save it to your desktop.

    Link 1
    Link 2
    Link 3
    Link 4

  • Before we begin, you should disable your anti-malware softwares you have installed so they do not interfere RKill running as some anti-malware softwares detect RKill as malicious. Please refer to this page if you are not sure how.
  • Double-click on Rkill on your desktop to run it. (If you are using Windows Vista, please right-click on it and select Run As Administrator)
  • A black screen will appear and then disappear. Please do not worry, that is normal. This means that the tool has been successfully executed.
  • If nothing happens or if the tool does not run, please let me know in your next reply

Do not reboot your computer after running rkill as the malware programs will start again. Or if rebooting is required run it again.


If you continue having problems running rkill.com, you can download iExplore.exe or eXplorer.exe, which are renamed copies of rkill.com, and try them instead.



Next run Superantisypware (SAS):

Download and scan with SUPERAntiSpyware Free for Home Users
  • Double-click SUPERAntiSpyware.exe and use the default settings for installation.
  • An icon will be created on your desktop. Double-click that icon to launch the program.
  • If asked to update the program definitions, click "Yes". If not, update the definitions before scanning by selecting "Check for Updates". (If you encounter any problems while downloading the updates, manually download them from here. Double-click on the hyperlink for Download Installer and save SASDEFINITIONS.EXE to your desktop. Then double-click on SASDEFINITIONS.EXE to install the definitions.)
  • In the Main Menu, click the Preferences... button.
  • Click the Scanning Control tab.
  • 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.
  • Back on the main screen, under "Scan for Harmful Software" click Scan your computer.
  • On the left, make sure you check C:\Fixed Drive.
  • On the right, under "Complete Scan", choose Perform Complete Scan.
  • Click "Next" to start the scan. Please be patient while it scans your computer.
  • After the scan is complete, a Scan Summary box will appear with potentially harmful items that were detected. Click "OK".
  • Make sure everything has a checkmark next to it and click "Next".
  • A notification will appear that "Quarantine and Removal is Complete". Click "OK" and then click the "Finish" button to return to the main menu.
  • If asked if you want to reboot, click "Yes".
  • 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.
If you have a problem downloading, installing or getting SAS to run, try downloading and using the SUPERAntiSpyware Portable Scanner instead. Save the randomly named file (i.e. SAS_1710895.COM) to a usb drive or CD and transfer to the infected computer. Then double-click on it to launch and scan. The file is randomly named to help keep malware from blocking the scanner.


Now reboot to Normal and run MBAM (MalwareBytes):

Please download Malwarebytes Anti-Malware and save it to your desktop.
Download Link 1
Download Link 2MBAM 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.
    For instructions with screenshots, please refer to the How to use Malwarebytes' Anti-Malware Guide.
  • 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.

Troubleshoot Malwarebytes' Anti-Malware

Please ask any needed questions,post 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 Ghostchase

Ghostchase
  • Topic Starter

  • Members
  • 45 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 22 June 2011 - 10:03 PM

Thanks for the reply!

Damn, right off the bat I'm shot down.

"VS 6.0 SP was not completed successfully"

#4 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,323 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:09:05 PM

Posted 22 June 2011 - 10:06 PM

OK skip MBAM for now. Run RKill and SAS.

EDIT also post your TDSS log.
A log file named TDSSKiller_version_date_time_log.txt (i.e. TDSSKiller.2.4.0.0_27.07.2010_09.o7.26_log.txt) will be created and saved to the root directory (usually Local Disk C:).
Copy and paste the contents of that file in your next reply.


Do a search for vbalsgrid6.ocx and see if it's located elsewhere on the system.

Please make sure that you can view all hidden files. Instructions on how to do this can be found here:
How to see hidden files in Windows

Edited by boopme, 22 June 2011 - 10:11 PM.

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 Ghostchase

Ghostchase
  • Topic Starter

  • Members
  • 45 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 22 June 2011 - 10:36 PM

Ok. Rkill has been run and completed, but it stopped no processes.

SAS updated. Running complete scan with those items checked and the rest unchecked.

2011/06/12 13:12:34.0593 1396 TDSS rootkit removing tool 2.5.4.0 Jun 7 2011 17:31:48
2011/06/12 13:12:34.0875 1396 ================================================================================
2011/06/12 13:12:34.0875 1396 SystemInfo:
2011/06/12 13:12:34.0875 1396
2011/06/12 13:12:34.0875 1396 OS Version: 5.1.2600 ServicePack: 3.0
2011/06/12 13:12:34.0875 1396 Product type: Workstation
2011/06/12 13:12:34.0875 1396 ComputerName: TREVOR-3160C65A
2011/06/12 13:12:34.0875 1396 UserName: Trevor
2011/06/12 13:12:34.0875 1396 Windows directory: C:\WINDOWS
2011/06/12 13:12:34.0875 1396 System windows directory: C:\WINDOWS
2011/06/12 13:12:34.0875 1396 Processor architecture: Intel x86
2011/06/12 13:12:34.0875 1396 Number of processors: 1
2011/06/12 13:12:34.0875 1396 Page size: 0x1000
2011/06/12 13:12:34.0875 1396 Boot type: Normal boot
2011/06/12 13:12:34.0875 1396 ================================================================================
2011/06/12 13:12:35.0843 1396 Initialize success
2011/06/12 13:12:41.0359 1840 ================================================================================
2011/06/12 13:12:41.0359 1840 Scan started
2011/06/12 13:12:41.0359 1840 Mode: Manual;
2011/06/12 13:12:41.0359 1840 ================================================================================
2011/06/12 13:12:41.0687 1840 Aavmker4 (3f6884eff406238d39aaa892218f1df7) C:\WINDOWS\system32\drivers\Aavmker4.sys
2011/06/12 13:12:41.0843 1840 ACPI (8fd99680a539792a30e97944fdaecf17) C:\WINDOWS\system32\DRIVERS\ACPI.sys
2011/06/12 13:12:41.0921 1840 ACPIEC (9859c0f6936e723e4892d7141b1327d5) C:\WINDOWS\system32\drivers\ACPIEC.sys
2011/06/12 13:12:42.0015 1840 aec (8bed39e3c35d6a489438b8141717a557) C:\WINDOWS\system32\drivers\aec.sys
2011/06/12 13:12:42.0093 1840 AFD (7e775010ef291da96ad17ca4b17137d7) C:\WINDOWS\System32\drivers\afd.sys
2011/06/12 13:12:42.0359 1840 ALCXWDM (933933288df5ed26d1928215c97d05c7) C:\WINDOWS\system32\drivers\ALCXWDM.SYS
2011/06/12 13:12:42.0625 1840 ANIO (920298c7aef97d8168d219d35975d295) C:\WINDOWS\system32\ANIO.SYS
2011/06/12 13:12:42.0828 1840 ASPI (54ab078660e536da72b21a27f56b035b) C:\WINDOWS\System32\DRIVERS\ASPI32.sys
2011/06/12 13:12:42.0906 1840 asuskbnt (f984f8bba45745e77ee0fc8a425bd417) C:\WINDOWS\system32\drivers\atkkbnt.sys
2011/06/12 13:12:42.0968 1840 aswFsBlk (7f08d9c504b015d81a8abd75c80028c5) C:\WINDOWS\system32\drivers\aswFsBlk.sys
2011/06/12 13:12:43.0000 1840 aswMon2 (c2181ef6b54752273a0759a968c59279) C:\WINDOWS\system32\drivers\aswMon2.sys
2011/06/12 13:12:43.0078 1840 aswRdr (ac48bdd4cd5d44af33087c06d6e9511c) C:\WINDOWS\system32\drivers\aswRdr.sys
2011/06/12 13:12:43.0156 1840 aswSnx (b64134316fcd1f20e0f10ef3e65bd522) C:\WINDOWS\system32\drivers\aswSnx.sys
2011/06/12 13:12:43.0203 1840 aswSP (d6788e3211afa9951ed7a4d617f68a4f) C:\WINDOWS\system32\drivers\aswSP.sys
2011/06/12 13:12:43.0265 1840 aswTdi (4d100c45517809439c7b6dd98997fa00) C:\WINDOWS\system32\drivers\aswTdi.sys
2011/06/12 13:12:43.0328 1840 AsyncMac (b153affac761e7f5fcfa822b9c4e97bc) C:\WINDOWS\system32\DRIVERS\asyncmac.sys
2011/06/12 13:12:43.0375 1840 atapi (9f3a2f5aa6875c72bf062c712cfa2674) C:\WINDOWS\system32\DRIVERS\atapi.sys
2011/06/12 13:12:43.0484 1840 Atmarpc (9916c1225104ba14794209cfa8012159) C:\WINDOWS\system32\DRIVERS\atmarpc.sys
2011/06/12 13:12:43.0562 1840 audstub (d9f724aa26c010a217c97606b160ed68) C:\WINDOWS\system32\DRIVERS\audstub.sys
2011/06/12 13:12:43.0609 1840 Beep (da1f27d85e0d1525f6621372e7b685e9) C:\WINDOWS\system32\drivers\Beep.sys
2011/06/12 13:12:43.0765 1840 BHDrvx86 (76154fa6a742c613b44bb636b1a7c057) C:\WINDOWS\System32\Drivers\NIS\1008000.029\BHDrvx86.sys
2011/06/12 13:12:43.0953 1840 cbidf2k (90a673fc8e12a79afbed2576f6a7aaf9) C:\WINDOWS\system32\drivers\cbidf2k.sys
2011/06/12 13:12:44.0093 1840 ccHP (8973ff34b83572d867b5b928905ad5ac) C:\WINDOWS\System32\Drivers\NIS\1008000.029\ccHPx86.sys
2011/06/12 13:12:44.0218 1840 Cdaudio (c1b486a7658353d33a10cc15211a873b) C:\WINDOWS\system32\drivers\Cdaudio.sys
2011/06/12 13:12:44.0281 1840 Cdfs (c885b02847f5d2fd45a24e219ed93b32) C:\WINDOWS\system32\drivers\Cdfs.sys
2011/06/12 13:12:44.0375 1840 Cdrom (4b0a100eaf5c49ef3cca8c641431eacc) C:\WINDOWS\system32\DRIVERS\cdrom.sys
2011/06/12 13:12:45.0812 1840 cfltmgr (5d63eba4596e7f85064656eaedef103c) C:\DOCUME~1\Trevor\LOCALS~1\Temp\cfltmgr.sys
2011/06/12 13:12:46.0296 1840 Disk (044452051f3e02e7963599fc8f4f3e25) C:\WINDOWS\system32\DRIVERS\disk.sys
2011/06/12 13:12:46.0359 1840 dmboot (d992fe1274bde0f84ad826acae022a41) C:\WINDOWS\system32\drivers\dmboot.sys
2011/06/12 13:12:46.0468 1840 dmio (7c824cf7bbde77d95c08005717a95f6f) C:\WINDOWS\system32\drivers\dmio.sys
2011/06/12 13:12:46.0515 1840 dmload (e9317282a63ca4d188c0df5e09c6ac5f) C:\WINDOWS\system32\drivers\dmload.sys
2011/06/12 13:12:46.0578 1840 DMusic (8a208dfcf89792a484e76c40e5f50b45) C:\WINDOWS\system32\drivers\DMusic.sys
2011/06/12 13:12:46.0656 1840 drmkaud (8f5fcff8e8848afac920905fbd9d33c8) C:\WINDOWS\system32\drivers\drmkaud.sys
2011/06/12 13:12:46.0765 1840 eeCtrl (5461f01b7def17dc90d90b029f874c3b) C:\Program Files\Common Files\Symantec Shared\EENGINE\eeCtrl.sys
2011/06/12 13:12:46.0828 1840 EIO (59d74c7b787aa3dda0948986403cea55) C:\WINDOWS\system32\drivers\EIO.sys
2011/06/12 13:12:46.0906 1840 EraserUtilRebootDrv (17fcc372d03ba39f3aee85198c0ec594) C:\Program Files\Common Files\Symantec Shared\EENGINE\EraserUtilRebootDrv.sys
2011/06/12 13:12:47.0000 1840 Fastfat (38d332a6d56af32635675f132548343e) C:\WINDOWS\system32\drivers\Fastfat.sys
2011/06/12 13:12:47.0046 1840 Fdc (92cdd60b6730b9f50f6a1a0c1f8cdc81) C:\WINDOWS\system32\DRIVERS\fdc.sys
2011/06/12 13:12:47.0078 1840 Fips (d45926117eb9fa946a6af572fbe1caa3) C:\WINDOWS\system32\drivers\Fips.sys
2011/06/12 13:12:47.0156 1840 Flpydisk (9d27e7b80bfcdf1cdd9b555862d5e7f0) C:\WINDOWS\system32\DRIVERS\flpydisk.sys
2011/06/12 13:12:47.0234 1840 FltMgr (b2cf4b0786f8212cb92ed2b50c6db6b0) C:\WINDOWS\system32\drivers\fltmgr.sys
2011/06/12 13:12:47.0296 1840 FsVga (455f778ee14368468560bd7cb8c854d0) C:\WINDOWS\system32\DRIVERS\fsvga.sys
2011/06/12 13:12:47.0328 1840 Fs_Rec (3e1e2bd4f39b0e2b7dc4f4d2bcc2779a) C:\WINDOWS\system32\drivers\Fs_Rec.sys
2011/06/12 13:12:47.0375 1840 Ftdisk (6ac26732762483366c3969c9e4d2259d) C:\WINDOWS\system32\DRIVERS\ftdisk.sys
2011/06/12 13:12:48.0843 1840 gameenum (065639773d8b03f33577f6cdaea21063) C:\WINDOWS\system32\DRIVERS\gameenum.sys
2011/06/12 13:12:50.0281 1840 gatmarpc (5d63eba4596e7f85064656eaedef103c) C:\DOCUME~1\Trevor\LOCALS~1\Temp\gatmarpc.sys
2011/06/12 13:12:50.0281 1840 Suspicious file (Forged): C:\DOCUME~1\Trevor\LOCALS~1\Temp\gatmarpc.sys. Real md5: 5d63eba4596e7f85064656eaedef103c, Fake md5: c911a195060b81c9af5252726a42ccf7
2011/06/12 13:12:51.0515 1840 gatmarpc - detected ForgedFile.Multi.Generic (1)
2011/06/12 13:12:51.0656 1840 Gpc (0a02c63c8b144bd8c86b103dee7c86a2) C:\WINDOWS\system32\DRIVERS\msgpc.sys
2011/06/12 13:12:51.0734 1840 hidusb (ccf82c5ec8a7326c3066de870c06daf1) C:\WINDOWS\system32\DRIVERS\hidusb.sys
2011/06/12 13:12:51.0859 1840 HTTP (f80a415ef82cd06ffaf0d971528ead38) C:\WINDOWS\system32\Drivers\HTTP.sys
2011/06/12 13:12:52.0015 1840 i8042prt (4a0b06aa8943c1e332520f7440c0aa30) C:\WINDOWS\system32\DRIVERS\i8042prt.sys
2011/06/12 13:12:52.0187 1840 IDSxpx86 (b9ba869eb7b66c5740e904a79f9245b4) C:\Documents and Settings\All Users\Application Data\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\Norton\Definitions\ipsdefs\20110604.001\IDSxpx86.sys
2011/06/12 13:12:52.0234 1840 Imapi (083a052659f5310dd8b6a6cb05edcf8e) C:\WINDOWS\system32\DRIVERS\imapi.sys
2011/06/12 13:12:52.0343 1840 Ip6Fw (3bb22519a194418d5fec05d800a19ad0) C:\WINDOWS\system32\drivers\ip6fw.sys
2011/06/12 13:12:52.0437 1840 IpFilterDriver (731f22ba402ee4b62748adaf6363c182) C:\WINDOWS\system32\DRIVERS\ipfltdrv.sys
2011/06/12 13:12:52.0500 1840 IpInIp (b87ab476dcf76e72010632b5550955f5) C:\WINDOWS\system32\DRIVERS\ipinip.sys
2011/06/12 13:12:52.0546 1840 IpNat (cc748ea12c6effde940ee98098bf96bb) C:\WINDOWS\system32\DRIVERS\ipnat.sys
2011/06/12 13:12:52.0593 1840 IPSec (23c74d75e36e7158768dd63d92789a91) C:\WINDOWS\system32\DRIVERS\ipsec.sys
2011/06/12 13:12:52.0671 1840 IRENUM (c93c9ff7b04d772627a3646d89f7bf89) C:\WINDOWS\system32\DRIVERS\irenum.sys
2011/06/12 13:12:52.0734 1840 isapnp (05a299ec56e52649b1cf2fc52d20f2d7) C:\WINDOWS\system32\DRIVERS\isapnp.sys
2011/06/12 13:12:55.0515 1840 jrawwan (5d63eba4596e7f85064656eaedef103c) C:\DOCUME~1\Trevor\LOCALS~1\Temp\jrawwan.sys
2011/06/12 13:12:55.0531 1840 Suspicious file (Forged): C:\DOCUME~1\Trevor\LOCALS~1\Temp\jrawwan.sys. Real md5: 5d63eba4596e7f85064656eaedef103c, Fake md5: c911a195060b81c9af5252726a42ccf7
2011/06/12 13:12:56.0031 1840 jrawwan - detected ForgedFile.Multi.Generic (1)
2011/06/12 13:12:56.0156 1840 Kbdclass (463c1ec80cd17420a542b7f36a36f128) C:\WINDOWS\system32\DRIVERS\kbdclass.sys
2011/06/12 13:12:56.0218 1840 kmixer (692bcf44383d056aed41b045a323d378) C:\WINDOWS\system32\drivers\kmixer.sys
2011/06/12 13:12:56.0281 1840 KSecDD (b467646c54cc746128904e1654c750c1) C:\WINDOWS\system32\drivers\KSecDD.sys
2011/06/12 13:12:56.0343 1840 L6DP (cd83854b89bd69f86225d9fc086c1abf) C:\WINDOWS\system32\Drivers\l6dp.sys
2011/06/12 13:12:56.0421 1840 L6TPortB (585e0a1368a84d4fbedca77418a9f7f1) C:\WINDOWS\system32\Drivers\L6TPortB.sys
2011/06/12 13:12:56.0578 1840 MBAMSwissArmy (b309912717c29fc67e1ba4730a82b6dd) C:\WINDOWS\system32\drivers\mbamswissarmy.sys
2011/06/12 13:12:56.0671 1840 mnmdd (4ae068242760a1fb6e1a44bf4e16afa6) C:\WINDOWS\system32\drivers\mnmdd.sys
2011/06/12 13:12:56.0750 1840 Modem (dfcbad3cec1c5f964962ae10e0bcc8e1) C:\WINDOWS\system32\drivers\Modem.sys
2011/06/12 13:12:56.0796 1840 Mouclass (35c9e97194c8cfb8430125f8dbc34d04) C:\WINDOWS\system32\DRIVERS\mouclass.sys
2011/06/12 13:12:56.0843 1840 mouhid (b1c303e17fb9d46e87a98e4ba6769685) C:\WINDOWS\system32\DRIVERS\mouhid.sys
2011/06/12 13:12:56.0906 1840 MountMgr (a80b9a0bad1b73637dbcbba7df72d3fd) C:\WINDOWS\system32\drivers\MountMgr.sys
2011/06/12 13:12:56.0953 1840 MRxDAV (11d42bb6206f33fbb3ba0288d3ef81bd) C:\WINDOWS\system32\DRIVERS\mrxdav.sys
2011/06/12 13:12:57.0000 1840 MRxSmb (f3aefb11abc521122b67095044169e98) C:\WINDOWS\system32\DRIVERS\mrxsmb.sys
2011/06/12 13:12:57.0125 1840 Msfs (c941ea2454ba8350021d774daf0f1027) C:\WINDOWS\system32\drivers\Msfs.sys
2011/06/12 13:12:57.0234 1840 MSKSSRV (d1575e71568f4d9e14ca56b7b0453bf1) C:\WINDOWS\system32\drivers\MSKSSRV.sys
2011/06/12 13:12:57.0296 1840 MSPCLOCK (325bb26842fc7ccc1fcce2c457317f3e) C:\WINDOWS\system32\drivers\MSPCLOCK.sys
2011/06/12 13:12:57.0328 1840 MSPQM (bad59648ba099da4a17680b39730cb3d) C:\WINDOWS\system32\drivers\MSPQM.sys
2011/06/12 13:12:57.0375 1840 mssmbios (af5f4f3f14a8ea2c26de30f7a1e17136) C:\WINDOWS\system32\DRIVERS\mssmbios.sys
2011/06/12 13:12:57.0484 1840 ms_mpu401 (ca3e22598f411199adc2dfee76cd0ae0) C:\WINDOWS\system32\drivers\msmpu401.sys
2011/06/12 13:12:57.0546 1840 MTsensor (d48659bb24c48345d926ecb45c1ebdf5) C:\WINDOWS\system32\DRIVERS\ASACPI.sys
2011/06/12 13:12:57.0593 1840 Mup (2f625d11385b1a94360bfc70aaefdee1) C:\WINDOWS\system32\drivers\Mup.sys
2011/06/12 13:12:57.0843 1840 NAVENG (920d9701bba90dbb7ccfd3536ea4d6f9) C:\Documents and Settings\All Users\Application Data\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\Norton\Definitions\VirusDefs\20110611.006\NAVENG.SYS
2011/06/12 13:12:57.0921 1840 NAVEX15 (31b1a9b53c3319b97f7874347cd992d2) C:\Documents and Settings\All Users\Application Data\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\Norton\Definitions\VirusDefs\20110611.006\NAVEX15.SYS
2011/06/12 13:12:57.0984 1840 NDIS (1df7f42665c94b825322fae71721130d) C:\WINDOWS\system32\drivers\NDIS.sys
2011/06/12 13:12:58.0046 1840 NdisTapi (1ab3d00c991ab086e69db84b6c0ed78f) C:\WINDOWS\system32\DRIVERS\ndistapi.sys
2011/06/12 13:12:58.0093 1840 Ndisuio (f927a4434c5028758a842943ef1a3849) C:\WINDOWS\system32\DRIVERS\ndisuio.sys
2011/06/12 13:12:58.0140 1840 NdisWan (edc1531a49c80614b2cfda43ca8659ab) C:\WINDOWS\system32\DRIVERS\ndiswan.sys
2011/06/12 13:12:58.0187 1840 NDProxy (6215023940cfd3702b46abc304e1d45a) C:\WINDOWS\system32\drivers\NDProxy.sys
2011/06/12 13:12:58.0218 1840 NetBIOS (5d81cf9a2f1a3a756b66cf684911cdf0) C:\WINDOWS\system32\DRIVERS\netbios.sys
2011/06/12 13:12:58.0281 1840 NetBT (74b2b2f5bea5e9a3dc021d685551bd3d) C:\WINDOWS\system32\DRIVERS\netbt.sys
2011/06/12 13:12:58.0390 1840 Npfs (3182d64ae053d6fb034f44b6def8034a) C:\WINDOWS\system32\drivers\Npfs.sys
2011/06/12 13:12:58.0421 1840 Ntfs (78a08dd6a8d65e697c18e1db01c5cdca) C:\WINDOWS\system32\drivers\Ntfs.sys
2011/06/12 13:12:58.0500 1840 Null (73c1e1f395918bc2c6dd67af7591a3ad) C:\WINDOWS\system32\drivers\Null.sys
2011/06/12 13:12:58.0906 1840 nv (ed9816dbaf6689542ea7d022631906a1) C:\WINDOWS\system32\DRIVERS\nv4_mini.sys
2011/06/12 13:12:59.0296 1840 NVENETFD (720cc533eecb65553bd86b139ca04433) C:\WINDOWS\system32\DRIVERS\NVENETFD.sys
2011/06/12 13:12:59.0343 1840 nvnetbus (5f9f545cc5904dd8765f84ee1d056406) C:\WINDOWS\system32\DRIVERS\nvnetbus.sys
2011/06/12 13:12:59.0437 1840 NwlnkFlt (b305f3fad35083837ef46a0bbce2fc57) C:\WINDOWS\system32\DRIVERS\nwlnkflt.sys
2011/06/12 13:12:59.0500 1840 NwlnkFwd (c99b3415198d1aab7227f2c88fd664b9) C:\WINDOWS\system32\DRIVERS\nwlnkfwd.sys
2011/06/12 13:12:59.0593 1840 Parport (5575faf8f97ce5e713d108c2a58d7c7c) C:\WINDOWS\system32\DRIVERS\parport.sys
2011/06/12 13:12:59.0640 1840 PartMgr (beb3ba25197665d82ec7065b724171c6) C:\WINDOWS\system32\drivers\PartMgr.sys
2011/06/12 13:12:59.0703 1840 ParVdm (70e98b3fd8e963a6a46a2e6247e0bea1) C:\WINDOWS\system32\drivers\ParVdm.sys
2011/06/12 13:12:59.0796 1840 PCI (a219903ccf74233761d92bef471a07b1) C:\WINDOWS\system32\DRIVERS\pci.sys
2011/06/12 13:12:59.0890 1840 PCIIde (ccf5f451bb1a5a2a522a76e670000ff0) C:\WINDOWS\system32\DRIVERS\pciide.sys
2011/06/12 13:12:59.0968 1840 Pcmcia (9e89ef60e9ee05e3f2eef2da7397f1c1) C:\WINDOWS\system32\drivers\Pcmcia.sys
2011/06/12 13:13:00.0406 1840 pfc (da86016f0672ada925f589ede715f185) C:\WINDOWS\system32\drivers\pfc.sys
2011/06/12 13:13:00.0484 1840 PptpMiniport (efeec01b1d3cf84f16ddd24d9d9d8f99) C:\WINDOWS\system32\DRIVERS\raspptp.sys
2011/06/12 13:13:00.0515 1840 Processor (a32bebaf723557681bfc6bd93e98bd26) C:\WINDOWS\system32\DRIVERS\processr.sys
2011/06/12 13:13:00.0593 1840 PSched (09298ec810b07e5d582cb3a3f9255424) C:\WINDOWS\system32\DRIVERS\psched.sys
2011/06/12 13:13:00.0671 1840 Ptilink (80d317bd1c3dbc5d4fe7b1678c60cadd) C:\WINDOWS\system32\DRIVERS\ptilink.sys
2011/06/12 13:13:00.0781 1840 PxHelp20 (e42e3433dbb4cffe8fdd91eab29aea8e) C:\WINDOWS\system32\DRIVERS\PxHelp20.sys
2011/06/12 13:13:01.0015 1840 RasAcd (fe0d99d6f31e4fad8159f690d68ded9c) C:\WINDOWS\system32\DRIVERS\rasacd.sys
2011/06/12 13:13:01.0093 1840 Rasl2tp (11b4a627bc9614b885c4969bfa5ff8a6) C:\WINDOWS\system32\DRIVERS\rasl2tp.sys
2011/06/12 13:13:01.0140 1840 RasPppoe (5bc962f2654137c9909c3d4603587dee) C:\WINDOWS\system32\DRIVERS\raspppoe.sys
2011/06/12 13:13:01.0203 1840 Raspti (fdbb1d60066fcfbb7452fd8f9829b242) C:\WINDOWS\system32\DRIVERS\raspti.sys
2011/06/12 13:13:01.0312 1840 Rdbss (7ad224ad1a1437fe28d89cf22b17780a) C:\WINDOWS\system32\DRIVERS\rdbss.sys
2011/06/12 13:13:01.0359 1840 RDPCDD (4912d5b403614ce99c28420f75353332) C:\WINDOWS\system32\DRIVERS\RDPCDD.sys
2011/06/12 13:13:01.0406 1840 RDPWD (6728e45b66f93c08f11de2e316fc70dd) C:\WINDOWS\system32\drivers\RDPWD.sys
2011/06/12 13:13:01.0484 1840 redbook (f828dd7e1419b6653894a8f97a0094c5) C:\WINDOWS\system32\DRIVERS\redbook.sys
2011/06/12 13:13:01.0593 1840 rt2870 (4311d22a38f7e403475aa2c338768c11) C:\WINDOWS\system32\DRIVERS\rt2870.sys
2011/06/12 13:13:01.0671 1840 RT73 (cb20f16afdba63707fb971e0922edec1) C:\WINDOWS\system32\DRIVERS\Dr71WU.sys
2011/06/12 13:13:01.0765 1840 Secdrv (90a3935d05b494a5a39d37e71f09a677) C:\WINDOWS\system32\DRIVERS\secdrv.sys
2011/06/12 13:13:01.0843 1840 serenum (0f29512ccd6bead730039fb4bd2c85ce) C:\WINDOWS\system32\DRIVERS\serenum.sys
2011/06/12 13:13:01.0906 1840 Serial (cca207a8896d4c6a0c9ce29a4ae411a7) C:\WINDOWS\system32\DRIVERS\serial.sys
2011/06/12 13:13:02.0015 1840 Sfloppy (8e6b8c671615d126fdc553d1e2de5562) C:\WINDOWS\system32\drivers\Sfloppy.sys
2011/06/12 13:13:02.0078 1840 Sftfs (92d1002b9ace530f37f256d3d58e5867) C:\WINDOWS\system32\DRIVERS\Sftfsxp.sys
2011/06/12 13:13:02.0203 1840 Sftplay (5eb49d97a281c3e71b23c66b13a24a6d) C:\WINDOWS\system32\DRIVERS\Sftplayxp.sys
2011/06/12 13:13:02.0296 1840 Sftredir (e8192208cc8cf24b3a81774c8078259c) C:\WINDOWS\system32\DRIVERS\Sftredirxp.sys
2011/06/12 13:13:02.0343 1840 Sftvol (f21569a5e0f9e9cf6e32819e08abfa2d) C:\WINDOWS\system32\DRIVERS\Sftvolxp.sys
2011/06/12 13:13:02.0515 1840 splitter (ab8b92451ecb048a4d1de7c3ffcb4a9f) C:\WINDOWS\system32\drivers\splitter.sys
2011/06/12 13:13:02.0656 1840 sptd (71e276f6d189413266ea22171806597b) C:\WINDOWS\system32\Drivers\sptd.sys
2011/06/12 13:13:02.0656 1840 Suspicious file (NoAccess): C:\WINDOWS\system32\Drivers\sptd.sys. md5: 71e276f6d189413266ea22171806597b
2011/06/12 13:13:02.0671 1840 sptd - detected LockedFile.Multi.Generic (1)
2011/06/12 13:13:02.0718 1840 sr (76bb022c2fb6902fd5bdd4f78fc13a5d) C:\WINDOWS\system32\DRIVERS\sr.sys
2011/06/12 13:13:02.0890 1840 SRTSP (e81f6caeab9ad5732e94c07c97866aa2) C:\WINDOWS\System32\Drivers\NIS\1008000.029\SRTSP.SYS
2011/06/12 13:13:02.0921 1840 SRTSPX (e28de499d942b08058bffac69d4122b6) C:\WINDOWS\system32\drivers\NIS\1008000.029\SRTSPX.SYS
2011/06/12 13:13:02.0984 1840 Srv (89220b427890aa1dffd1a02648ae51c3) C:\WINDOWS\system32\DRIVERS\srv.sys
2011/06/12 13:13:04.0296 1840 susbcamd (5d63eba4596e7f85064656eaedef103c) C:\DOCUME~1\Trevor\LOCALS~1\Temp\susbcamd.sys
2011/06/12 13:13:04.0296 1840 Suspicious file (Forged): C:\DOCUME~1\Trevor\LOCALS~1\Temp\susbcamd.sys. Real md5: 5d63eba4596e7f85064656eaedef103c, Fake md5: c911a195060b81c9af5252726a42ccf7
2011/06/12 13:13:12.0921 1840 susbcamd - detected ForgedFile.Multi.Generic (1)
2011/06/12 13:13:13.0250 1840 swenum (3941d127aef12e93addf6fe6ee027e0f) C:\WINDOWS\system32\DRIVERS\swenum.sys
2011/06/12 13:13:13.0312 1840 swmidi (8ce882bcc6cf8a62f2b2323d95cb3d01) C:\WINDOWS\system32\drivers\swmidi.sys
2011/06/12 13:13:13.0531 1840 SymEFA (d0885f6e24259a6c65e68d6ad749910a) C:\WINDOWS\system32\drivers\NIS\1008000.029\SYMEFA.SYS
2011/06/12 13:13:13.0609 1840 SymEvent (a54ff04bd6e75dc4d8cb6f3e352635e0) C:\WINDOWS\system32\Drivers\SYMEVENT.SYS
2011/06/12 13:13:13.0640 1840 SYMFW (1e825026436c4eac3e1a11d1e9c33f2c) C:\WINDOWS\System32\Drivers\NIS\1008000.029\SYMFW.SYS
2011/06/12 13:13:13.0656 1840 SYMIDS (7a20b7d774ef0f16cf81b898bfeca772) C:\WINDOWS\System32\Drivers\NIS\1008000.029\SYMIDS.SYS
2011/06/12 13:13:13.0718 1840 SymIM (c6db9f873b09c63f5cb1de10c08bf6f9) C:\WINDOWS\system32\DRIVERS\SymIM.sys
2011/06/12 13:13:13.0734 1840 SymIMMP (c6db9f873b09c63f5cb1de10c08bf6f9) C:\WINDOWS\system32\DRIVERS\SymIM.sys
2011/06/12 13:13:13.0781 1840 SYMNDIS (5ab7d00ea6b7a6fcd5067c632ec6f039) C:\WINDOWS\System32\Drivers\NIS\1008000.029\SYMNDIS.SYS
2011/06/12 13:13:13.0828 1840 SYMTDI (e4fa8bbb96e314e9508865de1a767538) C:\WINDOWS\System32\Drivers\NIS\1008000.029\SYMTDI.SYS
2011/06/12 13:13:13.0953 1840 sysaudio (8b83f3ed0f1688b4958f77cd6d2bf290) C:\WINDOWS\system32\drivers\sysaudio.sys
2011/06/12 13:13:14.0046 1840 Tcpip (9aefa14bd6b182d61e3119fa5f436d3d) C:\WINDOWS\system32\DRIVERS\tcpip.sys
2011/06/12 13:13:14.0140 1840 TDPIPE (6471a66807f5e104e4885f5b67349397) C:\WINDOWS\system32\drivers\TDPIPE.sys
2011/06/12 13:13:14.0187 1840 TDTCP (c56b6d0402371cf3700eb322ef3aaf61) C:\WINDOWS\system32\drivers\TDTCP.sys
2011/06/12 13:13:14.0250 1840 TermDD (88155247177638048422893737429d9e) C:\WINDOWS\system32\DRIVERS\termdd.sys
2011/06/12 13:13:14.0359 1840 Udfs (5787b80c2e3c5e2f56c2a233d91fa2c9) C:\WINDOWS\system32\drivers\Udfs.sys
2011/06/12 13:13:14.0531 1840 Update (402ddc88356b1bac0ee3dd1580c76a31) C:\WINDOWS\system32\DRIVERS\update.sys
2011/06/12 13:13:14.0593 1840 usbaudio (e919708db44ed8543a7c017953148330) C:\WINDOWS\system32\drivers\usbaudio.sys
2011/06/12 13:13:14.0656 1840 usbccgp (173f317ce0db8e21322e71b7e60a27e8) C:\WINDOWS\system32\DRIVERS\usbccgp.sys
2011/06/12 13:13:14.0687 1840 usbehci (65dcf09d0e37d4c6b11b5b0b76d470a7) C:\WINDOWS\system32\DRIVERS\usbehci.sys
2011/06/12 13:13:14.0734 1840 usbhub (1ab3cdde553b6e064d2e754efe20285c) C:\WINDOWS\system32\DRIVERS\usbhub.sys
2011/06/12 13:13:14.0828 1840 usbohci (0daecce65366ea32b162f85f07c6753b) C:\WINDOWS\system32\DRIVERS\usbohci.sys
2011/06/12 13:13:14.0890 1840 usbprint (a717c8721046828520c9edf31288fc00) C:\WINDOWS\system32\DRIVERS\usbprint.sys
2011/06/12 13:13:14.0984 1840 usbscan (a0b8cf9deb1184fbdd20784a58fa75d4) C:\WINDOWS\system32\DRIVERS\usbscan.sys
2011/06/12 13:13:15.0046 1840 USBSTOR (a32426d9b14a089eaa1d922e0c5801a9) C:\WINDOWS\system32\DRIVERS\USBSTOR.SYS
2011/06/12 13:13:15.0109 1840 VgaSave (0d3a8fafceacd8b7625cd549757a7df1) C:\WINDOWS\System32\drivers\vga.sys
2011/06/12 13:13:16.0593 1840 vnmnt (5d63eba4596e7f85064656eaedef103c) C:\DOCUME~1\Trevor\LOCALS~1\Temp\vnmnt.sys
2011/06/12 13:13:16.0640 1840 Suspicious file (Forged): C:\DOCUME~1\Trevor\LOCALS~1\Temp\vnmnt.sys. Real md5: 5d63eba4596e7f85064656eaedef103c, Fake md5: c911a195060b81c9af5252726a42ccf7
2011/06/12 13:13:17.0234 1840 vnmnt - detected ForgedFile.Multi.Generic (1)
2011/06/12 13:13:17.0375 1840 VolSnap (4c8fcb5cc53aab716d810740fe59d025) C:\WINDOWS\system32\drivers\VolSnap.sys
2011/06/12 13:13:17.0484 1840 Wanarp (e20b95baedb550f32dd489265c1da1f6) C:\WINDOWS\system32\DRIVERS\wanarp.sys
2011/06/12 13:13:17.0562 1840 Wdf01000 (d918617b46457b9ac28027722e30f647) C:\WINDOWS\system32\DRIVERS\Wdf01000.sys
2011/06/12 13:13:17.0656 1840 wdmaud (6768acf64b18196494413695f0c3a00f) C:\WINDOWS\system32\drivers\wdmaud.sys
2011/06/12 13:13:17.0781 1840 WinUSB (fd600b032e741eb6aab509fc630f7c42) C:\WINDOWS\system32\DRIVERS\WinUSB.sys
2011/06/12 13:13:17.0890 1840 WpdUsb (cf4def1bf66f06964dc0d91844239104) C:\WINDOWS\system32\DRIVERS\wpdusb.sys
2011/06/12 13:13:17.0937 1840 WS2IFSL (6abe6e225adb5a751622a9cc3bc19ce8) C:\WINDOWS\System32\drivers\ws2ifsl.sys
2011/06/12 13:13:18.0062 1840 WudfPf (9140439d888d34b0e8df1d877b59b1b6) C:\WINDOWS\system32\DRIVERS\WudfPf.sys
2011/06/12 13:13:18.0062 1840 Suspicious file (Forged): C:\WINDOWS\system32\DRIVERS\WudfPf.sys. Real md5: 9140439d888d34b0e8df1d877b59b1b6, Fake md5: eaa6324f51214d2f6718977ec9ce0def
2011/06/12 13:13:18.0078 1840 WudfPf - detected Rootkit.Win32.TDSS.tdl3 (0)
2011/06/12 13:13:18.0109 1840 WudfRd (f91ff1e51fca30b3c3981db7d5924252) C:\WINDOWS\system32\DRIVERS\wudfrd.sys
2011/06/12 13:13:19.0468 1840 yacpiec (5d63eba4596e7f85064656eaedef103c) C:\DOCUME~1\Trevor\LOCALS~1\Temp\yacpiec.sys
2011/06/12 13:13:19.0484 1840 Suspicious file (Forged): C:\DOCUME~1\Trevor\LOCALS~1\Temp\yacpiec.sys. Real md5: 5d63eba4596e7f85064656eaedef103c, Fake md5: c911a195060b81c9af5252726a42ccf7
2011/06/12 13:13:20.0046 1840 yacpiec - detected ForgedFile.Multi.Generic (1)
2011/06/12 13:13:21.0453 1840 ydisk (5d63eba4596e7f85064656eaedef103c) C:\DOCUME~1\Trevor\LOCALS~1\Temp\ydisk.sys
2011/06/12 13:13:21.0687 1840 zumbus (6bfb54f73aae470e9299e66cbc7bb632) C:\WINDOWS\system32\DRIVERS\zumbus.sys
2011/06/12 13:13:21.0828 1840 MBR (0x1B8) (8f558eb6672622401da993e1e865c861) \Device\Harddisk0\DR0
2011/06/12 13:13:21.0968 1840 ================================================================================
2011/06/12 13:13:21.0968 1840 Scan finished
2011/06/12 13:13:21.0968 1840 ================================================================================
2011/06/12 13:13:21.0984 1392 Detected object count: 7
2011/06/12 13:13:21.0984 1392 Actual detected object count: 7
2011/06/12 13:14:14.0187 1392 gatmarpc (5d63eba4596e7f85064656eaedef103c) C:\DOCUME~1\Trevor\LOCALS~1\Temp\gatmarpc.sys
2011/06/12 13:14:14.0187 1392 Suspicious file (Forged): C:\DOCUME~1\Trevor\LOCALS~1\Temp\gatmarpc.sys. Real md5: 5d63eba4596e7f85064656eaedef103c, Fake md5: c911a195060b81c9af5252726a42ccf7
2011/06/12 13:14:14.0203 1392 C:\DOCUME~1\Trevor\LOCALS~1\Temp\gatmarpc.sys - copied to quarantine
2011/06/12 13:14:14.0265 1392 ForgedFile.Multi.Generic(gatmarpc) - User select action: Quarantine
2011/06/12 13:14:15.0640 1392 jrawwan (5d63eba4596e7f85064656eaedef103c) C:\DOCUME~1\Trevor\LOCALS~1\Temp\jrawwan.sys
2011/06/12 13:14:15.0640 1392 Suspicious file (Forged): C:\DOCUME~1\Trevor\LOCALS~1\Temp\jrawwan.sys. Real md5: 5d63eba4596e7f85064656eaedef103c, Fake md5: c911a195060b81c9af5252726a42ccf7
2011/06/12 13:14:15.0671 1392 C:\DOCUME~1\Trevor\LOCALS~1\Temp\jrawwan.sys - copied to quarantine
2011/06/12 13:14:15.0734 1392 ForgedFile.Multi.Generic(jrawwan) - User select action: Quarantine
2011/06/12 13:14:15.0937 1392 sptd (71e276f6d189413266ea22171806597b) C:\WINDOWS\system32\Drivers\sptd.sys
2011/06/12 13:14:15.0937 1392 Suspicious file (NoAccess): C:\WINDOWS\system32\Drivers\sptd.sys. md5: 71e276f6d189413266ea22171806597b
2011/06/12 13:14:15.0937 1392 C:\WINDOWS\system32\Drivers\sptd.sys - copied to quarantine
2011/06/12 13:14:15.0984 1392 LockedFile.Multi.Generic(sptd) - User select action: Quarantine
2011/06/12 13:14:17.0531 1392 susbcamd (5d63eba4596e7f85064656eaedef103c) C:\DOCUME~1\Trevor\LOCALS~1\Temp\susbcamd.sys
2011/06/12 13:14:17.0531 1392 Suspicious file (Forged): C:\DOCUME~1\Trevor\LOCALS~1\Temp\susbcamd.sys. Real md5: 5d63eba4596e7f85064656eaedef103c, Fake md5: c911a195060b81c9af5252726a42ccf7
2011/06/12 13:14:17.0562 1392 C:\DOCUME~1\Trevor\LOCALS~1\Temp\susbcamd.sys - copied to quarantine
2011/06/12 13:14:17.0609 1392 ForgedFile.Multi.Generic(susbcamd) - User select action: Quarantine
2011/06/12 13:14:19.0031 1392 vnmnt (5d63eba4596e7f85064656eaedef103c) C:\DOCUME~1\Trevor\LOCALS~1\Temp\vnmnt.sys
2011/06/12 13:14:19.0031 1392 Suspicious file (Forged): C:\DOCUME~1\Trevor\LOCALS~1\Temp\vnmnt.sys. Real md5: 5d63eba4596e7f85064656eaedef103c, Fake md5: c911a195060b81c9af5252726a42ccf7
2011/06/12 13:14:19.0078 1392 C:\DOCUME~1\Trevor\LOCALS~1\Temp\vnmnt.sys - copied to quarantine
2011/06/12 13:14:19.0125 1392 ForgedFile.Multi.Generic(vnmnt) - User select action: Quarantine
2011/06/12 13:14:19.0281 1392 WudfPf (9140439d888d34b0e8df1d877b59b1b6) C:\WINDOWS\system32\DRIVERS\WudfPf.sys
2011/06/12 13:14:19.0296 1392 Suspicious file (Forged): C:\WINDOWS\system32\DRIVERS\WudfPf.sys. Real md5: 9140439d888d34b0e8df1d877b59b1b6, Fake md5: eaa6324f51214d2f6718977ec9ce0def
2011/06/12 13:14:20.0687 1392 Backup copy not found, trying to cure infected file..
2011/06/12 13:14:20.0687 1392 Cure success, using it..
2011/06/12 13:14:20.0750 1392 C:\WINDOWS\system32\DRIVERS\WudfPf.sys - will be cured after reboot
2011/06/12 13:14:20.0750 1392 Rootkit.Win32.TDSS.tdl3(WudfPf) - User select action: Cure
2011/06/12 13:14:22.0156 1392 yacpiec (5d63eba4596e7f85064656eaedef103c) C:\DOCUME~1\Trevor\LOCALS~1\Temp\yacpiec.sys
2011/06/12 13:14:22.0156 1392 Suspicious file (Forged): C:\DOCUME~1\Trevor\LOCALS~1\Temp\yacpiec.sys. Real md5: 5d63eba4596e7f85064656eaedef103c, Fake md5: c911a195060b81c9af5252726a42ccf7
2011/06/12 13:14:22.0203 1392 C:\DOCUME~1\Trevor\LOCALS~1\Temp\yacpiec.sys - copied to quarantine
2011/06/12 13:14:22.0281 1392 ForgedFile.Multi.Generic(yacpiec) - User select action: Quarantine
2011/06/12 13:14:26.0921 1640 Deinitialize success

#6 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,323 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:09:05 PM

Posted 23 June 2011 - 11:28 AM

OK,good ,did SAS find anything more than tracking cookies?

If MBAM still doesn't run.

1. Uninstall Malwarebytes' Anti-Malware using Add/Remove programs in the control panel.
2. Restart your computer (very important).
3. Download and run this utility. Mbam clean
4. It will ask to restart your computer (please allow it to).
5. After the computer restarts, install the latest version from here. http://www.malwarebytes.org/mbam-download.php
Note: You will need to reactivate the program using the license you were sent.
Note: If using Free version, ignore the part about putting in your license key and activating.
Launch the program and set the Protection and Registration.
Then go to the UPDATE tab if not done during installation and check for updates.
Restart the computer again and verify that MBAM is in the task tray and run a Quick Scan and post that log.
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 Ghostchase

Ghostchase
  • Topic Starter

  • Members
  • 45 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 23 June 2011 - 11:54 AM

It found nothing expect one tracking cookie. The day I started this thread I scanned with SAS and found a hole slew off things, 12 total I think. But I decided after SAS didn't remove them after reboot, to uninstall SAS so the log went with it I guess.

#8 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,323 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:09:05 PM

Posted 23 June 2011 - 11:56 AM

Ok, well cookies we get them evert=y day . So I run and delete them monthly.
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

#9 Ghostchase

Ghostchase
  • Topic Starter

  • Members
  • 45 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 23 June 2011 - 12:08 PM

I delete about 30-45 tracking cookies every week. But yeah my first SAS scan found a whole slew of adware and trojans, it was a lot, it didn't remove them after reboot. My computer was still infected and MBAM wouldn't run.

Anyways trying MBAM clean.

#10 Ghostchase

Ghostchase
  • Topic Starter

  • Members
  • 45 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 23 June 2011 - 12:43 PM

I followed your instructions for the Mbam clean utility to the T. Nothing. Still Mbam has it's Run Time-Error and won't open.

#11 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,323 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:09:05 PM

Posted 23 June 2011 - 01:12 PM

Do a search for vbalsgrid6.ocx and see if it's located elsewhere on the system.

Please make sure that you can view all hidden files. Instructions on how to do this can be found here:
How to see hidden files in Windows

We will run SAS Again... You can uninstall it after we get a log.


If you have Spybot installed temporarily disable it.
Next run ATF and SAS:

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.

Edited by boopme, 23 June 2011 - 01:16 PM.

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

#12 Ghostchase

Ghostchase
  • Topic Starter

  • Members
  • 45 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 23 June 2011 - 04:07 PM

Whatever has latched onto my system has knocked many of Windows' abilities, opening/using "search" seems like one of them.

Trying ATF...

Edited by Ghostchase, 23 June 2011 - 04:07 PM.


#13 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,323 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:09:05 PM

Posted 23 June 2011 - 06:46 PM

Maybe it will be best and safest if we move to the Malware Renoval Team. Get a deep look and cleab this. Ir will take about 4 days for a reply but they will. Lets see if we can do this.

Please go here....
Preparation Guide ,do steps 6 - 9.

Create a DDS log and post it in the new topic explained in step 9,which is here Virus, Trojan, Spyware, and Malware Removal Logs and not in this topic,thanks.
If Gmer won't run,skip it and move on.
Let me know if that went well.
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

#14 Ghostchase

Ghostchase
  • Topic Starter

  • Members
  • 45 posts
  • OFFLINE
  •  
  • Local time:05:05 PM

Posted 24 June 2011 - 01:12 PM

Will do.

Anyways ATF + SAS ran and completed in Safe Mode, found nothing.

#15 Andrew

Andrew

    Bleepin' Night Watchman


  • Moderator
  • 8,259 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Right behind you
  • Local time:06:05 PM

Posted 25 June 2011 - 12:32 PM

Now that your log is properly posted here, 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 Malware Removal Team member, nor should you continue to ask for help elsewhere. Doing so can result in system changes which may not show it the logs 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 Malware Removal 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 Malware Removal Team members are very busy working logs posted before yours. They are volunteers who will help you out as soon as possible. Now that your log is posted and you are waiting, please DO NOT make another reply until it has been responded to by a member of the Malware Removal 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 Malware Removal Team member is already assisting you and not open the thread to respond.

To avoid confusion, I am closing this topic.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users