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

Infected with TrojanDownloader:Win32/Unruy.H


  • Please log in to reply
4 replies to this topic

#1 4est

4est

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:23 AM

Posted 15 December 2010 - 05:53 PM

Forum,

I have a laptop on my desk that is infected with Unruy.H

Windows Defender notices it about every 15 minutes. I've removed it over and over but it keeps coming back.
I've also scanned for it and removed it via MalwareBytes' Anti-Malware, with the same results (it keeps coming back)
Trend Micro Internet Security doesn't even seem to detect it...

I've searched Google and this forum for removal instructions, but still no joy...

Can anybody help me remove it or point me to instructions to remove it?

Thanks,
~4est

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,490 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:01:23 PM

Posted 15 December 2010 - 08:30 PM

Hello and welcome. I believe ESET does a good job on this.
Please perform a scan with Eset Online Antiivirus Scanner.
This scan requires Internet Explorer to work. Vista/Windows 7 users need to run Internet Explorer as Administrator.
To do this, right-click on the IE icon in the Start Menu or Quick Launch Bar on the Taskbar and select Run As Administrator from the context menu.
  • Click the green Posted Image button.
  • Read the End User License Agreement and check the box:
  • Check Posted Image.
  • Click the Posted Image button.
  • Accept any security warnings from your browser.
  • Check Posted Image
  • Check Remove found threats and Scan potentially unwanted applications. (If given the option, choose "Quarantine" instead of delete.)
  • Click the Start button.
  • ESET will then download updates for itself, install itself, and begin scanning your computer.
  • If offered the option to get information or buy software at any point, just close the window.
  • The scan will take a while so be patient and do NOT use the computer while the scan is running. Keep all other programs and windows closed.
  • When the scan completes, push Posted Image
  • Push Posted Image, and save the file to your desktop as ESETScan.txt.
  • Push the Posted Image button, then Finish.
  • Copy and paste the contents of ESETScan.txt in your next reply.
Note: A log.txt file will also be created and automatically saved in the C:\Program Files\EsetOnlineScanner\ folder.
If you did not save the ESETScan log, click Posted Image > Run..., then type or copy and paste everything in the code box below into the Open dialogue box:

C:\Program Files\ESET\EsetOnlineScanner\log.txt
  • Click Ok and the scan results will open in Notepad.
  • Copy and paste the contents of log.txt in your next reply.
-- Some online scanners will detect existing anti-virus software and refuse to cooperate. You may have to disable the real-time protection components of your existing anti-virus and try running the scan again. If you do this, remember to turn them back on after you are finished.

NOTE: In some instances if no malware is found there will be no log produced.



Rerun MBAM (MalwareBytes) like this:

Open MBAM in normal mode and click Update tab, select Check for Updates,when done
click Scanner tab,select Quick scan and scan (normal mode).
After scan click Remove Selected, Post new scan log and Reboot into normal mode.

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 4est

4est
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:23 AM

Posted 16 December 2010 - 06:39 PM

Thank You for helping!

I ran the ESET Online Scan according to instructions.
Here is that log...





C:\Documents and Settings\Owner\Application Data\Sun\Java\Deployment\cache\6.0\47\fa54f6f-3206f76d multiple threats deleted - quarantined
C:\Program Files\Common Files\Microsoft Shared\DW\dwtrig20.exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\HP\HP Software Update\HPWuSchd2.exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\iTunes\iTunesHelper.exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\Java\jre6\bin\jusched.exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask .exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\QuickTime\qttask.exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\Realtek\InstallShield\AzMixerSel.exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\Program Files\Trend Micro\Internet Security\UfSeAgnt.exe a variant of Win32/Injector.DTR trojan cleaned by deleting (after the next restart) - quarantined
C:\Program Files\Trend Micro\Internet Security\TMAS_OE\TMAS_OEMon.exe a variant of Win32/Injector.DTR trojan cleaned by deleting (after the next restart) - quarantined
C:\Program Files\Windows Defender\MSASCui.exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\WINDOWS\system32\HDAShCut.exe a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined
C:\WINDOWS\UMStor\Res.EXE a variant of Win32/Injector.DTR trojan cleaned by deleting - quarantined







I also ran MBAM according to instructions...
I couldn't get it to update via the initial update option or via the update tab. I manually downloaded the newest rules from http://data.mbamupdates.com/tools/mbam-rules.exe and installed it before running MBAM.
Here is that log...






Malwarebytes' Anti-Malware 1.50
www.malwarebytes.org

Database version: 5249

Windows 5.1.2600 Service Pack 3
Internet Explorer 8.0.6001.18702

12/16/2010 11:50:11 AM
mbam-log-2010-12-16 (11-50-11).txt

Scan type: Quick scan
Objects scanned: 155460
Time elapsed: 24 minute(s), 40 second(s)

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

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

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:
(No malicious items detected)







The PC appeared to be working because i'm not getting windows defender popping up but our corporate barracuda web filter detected Trojan.Tdss so i ran the Kaspersky TDSSKiller Rootkit remover and it found the rootkit on the system.
Here is that log...





2010/12/16 12:32:59.0343 TDSS rootkit removing tool 2.4.11.0 Dec 8 2010 14:46:40
2010/12/16 12:32:59.0343 ================================================================================
2010/12/16 12:32:59.0343 SystemInfo:
2010/12/16 12:32:59.0343
2010/12/16 12:32:59.0343 OS Version: 5.1.2600 ServicePack: 3.0
2010/12/16 12:32:59.0343 Product type: Workstation
2010/12/16 12:32:59.0343 ComputerName: NAME-B2436390A2
2010/12/16 12:32:59.0343 UserName: Owner
2010/12/16 12:32:59.0343 Windows directory: C:\WINDOWS
2010/12/16 12:32:59.0343 System windows directory: C:\WINDOWS
2010/12/16 12:32:59.0343 Processor architecture: Intel x86
2010/12/16 12:32:59.0343 Number of processors: 1
2010/12/16 12:32:59.0343 Page size: 0x1000
2010/12/16 12:32:59.0343 Boot type: Normal boot
2010/12/16 12:32:59.0343 ================================================================================
2010/12/16 12:32:59.0843 Initialize success
2010/12/16 12:33:05.0000 ================================================================================
2010/12/16 12:33:05.0000 Scan started
2010/12/16 12:33:05.0000 Mode: Manual;
2010/12/16 12:33:05.0000 ================================================================================
2010/12/16 12:33:07.0203 ACPI (8fd99680a539792a30e97944fdaecf17) C:\WINDOWS\system32\DRIVERS\ACPI.sys
2010/12/16 12:33:07.0250 ACPIEC (9859c0f6936e723e4892d7141b1327d5) C:\WINDOWS\system32\DRIVERS\ACPIEC.sys
2010/12/16 12:33:07.0375 aec (8bed39e3c35d6a489438b8141717a557) C:\WINDOWS\system32\drivers\aec.sys
2010/12/16 12:33:07.0500 AegisP (023867b6606fbabcdd52e089c4a507da) C:\WINDOWS\system32\DRIVERS\AegisP.sys
2010/12/16 12:33:07.0625 AFD (7e775010ef291da96ad17ca4b17137d7) C:\WINDOWS\System32\drivers\afd.sys
2010/12/16 12:33:07.0906 Arp1394 (b5b8a80875c1dededa8b02765642c32f) C:\WINDOWS\system32\DRIVERS\arp1394.sys
2010/12/16 12:33:08.0109 AsyncMac (b153affac761e7f5fcfa822b9c4e97bc) C:\WINDOWS\system32\DRIVERS\asyncmac.sys
2010/12/16 12:33:08.0171 atapi (9f3a2f5aa6875c72bf062c712cfa2674) C:\WINDOWS\system32\DRIVERS\atapi.sys
2010/12/16 12:33:08.0250 Atmarpc (9916c1225104ba14794209cfa8012159) C:\WINDOWS\system32\DRIVERS\atmarpc.sys
2010/12/16 12:33:08.0343 audstub (d9f724aa26c010a217c97606b160ed68) C:\WINDOWS\system32\DRIVERS\audstub.sys
2010/12/16 12:33:08.0484 Beep (da1f27d85e0d1525f6621372e7b685e9) C:\WINDOWS\system32\drivers\Beep.sys
2010/12/16 12:33:08.0640 Cam5603D (273daec27d2aaddc0e7918c35ffa15e3) C:\WINDOWS\system32\Drivers\BisonCam.sys
2010/12/16 12:33:08.0890 cbidf2k (90a673fc8e12a79afbed2576f6a7aaf9) C:\WINDOWS\system32\drivers\cbidf2k.sys
2010/12/16 12:33:08.0968 CCDECODE (0be5aef125be881c4f854c554f2b025c) C:\WINDOWS\system32\DRIVERS\CCDECODE.sys
2010/12/16 12:33:09.0078 Cdaudio (c1b486a7658353d33a10cc15211a873b) C:\WINDOWS\system32\drivers\Cdaudio.sys
2010/12/16 12:33:09.0140 Cdfs (c885b02847f5d2fd45a24e219ed93b32) C:\WINDOWS\system32\drivers\Cdfs.sys
2010/12/16 12:33:09.0218 Cdrom (1f4260cc5b42272d71f79e570a27a4fe) C:\WINDOWS\system32\DRIVERS\cdrom.sys
2010/12/16 12:33:09.0343 CmBatt (0f6c187d38d98f8df904589a5f94d411) C:\WINDOWS\system32\DRIVERS\CmBatt.sys
2010/12/16 12:33:09.0406 Compbatt (6e4c9f21f0fae8940661144f41b13203) C:\WINDOWS\system32\DRIVERS\compbatt.sys
2010/12/16 12:33:09.0531 Disk (044452051f3e02e7963599fc8f4f3e25) C:\WINDOWS\system32\DRIVERS\disk.sys
2010/12/16 12:33:09.0609 dmboot (d992fe1274bde0f84ad826acae022a41) C:\WINDOWS\system32\drivers\dmboot.sys
2010/12/16 12:33:09.0750 dmio (7c824cf7bbde77d95c08005717a95f6f) C:\WINDOWS\system32\drivers\dmio.sys
2010/12/16 12:33:09.0812 dmload (e9317282a63ca4d188c0df5e09c6ac5f) C:\WINDOWS\system32\drivers\dmload.sys
2010/12/16 12:33:09.0875 DMusic (8a208dfcf89792a484e76c40e5f50b45) C:\WINDOWS\system32\drivers\DMusic.sys
2010/12/16 12:33:09.0953 drmkaud (8f5fcff8e8848afac920905fbd9d33c8) C:\WINDOWS\system32\drivers\drmkaud.sys
2010/12/16 12:33:10.0031 EMSCR (2c11a51d541b22b0494c5bae19a9a674) C:\WINDOWS\system32\DRIVERS\EMS7SK.sys
2010/12/16 12:33:10.0109 ESDCR (2da0d2dda536670969584911c0a517dd) C:\WINDOWS\system32\DRIVERS\ESD7SK.sys
2010/12/16 12:33:10.0187 Fastfat (38d332a6d56af32635675f132548343e) C:\WINDOWS\system32\drivers\Fastfat.sys
2010/12/16 12:33:10.0234 Fdc (92cdd60b6730b9f50f6a1a0c1f8cdc81) C:\WINDOWS\system32\drivers\Fdc.sys
2010/12/16 12:33:10.0296 Fips (d45926117eb9fa946a6af572fbe1caa3) C:\WINDOWS\system32\drivers\Fips.sys
2010/12/16 12:33:10.0359 Flpydisk (9d27e7b80bfcdf1cdd9b555862d5e7f0) C:\WINDOWS\system32\drivers\Flpydisk.sys
2010/12/16 12:33:10.0453 FltMgr (b2cf4b0786f8212cb92ed2b50c6db6b0) C:\WINDOWS\system32\drivers\fltmgr.sys
2010/12/16 12:33:10.0515 Fs_Rec (3e1e2bd4f39b0e2b7dc4f4d2bcc2779a) C:\WINDOWS\system32\drivers\Fs_Rec.sys
2010/12/16 12:33:10.0578 Ftdisk (6ac26732762483366c3969c9e4d2259d) C:\WINDOWS\system32\DRIVERS\ftdisk.sys
2010/12/16 12:33:10.0671 GEARAspiWDM (8182ff89c65e4d38b2de4bb0fb18564e) C:\WINDOWS\system32\DRIVERS\GEARAspiWDM.sys
2010/12/16 12:33:10.0718 Gpc (0a02c63c8b144bd8c86b103dee7c86a2) C:\WINDOWS\system32\DRIVERS\msgpc.sys
2010/12/16 12:33:10.0796 HdAudAddService (2a013e7530beab6e569faa83f517e836) C:\WINDOWS\system32\drivers\HdAudio.sys
2010/12/16 12:33:10.0875 HDAudBus (573c7d0a32852b48f3058cfd8026f511) C:\WINDOWS\system32\DRIVERS\HDAudBus.sys
2010/12/16 12:33:10.0953 HidUsb (ccf82c5ec8a7326c3066de870c06daf1) C:\WINDOWS\system32\DRIVERS\hidusb.sys
2010/12/16 12:33:11.0093 HPZid412 (5faba4775d4c61e55ec669d643ffc71f) C:\WINDOWS\system32\DRIVERS\HPZid412.sys
2010/12/16 12:33:11.0218 HPZipr12 (a3c43980ee1f1beac778b44ea65dbdd4) C:\WINDOWS\system32\DRIVERS\HPZipr12.sys
2010/12/16 12:33:11.0312 HPZius12 (2906949bd4e206f2bb0dd1896ce9f66f) C:\WINDOWS\system32\DRIVERS\HPZius12.sys
2010/12/16 12:33:11.0437 HTTP (f80a415ef82cd06ffaf0d971528ead38) C:\WINDOWS\system32\Drivers\HTTP.sys
2010/12/16 12:33:11.0578 i8042prt (4a0b06aa8943c1e332520f7440c0aa30) C:\WINDOWS\system32\DRIVERS\i8042prt.sys
2010/12/16 12:33:11.0781 ialm (737da0be27652c4482ac5cde099bfce9) C:\WINDOWS\system32\DRIVERS\ialmnt5.sys
2010/12/16 12:33:11.0953 Imapi (083a052659f5310dd8b6a6cb05edcf8e) C:\WINDOWS\system32\DRIVERS\imapi.sys
2010/12/16 12:33:12.0375 IntcAzAudAddService (a30685283f90ae02f1cd50972c6065e3) C:\WINDOWS\system32\drivers\RtkHDAud.sys
2010/12/16 12:33:12.0843 IntelIde (b5466a9250342a7aa0cd1fba13420678) C:\WINDOWS\system32\DRIVERS\intelide.sys
2010/12/16 12:33:12.0953 intelppm (8c953733d8f36eb2133f5bb58808b66b) C:\WINDOWS\system32\DRIVERS\intelppm.sys
2010/12/16 12:33:13.0000 Ip6Fw (3bb22519a194418d5fec05d800a19ad0) C:\WINDOWS\system32\drivers\ip6fw.sys
2010/12/16 12:33:13.0109 IpFilterDriver (731f22ba402ee4b62748adaf6363c182) C:\WINDOWS\system32\DRIVERS\ipfltdrv.sys
2010/12/16 12:33:13.0171 IpInIp (b87ab476dcf76e72010632b5550955f5) C:\WINDOWS\system32\DRIVERS\ipinip.sys
2010/12/16 12:33:13.0250 IpNat (cc748ea12c6effde940ee98098bf96bb) C:\WINDOWS\system32\DRIVERS\ipnat.sys
2010/12/16 12:33:13.0328 IPSec (23c74d75e36e7158768dd63d92789a91) C:\WINDOWS\system32\DRIVERS\ipsec.sys
2010/12/16 12:33:13.0437 IRENUM (c93c9ff7b04d772627a3646d89f7bf89) C:\WINDOWS\system32\DRIVERS\irenum.sys
2010/12/16 12:33:13.0484 isapnp (05a299ec56e52649b1cf2fc52d20f2d7) C:\WINDOWS\system32\DRIVERS\isapnp.sys
2010/12/16 12:33:13.0609 Kbdclass (463c1ec80cd17420a542b7f36a36f128) C:\WINDOWS\system32\DRIVERS\kbdclass.sys
2010/12/16 12:33:13.0703 kbdhid (9ef487a186dea361aa06913a75b3fa99) C:\WINDOWS\system32\DRIVERS\kbdhid.sys
2010/12/16 12:33:13.0781 kmixer (692bcf44383d056aed41b045a323d378) C:\WINDOWS\system32\drivers\kmixer.sys
2010/12/16 12:33:13.0859 KSecDD (b467646c54cc746128904e1654c750c1) C:\WINDOWS\system32\drivers\KSecDD.sys
2010/12/16 12:33:13.0953 Ktp (475a6af6ba5e060981a9f9fe284f45ab) C:\WINDOWS\system32\DRIVERS\Ktp.sys
2010/12/16 12:33:14.0078 mnmdd (4ae068242760a1fb6e1a44bf4e16afa6) C:\WINDOWS\system32\drivers\mnmdd.sys
2010/12/16 12:33:14.0156 Modem (dfcbad3cec1c5f964962ae10e0bcc8e1) C:\WINDOWS\system32\drivers\Modem.sys
2010/12/16 12:33:14.0187 Mouclass (35c9e97194c8cfb8430125f8dbc34d04) C:\WINDOWS\system32\DRIVERS\mouclass.sys
2010/12/16 12:33:14.0296 mouhid (b1c303e17fb9d46e87a98e4ba6769685) C:\WINDOWS\system32\DRIVERS\mouhid.sys
2010/12/16 12:33:14.0406 MountMgr (a80b9a0bad1b73637dbcbba7df72d3fd) C:\WINDOWS\system32\drivers\MountMgr.sys
2010/12/16 12:33:14.0515 MRxDAV (11d42bb6206f33fbb3ba0288d3ef81bd) C:\WINDOWS\system32\DRIVERS\mrxdav.sys
2010/12/16 12:33:14.0671 MRxSmb (f3aefb11abc521122b67095044169e98) C:\WINDOWS\system32\DRIVERS\mrxsmb.sys
2010/12/16 12:33:14.0781 Msfs (c941ea2454ba8350021d774daf0f1027) C:\WINDOWS\system32\drivers\Msfs.sys
2010/12/16 12:33:14.0875 MSKSSRV (d1575e71568f4d9e14ca56b7b0453bf1) C:\WINDOWS\system32\drivers\MSKSSRV.sys
2010/12/16 12:33:14.0968 MSPCLOCK (325bb26842fc7ccc1fcce2c457317f3e) C:\WINDOWS\system32\drivers\MSPCLOCK.sys
2010/12/16 12:33:15.0031 MSPQM (bad59648ba099da4a17680b39730cb3d) C:\WINDOWS\system32\drivers\MSPQM.sys
2010/12/16 12:33:15.0125 mssmbios (af5f4f3f14a8ea2c26de30f7a1e17136) C:\WINDOWS\system32\DRIVERS\mssmbios.sys
2010/12/16 12:33:15.0187 MSTEE (e53736a9e30c45fa9e7b5eac55056d1d) C:\WINDOWS\system32\drivers\MSTEE.sys
2010/12/16 12:33:15.0234 Mup (2f625d11385b1a94360bfc70aaefdee1) C:\WINDOWS\system32\drivers\Mup.sys
2010/12/16 12:33:15.0328 NABTSFEC (5b50f1b2a2ed47d560577b221da734db) C:\WINDOWS\system32\DRIVERS\NABTSFEC.sys
2010/12/16 12:33:15.0453 NDIS (1df7f42665c94b825322fae71721130d) C:\WINDOWS\system32\drivers\NDIS.sys
2010/12/16 12:33:15.0546 NdisIP (7ff1f1fd8609c149aa432f95a8163d97) C:\WINDOWS\system32\DRIVERS\NdisIP.sys
2010/12/16 12:33:15.0609 NdisTapi (1ab3d00c991ab086e69db84b6c0ed78f) C:\WINDOWS\system32\DRIVERS\ndistapi.sys
2010/12/16 12:33:15.0671 Ndisuio (f927a4434c5028758a842943ef1a3849) C:\WINDOWS\system32\DRIVERS\ndisuio.sys
2010/12/16 12:33:15.0750 NdisWan (edc1531a49c80614b2cfda43ca8659ab) C:\WINDOWS\system32\DRIVERS\ndiswan.sys
2010/12/16 12:33:15.0812 NDProxy (6215023940cfd3702b46abc304e1d45a) C:\WINDOWS\system32\drivers\NDProxy.sys
2010/12/16 12:33:15.0843 NetBIOS (5d81cf9a2f1a3a756b66cf684911cdf0) C:\WINDOWS\system32\DRIVERS\netbios.sys
2010/12/16 12:33:15.0906 NetBT (74b2b2f5bea5e9a3dc021d685551bd3d) C:\WINDOWS\system32\DRIVERS\netbt.sys
2010/12/16 12:33:15.0984 NIC1394 (e9e47cfb2d461fa0fc75b7a74c6383ea) C:\WINDOWS\system32\DRIVERS\nic1394.sys
2010/12/16 12:33:16.0078 Npfs (3182d64ae053d6fb034f44b6def8034a) C:\WINDOWS\system32\drivers\Npfs.sys
2010/12/16 12:33:16.0156 Ntfs (78a08dd6a8d65e697c18e1db01c5cdca) C:\WINDOWS\system32\drivers\Ntfs.sys
2010/12/16 12:33:16.0281 Null (73c1e1f395918bc2c6dd67af7591a3ad) C:\WINDOWS\system32\drivers\Null.sys
2010/12/16 12:33:16.0343 NWADI (0973c0c696780161f4526586d5eac422) C:\WINDOWS\system32\DRIVERS\NWADIenum.sys
2010/12/16 12:33:16.0421 NwlnkFlt (b305f3fad35083837ef46a0bbce2fc57) C:\WINDOWS\system32\DRIVERS\nwlnkflt.sys
2010/12/16 12:33:16.0484 NwlnkFwd (c99b3415198d1aab7227f2c88fd664b9) C:\WINDOWS\system32\DRIVERS\nwlnkfwd.sys
2010/12/16 12:33:16.0578 NWUSBModem (65b471bb7e57c416a1e685ec07d4abfa) C:\WINDOWS\system32\DRIVERS\nwusbmdm.sys
2010/12/16 12:33:16.0656 NWUSBPort (65b471bb7e57c416a1e685ec07d4abfa) C:\WINDOWS\system32\DRIVERS\nwusbser.sys
2010/12/16 12:33:16.0750 NWUSBPort2 (65b471bb7e57c416a1e685ec07d4abfa) C:\WINDOWS\system32\DRIVERS\nwusbser2.sys
2010/12/16 12:33:16.0812 ohci1394 (ca33832df41afb202ee7aeb05145922f) C:\WINDOWS\system32\DRIVERS\ohci1394.sys
2010/12/16 12:33:16.0875 Parport (5575faf8f97ce5e713d108c2a58d7c7c) C:\WINDOWS\system32\drivers\Parport.sys
2010/12/16 12:33:16.0937 PartMgr (beb3ba25197665d82ec7065b724171c6) C:\WINDOWS\system32\drivers\PartMgr.sys
2010/12/16 12:33:17.0015 ParVdm (70e98b3fd8e963a6a46a2e6247e0bea1) C:\WINDOWS\system32\drivers\ParVdm.sys
2010/12/16 12:33:17.0109 PCASp50 (1961590aa191b6b7dcf18a6a693af7b8) C:\WINDOWS\system32\Drivers\PCASp50.sys
2010/12/16 12:33:17.0203 PCI (a219903ccf74233761d92bef471a07b1) C:\WINDOWS\system32\DRIVERS\pci.sys
2010/12/16 12:33:17.0328 PCIIde (ccf5f451bb1a5a2a522a76e670000ff0) C:\WINDOWS\system32\DRIVERS\pciide.sys
2010/12/16 12:33:17.0406 Pcmcia (9e89ef60e9ee05e3f2eef2da7397f1c1) C:\WINDOWS\system32\DRIVERS\pcmcia.sys
2010/12/16 12:33:17.0750 PptpMiniport (efeec01b1d3cf84f16ddd24d9d9d8f99) C:\WINDOWS\system32\DRIVERS\raspptp.sys
2010/12/16 12:33:17.0828 PSched (09298ec810b07e5d582cb3a3f9255424) C:\WINDOWS\system32\DRIVERS\psched.sys
2010/12/16 12:33:17.0906 Ptilink (80d317bd1c3dbc5d4fe7b1678c60cadd) C:\WINDOWS\system32\DRIVERS\ptilink.sys
2010/12/16 12:33:17.0968 PxHelp20 (db3b30c3a4cdcf07e164c14584d9d0f2) C:\WINDOWS\system32\Drivers\PxHelp20.sys
2010/12/16 12:33:18.0125 RasAcd (fe0d99d6f31e4fad8159f690d68ded9c) C:\WINDOWS\system32\DRIVERS\rasacd.sys
2010/12/16 12:33:18.0171 Rasl2tp (11b4a627bc9614b885c4969bfa5ff8a6) C:\WINDOWS\system32\DRIVERS\rasl2tp.sys
2010/12/16 12:33:18.0218 RasPppoe (5bc962f2654137c9909c3d4603587dee) C:\WINDOWS\system32\DRIVERS\raspppoe.sys
2010/12/16 12:33:18.0265 Raspti (fdbb1d60066fcfbb7452fd8f9829b242) C:\WINDOWS\system32\DRIVERS\raspti.sys
2010/12/16 12:33:18.0328 Rdbss (7ad224ad1a1437fe28d89cf22b17780a) C:\WINDOWS\system32\DRIVERS\rdbss.sys
2010/12/16 12:33:18.0375 RDPCDD (4912d5b403614ce99c28420f75353332) C:\WINDOWS\system32\DRIVERS\RDPCDD.sys
2010/12/16 12:33:18.0453 RDPWD (6728e45b66f93c08f11de2e316fc70dd) C:\WINDOWS\system32\drivers\RDPWD.sys
2010/12/16 12:33:18.0531 redbook (f828dd7e1419b6653894a8f97a0094c5) C:\WINDOWS\system32\DRIVERS\redbook.sys
2010/12/16 12:33:18.0625 RimVSerPort (d9b34325ee5df78b8f28a3de9f577c7d) C:\WINDOWS\system32\DRIVERS\RimSerial.sys
2010/12/16 12:33:18.0781 ROOTMODEM (d8b0b4ade32574b2d9c5cc34dc0dbbe7) C:\WINDOWS\system32\Drivers\RootMdm.sys
2010/12/16 12:33:18.0953 rt2870 (19a0b57164830df3c699e3cc93f68e37) C:\WINDOWS\system32\DRIVERS\rt2870.sys
2010/12/16 12:33:19.0140 RTL8023xp (69ee1e8dc0c750a5d03739e6e9429959) C:\WINDOWS\system32\DRIVERS\Rtnicxp.sys
2010/12/16 12:33:19.0281 sdbus (8d04819a3ce51b9eb47e5689b44d43c4) C:\WINDOWS\system32\DRIVERS\sdbus.sys
2010/12/16 12:33:19.0375 Secdrv (90a3935d05b494a5a39d37e71f09a677) C:\WINDOWS\system32\DRIVERS\secdrv.sys
2010/12/16 12:33:19.0484 Serial (cca207a8896d4c6a0c9ce29a4ae411a7) C:\WINDOWS\system32\drivers\Serial.sys
2010/12/16 12:33:19.0593 Sfloppy (8e6b8c671615d126fdc553d1e2de5562) C:\WINDOWS\system32\drivers\Sfloppy.sys
2010/12/16 12:33:19.0718 SLIP (866d538ebe33709a5c9f5c62b73b7d14) C:\WINDOWS\system32\DRIVERS\SLIP.sys
2010/12/16 12:33:19.0875 smserial (2a88b1286305eb6df1c053d39f88185c) C:\WINDOWS\system32\DRIVERS\smserial.sys
2010/12/16 12:33:20.0218 splitter (ab8b92451ecb048a4d1de7c3ffcb4a9f) C:\WINDOWS\system32\drivers\splitter.sys
2010/12/16 12:33:20.0281 sr (76bb022c2fb6902fd5bdd4f78fc13a5d) C:\WINDOWS\system32\DRIVERS\sr.sys
2010/12/16 12:33:20.0359 Srv (0f6aefad3641a657e18081f52d0c15af) C:\WINDOWS\system32\DRIVERS\srv.sys
2010/12/16 12:33:20.0421 streamip (77813007ba6265c4b6098187e6ed79d2) C:\WINDOWS\system32\DRIVERS\StreamIP.sys
2010/12/16 12:33:20.0484 swenum (3941d127aef12e93addf6fe6ee027e0f) C:\WINDOWS\system32\DRIVERS\swenum.sys
2010/12/16 12:33:20.0546 swmidi (8ce882bcc6cf8a62f2b2323d95cb3d01) C:\WINDOWS\system32\drivers\swmidi.sys
2010/12/16 12:33:20.0625 swmsflt (e6c797b33a454840245c0c96e7f08b0a) C:\WINDOWS\System32\drivers\swmsflt.sys
2010/12/16 12:33:20.0734 swmx00 (5d3c9f767eaded3e14fa4ce6cf9f7725) C:\WINDOWS\system32\DRIVERS\swmx00.sys
2010/12/16 12:33:20.0812 SWNC5E00 (e0919389fb29ed5c03b0b664236abe50) C:\WINDOWS\system32\DRIVERS\SWNC5E00.sys
2010/12/16 12:33:21.0000 sysaudio (8b83f3ed0f1688b4958f77cd6d2bf290) C:\WINDOWS\system32\drivers\sysaudio.sys
2010/12/16 12:33:21.0140 Tcpip (9aefa14bd6b182d61e3119fa5f436d3d) C:\WINDOWS\system32\DRIVERS\tcpip.sys
2010/12/16 12:33:21.0187 TDPIPE (6471a66807f5e104e4885f5b67349397) C:\WINDOWS\system32\drivers\TDPIPE.sys
2010/12/16 12:33:21.0250 TDTCP (c56b6d0402371cf3700eb322ef3aaf61) C:\WINDOWS\system32\drivers\TDTCP.sys
2010/12/16 12:33:21.0343 TermDD (88155247177638048422893737429d9e) C:\WINDOWS\system32\DRIVERS\termdd.sys
2010/12/16 12:33:21.0421 tmactmon (02ffe7402fb07f2f64d1ac6866345087) C:\WINDOWS\system32\drivers\tmactmon.sys
2010/12/16 12:33:21.0578 tmcfw (73d3b5d101e3202c268ffe851574b6eb) C:\WINDOWS\system32\DRIVERS\TM_CFW.sys
2010/12/16 12:33:21.0781 tmcomm (8762cb58a489b385feef2aea7f7718f3) C:\WINDOWS\system32\drivers\tmcomm.sys
2010/12/16 12:33:21.0828 tmevtmgr (efe60b70fa964459dde55039c5b05be7) C:\WINDOWS\system32\drivers\tmevtmgr.sys
2010/12/16 12:33:21.0890 tmpreflt (9cbbe54780770fdb7aaa73be530e4d80) C:\WINDOWS\system32\DRIVERS\tmpreflt.sys
2010/12/16 12:33:21.0953 tmtdi (ce1321671eee4520b9b50cd513f67dad) C:\WINDOWS\system32\DRIVERS\tmtdi.sys
2010/12/16 12:33:22.0000 tmxpflt (6cc393305bd60056ca09a4c8032a169a) C:\WINDOWS\system32\DRIVERS\tmxpflt.sys
2010/12/16 12:33:22.0125 Udfs (5787b80c2e3c5e2f56c2a233d91fa2c9) C:\WINDOWS\system32\drivers\Udfs.sys
2010/12/16 12:33:22.0234 Update (402ddc88356b1bac0ee3dd1580c76a31) C:\WINDOWS\system32\DRIVERS\update.sys
2010/12/16 12:33:22.0359 USBAAPL (1df89c499bf45d878b87ebd4421d462d) C:\WINDOWS\system32\Drivers\usbaapl.sys
2010/12/16 12:33:22.0421 usbccgp (173f317ce0db8e21322e71b7e60a27e8) C:\WINDOWS\system32\DRIVERS\usbccgp.sys
2010/12/16 12:33:22.0500 usbehci (65dcf09d0e37d4c6b11b5b0b76d470a7) C:\WINDOWS\system32\DRIVERS\usbehci.sys
2010/12/16 12:33:22.0578 usbhub (1ab3cdde553b6e064d2e754efe20285c) C:\WINDOWS\system32\DRIVERS\usbhub.sys
2010/12/16 12:33:22.0656 usbohci (0daecce65366ea32b162f85f07c6753b) C:\WINDOWS\system32\DRIVERS\usbohci.sys
2010/12/16 12:33:22.0750 usbprint (a717c8721046828520c9edf31288fc00) C:\WINDOWS\system32\DRIVERS\usbprint.sys
2010/12/16 12:33:22.0812 usbscan (a0b8cf9deb1184fbdd20784a58fa75d4) C:\WINDOWS\system32\DRIVERS\usbscan.sys
2010/12/16 12:33:22.0906 USBSTOR (a32426d9b14a089eaa1d922e0c5801a9) C:\WINDOWS\system32\DRIVERS\USBSTOR.SYS
2010/12/16 12:33:22.0937 usbuhci (26496f9dee2d787fc3e61ad54821ffe6) C:\WINDOWS\system32\DRIVERS\usbuhci.sys
2010/12/16 12:33:22.0984 VgaSave (0d3a8fafceacd8b7625cd549757a7df1) C:\WINDOWS\System32\drivers\vga.sys
2010/12/16 12:33:23.0109 VolSnap (4c8fcb5cc53aab716d810740fe59d025) C:\WINDOWS\system32\drivers\VolSnap.sys
2010/12/16 12:33:23.0281 vsapint (bbdd84ca629c1f7c8172b4405867f196) C:\WINDOWS\system32\DRIVERS\vsapint.sys
2010/12/16 12:33:23.0578 Wanarp (e20b95baedb550f32dd489265c1da1f6) C:\WINDOWS\system32\DRIVERS\wanarp.sys
2010/12/16 12:33:23.0734 wdmaud (6768acf64b18196494413695f0c3a00f) C:\WINDOWS\system32\drivers\wdmaud.sys
2010/12/16 12:33:23.0921 WpdUsb (cf4def1bf66f06964dc0d91844239104) C:\WINDOWS\system32\Drivers\wpdusb.sys
2010/12/16 12:33:23.0984 WSTCODEC (c98b39829c2bbd34e454150633c62c78) C:\WINDOWS\system32\DRIVERS\WSTCODEC.SYS
2010/12/16 12:33:24.0031 WudfPf (f15feafffbb3644ccc80c5da584e6311) C:\WINDOWS\system32\DRIVERS\WudfPf.sys
2010/12/16 12:33:24.0093 WudfRd (28b524262bce6de1f7ef9f510ba3985b) C:\WINDOWS\system32\DRIVERS\wudfrd.sys
2010/12/16 12:33:24.0187 \HardDisk0 - detected Rootkit.Win32.TDSS.tdl4 (0)
2010/12/16 12:33:24.0187 ================================================================================
2010/12/16 12:33:24.0187 Scan finished
2010/12/16 12:33:24.0187 ================================================================================
2010/12/16 12:33:24.0203 Detected object count: 1
2010/12/16 12:49:38.0546 \HardDisk0 - will be cured after reboot
2010/12/16 12:49:38.0546 Rootkit.Win32.TDSS.tdl4(\HardDisk0) - User select action: Cure





After rebooting and re running the TDSS rootkit removing tool it is coming up with 0 Detected objects.
So Is the system now clean?
Thank You for your time and effort...




Also FYI: My Supervisor pointed out that because TrendMicro Internet Security is installed and is a firewall that it might be blocking the MBAM update. He was right because after disabling it MBAM updated just fine...

#4 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,490 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:01:23 PM

Posted 16 December 2010 - 10:03 PM

This looks good now. TDDSkiller would have been the next step,so good call. Just a note about what may have occurred while infected.
These infections (while active)can allow an attacker to gain control of the system, log keystrokes, steal passwords, access personal
data, send malevolent outgoing traffic, and close the security warning messages displayed by some anti-virus and security programs.

I would advise you to change any passwords or security information that was held on this computer. In particular, check whatever relates to online
banking financial transactions, shopping, credit cards, or sensitive personal information. It is also wise to contact your financial institutions
to apprise them of your situation.



If there are no more problems or signs of infection, you should Create a New Restore Point to prevent possible reinfection from an old one. Some of the malware you picked up could have been saved in System Restore. Since this is a protected directory your tools cannot access to delete these files, they sometimes can reinfect your system if you accidentally use an old restore point. Setting a new restore point AFTER cleaning your system will help prevent this and enable your computer to "roll-back" to a clean working state.

The easiest and safest way to do this is:
  • Go to Start > Programs > Accessories > System Tools and click "System Restore".
  • Choose the radio button marked "Create a Restore Point" on the first screen then click "Next". Give the R.P. a name, then click "Create". The new point will be stamped with the current date and time. Keep a log of this so you can find it easily should you need to use System Restore.
  • Then use Disk Cleanup to remove all but the most recently created Restore Point.
  • Go to Start > Run and type: Cleanmgr
  • Click "Ok". Disk Cleanup will scan your files for several minutes, then open.
  • Click the "More Options" tab, then click the "Clean up" button under System Restore.
  • Click Ok. You will be prompted with "Are you sure you want to delete all but the most recent restore point?"
  • Click Yes, then click Ok.
  • Click Yes again when prompted with "Are you sure you want to perform these actions?"
  • Disk Cleanup will remove the files and close automatically.
Vista Users can refer to these links: Create a New Restore Point and Disk Cleanup.

Tips to protect yourself against malware and reduce the potential for re-infection:Avoid gaming sites, pirated software, cracking tools, keygens, and peer-to-peer (P2P) file sharing programs. They are a security risk which can make your computer susceptible to a smörgåsbord of malware infections, remote attacks, exposure of personal information, and identity theft. Many malicious worms and Trojans spread across P2P file sharing networks, gaming and underground sites. Users visiting such pages may see innocuous-looking banner ads containing code which can trigger pop-up ads and malicious Flash ads that install viruses, Trojans and spyware. Ads are a target for hackers because they offer a stealthy way to distribute malware to a wide range of Internet users. The best way to reduce the risk of infection is to avoid these types of web sites and not use any P2P applications. Read P2P Software User Advisories and Risks of File-Sharing Technology.

Keeping Autorun enabled on USB and other removable drives has become a significant security risk due to the increasing number of malware variants that can infect them and transfer the infection to your computer. To learn more about this risk, please read: (credit quietman7}
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 4est

4est
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:23 AM

Posted 17 December 2010 - 11:08 AM

Thank You So Much!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users