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

Hello4 virus?


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

#1 hampmeister

hampmeister

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:01:02 AM

Posted 16 July 2011 - 07:47 PM

Hello4 process won't kill, Blank Window2 every few seconds OS is XP Pro 2002 sp3 .

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,534 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:02 AM

Posted 16 July 2011 - 08:52 PM

Hello, I moved this to the Am I Infected forum from XP.

Please download the TDSS Rootkit Removing Tool (TDSSKiller.exe) and save it to your Desktop. <-Important!!!
Be sure to download TDSSKiller.exe (v2.5.9.0) from Kaspersky's website and not TDSSKiller.zip which appears to be an older version 2.3.2.2 of the tool.
  • Double-click on TDSSKiller.exe to run the tool for known TDSS variants.
    Vista/Windows 7 users right-click and select Run As Administrator.
  • If TDSSKiller does not run, try renaming it.
  • To do this, right-click on TDSSKiller.exe, select Rename and give it a random name with the .com file extension (i.e. 123abc.com). If you do not see the file extension, please refer to How to change the file extension.
  • Click the Start Scan button.
  • Do not use the computer during the scan
  • If the scan completes with nothing found, click Close to exit.
  • If malicious objects are found, they will show in the Scan results - Select action for found objects and offer three options.
  • Ensure Cure (default) is selected, then click Continue > Reboot now to finish the cleaning process.
  • 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.


Next 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
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 hampmeister

hampmeister
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:01:02 AM

Posted 17 July 2011 - 07:10 AM

Neither was successful. Here are the logs...

2011/07/16 20:15:02.0843 2140 TDSS rootkit removing tool 2.5.11.0 Jul 11 2011 16:56:56
2011/07/16 20:15:03.0328 2140 ================================================================================
2011/07/16 20:15:03.0328 2140 SystemInfo:
2011/07/16 20:15:03.0328 2140
2011/07/16 20:15:03.0328 2140 OS Version: 5.1.2600 ServicePack: 3.0
2011/07/16 20:15:03.0328 2140 Product type: Workstation
2011/07/16 20:15:03.0328 2140 ComputerName: jhamp-us
2011/07/16 20:15:03.0328 2140 UserName: jhamp
2011/07/16 20:15:03.0328 2140 Windows directory: C:\WINDOWS
2011/07/16 20:15:03.0328 2140 System windows directory: C:\WINDOWS
2011/07/16 20:15:03.0328 2140 Processor architecture: Intel x86
2011/07/16 20:15:03.0328 2140 Number of processors: 2
2011/07/16 20:15:03.0328 2140 Page size: 0x1000
2011/07/16 20:15:03.0328 2140 Boot type: Normal boot
2011/07/16 20:15:03.0328 2140 ================================================================================
2011/07/16 20:15:05.0281 2140 Initialize success
2011/07/16 20:15:15.0078 4576 ================================================================================
2011/07/16 20:15:15.0078 4576 Scan started
2011/07/16 20:15:15.0078 4576 Mode: Manual;
2011/07/16 20:15:15.0078 4576 ================================================================================
2011/07/16 20:15:16.0515 4576 abp480n5 (6abb91494fe6c59089b9336452ab2ea3) C:\WINDOWS\system32\DRIVERS\ABP480N5.SYS
2011/07/16 20:15:16.0593 4576 ACPI (8fd99680a539792a30e97944fdaecf17) C:\WINDOWS\system32\DRIVERS\ACPI.sys
2011/07/16 20:15:16.0671 4576 ACPIEC (9859c0f6936e723e4892d7141b1327d5) C:\WINDOWS\system32\drivers\ACPIEC.sys
2011/07/16 20:15:16.0796 4576 adpu160m (9a11864873da202c996558b2106b0bbc) C:\WINDOWS\system32\DRIVERS\adpu160m.sys
2011/07/16 20:15:16.0859 4576 aec (8bed39e3c35d6a489438b8141717a557) C:\WINDOWS\system32\drivers\aec.sys
2011/07/16 20:15:16.0937 4576 AFD (7e775010ef291da96ad17ca4b17137d7) C:\WINDOWS\System32\drivers\afd.sys
2011/07/16 20:15:17.0000 4576 agp440 (08fd04aa961bdc77fb983f328334e3d7) C:\WINDOWS\system32\DRIVERS\agp440.sys
2011/07/16 20:15:17.0031 4576 agpCPQ (03a7e0922acfe1b07d5db2eeb0773063) C:\WINDOWS\system32\DRIVERS\agpCPQ.sys
2011/07/16 20:15:17.0093 4576 Aha154x (9d863e368ef1258065c07f95b85f91a3) C:\WINDOWS\system32\DRIVERS\aha154x.sys
2011/07/16 20:15:17.0093 4576 Suspicious file (Forged): C:\WINDOWS\system32\DRIVERS\aha154x.sys. Real md5: 9d863e368ef1258065c07f95b85f91a3, Fake md5: c23ea9b5f46c7f7910db3eab648ff013
2011/07/16 20:15:17.0109 4576 Aha154x - detected Rootkit.Win32.TDSS.tdl3 (0)
2011/07/16 20:15:17.0203 4576 aic78u2 (19dd0fb48b0c18892f70e2e7d61a1529) C:\WINDOWS\system32\DRIVERS\aic78u2.sys
2011/07/16 20:15:17.0250 4576 aic78xx (b7fe594a7468aa0132deb03fb8e34326) C:\WINDOWS\system32\DRIVERS\aic78xx.sys
2011/07/16 20:15:17.0312 4576 AliIde (1140ab9938809700b46bb88e46d72a96) C:\WINDOWS\system32\DRIVERS\aliide.sys
2011/07/16 20:15:17.0343 4576 alim1541 (cb08aed0de2dd889a8a820cd8082d83c) C:\WINDOWS\system32\DRIVERS\alim1541.sys
2011/07/16 20:15:17.0406 4576 amdagp (95b4fb835e28aa1336ceeb07fd5b9398) C:\WINDOWS\system32\DRIVERS\amdagp.sys
2011/07/16 20:15:17.0453 4576 amsint (79f5add8d24bd6893f2903a3e2f3fad6) C:\WINDOWS\system32\DRIVERS\amsint.sys
2011/07/16 20:15:17.0578 4576 ApfiltrService (b8d65da679a4a8d048783ede2691b5d4) C:\WINDOWS\system32\DRIVERS\Apfiltr.sys
2011/07/16 20:15:17.0734 4576 Arp1394 (b5b8a80875c1dededa8b02765642c32f) C:\WINDOWS\system32\DRIVERS\arp1394.sys
2011/07/16 20:15:17.0812 4576 asc (62d318e9a0c8fc9b780008e724283707) C:\WINDOWS\system32\DRIVERS\asc.sys
2011/07/16 20:15:17.0843 4576 asc3350p (69eb0cc7714b32896ccbfd5edcbea447) C:\WINDOWS\system32\DRIVERS\asc3350p.sys
2011/07/16 20:15:17.0906 4576 asc3550 (5d8de112aa0254b907861e9e9c31d597) C:\WINDOWS\system32\DRIVERS\asc3550.sys
2011/07/16 20:15:18.0000 4576 AsyncMac (b153affac761e7f5fcfa822b9c4e97bc) C:\WINDOWS\system32\DRIVERS\asyncmac.sys
2011/07/16 20:15:18.0046 4576 atapi (9f3a2f5aa6875c72bf062c712cfa2674) C:\WINDOWS\system32\DRIVERS\atapi.sys
2011/07/16 20:15:18.0234 4576 Atmarpc (9916c1225104ba14794209cfa8012159) C:\WINDOWS\system32\DRIVERS\atmarpc.sys
2011/07/16 20:15:18.0312 4576 audstub (d9f724aa26c010a217c97606b160ed68) C:\WINDOWS\system32\DRIVERS\audstub.sys
2011/07/16 20:15:18.0375 4576 b57w2k (f96038aa1ec4013a93d2420fc689d1e9) C:\WINDOWS\system32\DRIVERS\b57xp32.sys
2011/07/16 20:15:18.0406 4576 Beep (da1f27d85e0d1525f6621372e7b685e9) C:\WINDOWS\system32\drivers\Beep.sys
2011/07/16 20:15:18.0468 4576 BVRPMPR5 (248dfa5762dde38dfddbbd44149e9d7a) C:\WINDOWS\system32\drivers\BVRPMPR5.SYS
2011/07/16 20:15:18.0515 4576 cbidf (90a673fc8e12a79afbed2576f6a7aaf9) C:\WINDOWS\system32\DRIVERS\cbidf2k.sys
2011/07/16 20:15:18.0531 4576 cbidf2k (90a673fc8e12a79afbed2576f6a7aaf9) C:\WINDOWS\system32\drivers\cbidf2k.sys
2011/07/16 20:15:18.0546 4576 cd20xrnt (f3ec03299634490e97bbce94cd2954c7) C:\WINDOWS\system32\DRIVERS\cd20xrnt.sys
2011/07/16 20:15:18.0687 4576 Cdaudio (c1b486a7658353d33a10cc15211a873b) C:\WINDOWS\system32\drivers\Cdaudio.sys
2011/07/16 20:15:18.0765 4576 Cdfs (c885b02847f5d2fd45a24e219ed93b32) C:\WINDOWS\system32\drivers\Cdfs.sys
2011/07/16 20:15:18.0828 4576 Cdrom (1f4260cc5b42272d71f79e570a27a4fe) C:\WINDOWS\system32\DRIVERS\cdrom.sys
2011/07/16 20:15:18.0921 4576 CmBatt (0f6c187d38d98f8df904589a5f94d411) C:\WINDOWS\system32\DRIVERS\CmBatt.sys
2011/07/16 20:15:19.0000 4576 CmdIde (e5dcb56c533014ecbc556a8357c929d5) C:\WINDOWS\system32\DRIVERS\cmdide.sys
2011/07/16 20:15:19.0046 4576 Compbatt (6e4c9f21f0fae8940661144f41b13203) C:\WINDOWS\system32\DRIVERS\compbatt.sys
2011/07/16 20:15:19.0109 4576 Cpqarray (3ee529119eed34cd212a215e8c40d4b6) C:\WINDOWS\system32\DRIVERS\cpqarray.sys
2011/07/16 20:15:19.0250 4576 CSRBC (8e1945984e147562f9f08e1d344a69cc) C:\WINDOWS\system32\Drivers\csrbcxp.sys
2011/07/16 20:15:19.0328 4576 CVirtA (5c706c06c1279952d2cc1a609ca948bf) C:\WINDOWS\system32\DRIVERS\CVirtA.sys
2011/07/16 20:15:19.0390 4576 CVPNDRVA (5ba042bcab6246c6bba51606afd7b488) c:\WINDOWS\system32\Drivers\CVPNDRVA.sys
2011/07/16 20:15:19.0421 4576 dac2w2k (e550e7418984b65a78299d248f0a7f36) C:\WINDOWS\system32\DRIVERS\dac2w2k.sys
2011/07/16 20:15:19.0437 4576 dac960nt (683789caa3864eb46125ae86ff677d34) C:\WINDOWS\system32\DRIVERS\dac960nt.sys
2011/07/16 20:15:19.0531 4576 Disk (044452051f3e02e7963599fc8f4f3e25) C:\WINDOWS\system32\DRIVERS\disk.sys
2011/07/16 20:15:19.0609 4576 dmboot (d992fe1274bde0f84ad826acae022a41) C:\WINDOWS\system32\drivers\dmboot.sys
2011/07/16 20:15:19.0812 4576 dmio (7c824cf7bbde77d95c08005717a95f6f) C:\WINDOWS\system32\drivers\dmio.sys
2011/07/16 20:15:20.0125 4576 dmload (e9317282a63ca4d188c0df5e09c6ac5f) C:\WINDOWS\system32\drivers\dmload.sys
2011/07/16 20:15:20.0343 4576 DMusic (8a208dfcf89792a484e76c40e5f50b45) C:\WINDOWS\system32\drivers\DMusic.sys
2011/07/16 20:15:20.0734 4576 DNE (2eddbb3ef1dd5a28cb07c149d36e7286) C:\WINDOWS\system32\DRIVERS\dne2000.sys
2011/07/16 20:15:20.0828 4576 dpti2o (40f3b93b4e5b0126f2f5c0a7a5e22660) C:\WINDOWS\system32\DRIVERS\dpti2o.sys
2011/07/16 20:15:20.0921 4576 drmkaud (8f5fcff8e8848afac920905fbd9d33c8) C:\WINDOWS\system32\drivers\drmkaud.sys
2011/07/16 20:15:21.0046 4576 dsdd (5164d3e7243459db3be26dee56b4afdf) C:\WINDOWS\system32\DRIVERS\dsvideo.sys
2011/07/16 20:15:21.0156 4576 dsload (4d0c738fe7b84b6cf3ce17606695014c) C:\WINDOWS\system32\drivers\dsload.sys
2011/07/16 20:15:21.0234 4576 E1000 (854293999e91bf2eb9e786166de4a35f) C:\WINDOWS\system32\DRIVERS\e1000325.sys
2011/07/16 20:15:21.0343 4576 Fastfat (38d332a6d56af32635675f132548343e) C:\WINDOWS\system32\drivers\Fastfat.sys
2011/07/16 20:15:21.0453 4576 Fdc (92cdd60b6730b9f50f6a1a0c1f8cdc81) C:\WINDOWS\system32\DRIVERS\fdc.sys
2011/07/16 20:15:21.0515 4576 Fips (d45926117eb9fa946a6af572fbe1caa3) C:\WINDOWS\system32\drivers\Fips.sys
2011/07/16 20:15:21.0625 4576 Firehk (f96d1c2c40902604329933374950babb) C:\WINDOWS\system32\DRIVERS\firehk.sys
2011/07/16 20:15:21.0640 4576 FirehkMP (f96d1c2c40902604329933374950babb) C:\WINDOWS\system32\DRIVERS\firehk.sys
2011/07/16 20:15:21.0703 4576 firelm01 (7e661e34cce11472fd468f9a9383b391) C:\WINDOWS\system32\drivers\firelm01.sys
2011/07/16 20:15:21.0859 4576 FirePM (f0a996a78cf4fc361b319f2fc2abcefe) C:\WINDOWS\system32\Drivers\FirePM.sys
2011/07/16 20:15:21.0890 4576 FireTDI (91cbe1e5d61819d290b3471cab620fe3) C:\WINDOWS\system32\Drivers\FireTDI.sys
2011/07/16 20:15:21.0984 4576 Flpydisk (9d27e7b80bfcdf1cdd9b555862d5e7f0) C:\WINDOWS\system32\DRIVERS\flpydisk.sys
2011/07/16 20:15:22.0031 4576 FltMgr (b2cf4b0786f8212cb92ed2b50c6db6b0) C:\WINDOWS\system32\drivers\fltmgr.sys
2011/07/16 20:15:22.0125 4576 Fs_Rec (3e1e2bd4f39b0e2b7dc4f4d2bcc2779a) C:\WINDOWS\system32\drivers\Fs_Rec.sys
2011/07/16 20:15:22.0203 4576 Ftdisk (6ac26732762483366c3969c9e4d2259d) C:\WINDOWS\system32\DRIVERS\ftdisk.sys
2011/07/16 20:15:22.0296 4576 Gpc (0a02c63c8b144bd8c86b103dee7c86a2) C:\WINDOWS\system32\DRIVERS\msgpc.sys
2011/07/16 20:15:22.0343 4576 guardian2 (0e1fd1ea2837d6b7a1d7b6c928014d05) C:\WINDOWS\system32\Drivers\oz776.sys
2011/07/16 20:15:22.0437 4576 HDAudBus (573c7d0a32852b48f3058cfd8026f511) C:\WINDOWS\system32\DRIVERS\HDAudBus.sys
2011/07/16 20:15:22.0562 4576 HidUsb (ccf82c5ec8a7326c3066de870c06daf1) C:\WINDOWS\system32\DRIVERS\hidusb.sys
2011/07/16 20:15:22.0640 4576 HIPK (c61656628f974bbe152d971b34a3e74c) C:\WINDOWS\system32\drivers\HIPK.sys
2011/07/16 20:15:22.0734 4576 HIPPSK (cbabea2348172968a7b4ff54c382893f) C:\WINDOWS\system32\drivers\HIPPSK.sys
2011/07/16 20:15:22.0781 4576 HIPQK (f44af553d6291317daaa428ad65ad3e7) C:\WINDOWS\system32\drivers\HIPQK.sys
2011/07/16 20:15:22.0843 4576 hpn (b028377dea0546a5fcfba928a8aefae0) C:\WINDOWS\system32\DRIVERS\hpn.sys
2011/07/16 20:15:23.0078 4576 HPZid412 (d03d10f7ded688fecf50f8fbf1ea9b8a) C:\WINDOWS\system32\DRIVERS\HPZid412.sys
2011/07/16 20:15:23.0203 4576 HPZipr12 (89f41658929393487b6b7d13c8528ce3) C:\WINDOWS\system32\DRIVERS\HPZipr12.sys
2011/07/16 20:15:23.0265 4576 HPZius12 (abcb05ccdbf03000354b9553820e39f8) C:\WINDOWS\system32\DRIVERS\HPZius12.sys
2011/07/16 20:15:23.0406 4576 HSFHWAZL (b1526810210980bed9d22315946c919d) C:\WINDOWS\system32\DRIVERS\HSFHWAZL.sys
2011/07/16 20:15:23.0484 4576 HSF_DPV (ddbd528e60f5961c142a490dc4ea7780) C:\WINDOWS\system32\DRIVERS\HSF_DPV.sys
2011/07/16 20:15:23.0625 4576 HTTP (f6aacf5bce2893e0c1754afeb672e5c9) C:\WINDOWS\system32\Drivers\HTTP.sys
2011/07/16 20:15:23.0750 4576 i2omgmt (9368670bd426ebea5e8b18a62416ec28) C:\WINDOWS\system32\drivers\i2omgmt.sys
2011/07/16 20:15:23.0796 4576 i2omp (f10863bf1ccc290babd1a09188ae49e0) C:\WINDOWS\system32\DRIVERS\i2omp.sys
2011/07/16 20:15:23.0828 4576 i8042prt (4a0b06aa8943c1e332520f7440c0aa30) C:\WINDOWS\system32\DRIVERS\i8042prt.sys
2011/07/16 20:15:24.0125 4576 ialm (200cca76cd0e0f7eec78fa56c29b4d67) C:\WINDOWS\system32\DRIVERS\igxpmp32.sys
2011/07/16 20:15:24.0406 4576 iaStor (fd7f9d74c2b35dbda400804a3f5ed5d8) C:\WINDOWS\system32\Drivers\iaStor.sys
2011/07/16 20:15:24.0531 4576 Imapi (083a052659f5310dd8b6a6cb05edcf8e) C:\WINDOWS\system32\DRIVERS\imapi.sys
2011/07/16 20:15:24.0609 4576 ini910u (4a40e045faee58631fd8d91afc620719) C:\WINDOWS\system32\DRIVERS\ini910u.sys
2011/07/16 20:15:24.0734 4576 IntelIde (b5466a9250342a7aa0cd1fba13420678) C:\WINDOWS\system32\DRIVERS\intelide.sys
2011/07/16 20:15:24.0781 4576 intelppm (8c953733d8f36eb2133f5bb58808b66b) C:\WINDOWS\system32\DRIVERS\intelppm.sys
2011/07/16 20:15:24.0875 4576 ip6fw (3bb22519a194418d5fec05d800a19ad0) C:\WINDOWS\system32\drivers\ip6fw.sys
2011/07/16 20:15:24.0968 4576 iPassP (c7cb23eb2f2b3df2139f52b07cb5f22c) C:\WINDOWS\system32\DRIVERS\iPassP.sys
2011/07/16 20:15:25.0046 4576 IpFilterDriver (731f22ba402ee4b62748adaf6363c182) C:\WINDOWS\system32\DRIVERS\ipfltdrv.sys
2011/07/16 20:15:25.0109 4576 IpInIp (b87ab476dcf76e72010632b5550955f5) C:\WINDOWS\system32\DRIVERS\ipinip.sys
2011/07/16 20:15:25.0218 4576 IpNat (cc748ea12c6effde940ee98098bf96bb) C:\WINDOWS\system32\DRIVERS\ipnat.sys
2011/07/16 20:15:25.0281 4576 IPSec (23c74d75e36e7158768dd63d92789a91) C:\WINDOWS\system32\DRIVERS\ipsec.sys
2011/07/16 20:15:25.0328 4576 IRENUM (c93c9ff7b04d772627a3646d89f7bf89) C:\WINDOWS\system32\DRIVERS\irenum.sys
2011/07/16 20:15:25.0421 4576 isapnp (05a299ec56e52649b1cf2fc52d20f2d7) C:\WINDOWS\system32\DRIVERS\isapnp.sys
2011/07/16 20:15:25.0500 4576 Kbdclass (463c1ec80cd17420a542b7f36a36f128) C:\WINDOWS\system32\DRIVERS\kbdclass.sys
2011/07/16 20:15:25.0625 4576 kbdhid (9ef487a186dea361aa06913a75b3fa99) C:\WINDOWS\system32\DRIVERS\kbdhid.sys
2011/07/16 20:15:25.0703 4576 KLIF (2cf7c3dd0102a32a680ef97f3b1c861a) C:\WINDOWS\system32\DRIVERS\klif.sys
2011/07/16 20:15:25.0765 4576 kmixer (692bcf44383d056aed41b045a323d378) C:\WINDOWS\system32\drivers\kmixer.sys
2011/07/16 20:15:25.0843 4576 KSecDD (b467646c54cc746128904e1654c750c1) C:\WINDOWS\system32\drivers\KSecDD.sys
2011/07/16 20:15:26.0078 4576 mdmxsdk (0cea2d0d3fa284b85ed5b68365114f76) C:\WINDOWS\system32\DRIVERS\mdmxsdk.sys
2011/07/16 20:15:26.0171 4576 mfeapfk (5cbf9d2fab2abc461b2f67c802f52543) C:\WINDOWS\system32\drivers\mfeapfk.sys
2011/07/16 20:15:26.0296 4576 mfeavfk (10718b3eeb9e98c5b4aad7c0a23a9efa) C:\WINDOWS\system32\drivers\mfeavfk.sys
2011/07/16 20:15:26.0421 4576 mfebopk (e665cff48e376b48d2cc84be1559f131) C:\WINDOWS\system32\drivers\mfebopk.sys
2011/07/16 20:15:26.0500 4576 mfehidk (e2f200d38b72e47b88489e2c97dfd6d8) C:\WINDOWS\system32\drivers\mfehidk.sys
2011/07/16 20:15:26.0546 4576 mferkdet (ef04236d1a4f9f672b5258de83e2ee35) C:\WINDOWS\system32\drivers\mferkdet.sys
2011/07/16 20:15:26.0640 4576 mfetdik (d5a4b1ae4958ccfc66c1d17c1f42ba08) C:\WINDOWS\system32\drivers\mfetdik.sys
2011/07/16 20:15:26.0718 4576 mnmdd (4ae068242760a1fb6e1a44bf4e16afa6) C:\WINDOWS\system32\drivers\mnmdd.sys
2011/07/16 20:15:26.0796 4576 Modem (dfcbad3cec1c5f964962ae10e0bcc8e1) C:\WINDOWS\system32\drivers\Modem.sys
2011/07/16 20:15:26.0906 4576 Mouclass (35c9e97194c8cfb8430125f8dbc34d04) C:\WINDOWS\system32\DRIVERS\mouclass.sys
2011/07/16 20:15:26.0953 4576 mouhid (b1c303e17fb9d46e87a98e4ba6769685) C:\WINDOWS\system32\DRIVERS\mouhid.sys
2011/07/16 20:15:27.0078 4576 MountMgr (a80b9a0bad1b73637dbcbba7df72d3fd) C:\WINDOWS\system32\drivers\MountMgr.sys
2011/07/16 20:15:27.0375 4576 mraid35x (3f4bb95e5a44f3be34824e8e7caf0737) C:\WINDOWS\system32\DRIVERS\mraid35x.sys
2011/07/16 20:15:27.0546 4576 MRxDAV (11d42bb6206f33fbb3ba0288d3ef81bd) C:\WINDOWS\system32\DRIVERS\mrxdav.sys
2011/07/16 20:15:27.0640 4576 MRxSmb (60ae98742484e7ab80c3c1450e708148) C:\WINDOWS\system32\DRIVERS\mrxsmb.sys
2011/07/16 20:15:27.0781 4576 Msfs (c941ea2454ba8350021d774daf0f1027) C:\WINDOWS\system32\drivers\Msfs.sys
2011/07/16 20:15:27.0843 4576 MSKSSRV (d1575e71568f4d9e14ca56b7b0453bf1) C:\WINDOWS\system32\drivers\MSKSSRV.sys
2011/07/16 20:15:27.0890 4576 MSPCLOCK (325bb26842fc7ccc1fcce2c457317f3e) C:\WINDOWS\system32\drivers\MSPCLOCK.sys
2011/07/16 20:15:27.0953 4576 MSPQM (bad59648ba099da4a17680b39730cb3d) C:\WINDOWS\system32\drivers\MSPQM.sys
2011/07/16 20:15:28.0062 4576 mssmbios (af5f4f3f14a8ea2c26de30f7a1e17136) C:\WINDOWS\system32\DRIVERS\mssmbios.sys
2011/07/16 20:15:28.0218 4576 Mup (2f625d11385b1a94360bfc70aaefdee1) C:\WINDOWS\system32\drivers\Mup.sys
2011/07/16 20:15:28.0281 4576 NDIS (1df7f42665c94b825322fae71721130d) C:\WINDOWS\system32\drivers\NDIS.sys
2011/07/16 20:15:28.0343 4576 NdisTapi (1ab3d00c991ab086e69db84b6c0ed78f) C:\WINDOWS\system32\DRIVERS\ndistapi.sys
2011/07/16 20:15:28.0406 4576 Ndisuio (f927a4434c5028758a842943ef1a3849) C:\WINDOWS\system32\DRIVERS\ndisuio.sys
2011/07/16 20:15:28.0500 4576 NdisWan (edc1531a49c80614b2cfda43ca8659ab) C:\WINDOWS\system32\DRIVERS\ndiswan.sys
2011/07/16 20:15:28.0562 4576 NDProxy (6215023940cfd3702b46abc304e1d45a) C:\WINDOWS\system32\drivers\NDProxy.sys
2011/07/16 20:15:28.0625 4576 NetBIOS (5d81cf9a2f1a3a756b66cf684911cdf0) C:\WINDOWS\system32\DRIVERS\netbios.sys
2011/07/16 20:15:28.0750 4576 NetBT (74b2b2f5bea5e9a3dc021d685551bd3d) C:\WINDOWS\system32\DRIVERS\netbt.sys
2011/07/16 20:15:28.0921 4576 NETw4x32 (18b2d3e11ed7a3c898ade6a6692b6929) C:\WINDOWS\system32\DRIVERS\NETw4x32.sys
2011/07/16 20:15:29.0171 4576 NIC1394 (e9e47cfb2d461fa0fc75b7a74c6383ea) C:\WINDOWS\system32\DRIVERS\nic1394.sys
2011/07/16 20:15:29.0250 4576 Npfs (3182d64ae053d6fb034f44b6def8034a) C:\WINDOWS\system32\drivers\Npfs.sys
2011/07/16 20:15:29.0343 4576 Ntfs (78a08dd6a8d65e697c18e1db01c5cdca) C:\WINDOWS\system32\drivers\Ntfs.sys
2011/07/16 20:15:29.0406 4576 Null (73c1e1f395918bc2c6dd67af7591a3ad) C:\WINDOWS\system32\drivers\Null.sys
2011/07/16 20:15:29.0468 4576 NwlnkFlt (b305f3fad35083837ef46a0bbce2fc57) C:\WINDOWS\system32\DRIVERS\nwlnkflt.sys
2011/07/16 20:15:29.0531 4576 NwlnkFwd (c99b3415198d1aab7227f2c88fd664b9) C:\WINDOWS\system32\DRIVERS\nwlnkfwd.sys
2011/07/16 20:15:29.0625 4576 ohci1394 (ca33832df41afb202ee7aeb05145922f) C:\WINDOWS\system32\DRIVERS\ohci1394.sys
2011/07/16 20:15:29.0796 4576 Parport (5575faf8f97ce5e713d108c2a58d7c7c) C:\WINDOWS\system32\DRIVERS\parport.sys
2011/07/16 20:15:29.0843 4576 PartMgr (beb3ba25197665d82ec7065b724171c6) C:\WINDOWS\system32\drivers\PartMgr.sys
2011/07/16 20:15:29.0890 4576 ParVdm (70e98b3fd8e963a6a46a2e6247e0bea1) C:\WINDOWS\system32\drivers\ParVdm.sys
2011/07/16 20:15:29.0921 4576 PCI (a219903ccf74233761d92bef471a07b1) C:\WINDOWS\system32\DRIVERS\pci.sys
2011/07/16 20:15:30.0031 4576 PCIIde (ccf5f451bb1a5a2a522a76e670000ff0) C:\WINDOWS\system32\DRIVERS\pciide.sys
2011/07/16 20:15:30.0125 4576 Pcmcia (9e89ef60e9ee05e3f2eef2da7397f1c1) C:\WINDOWS\system32\DRIVERS\pcmcia.sys
2011/07/16 20:15:30.0359 4576 perc2 (6c14b9c19ba84f73d3a86dba11133101) C:\WINDOWS\system32\DRIVERS\perc2.sys
2011/07/16 20:15:30.0406 4576 perc2hib (f50f7c27f131afe7beba13e14a3b9416) C:\WINDOWS\system32\DRIVERS\perc2hib.sys
2011/07/16 20:15:30.0531 4576 PMEMNT (fa292805788528c083f416e151b60ab6) C:\WINDOWS\pmemnt.sys
2011/07/16 20:15:31.0437 4576 PptpMiniport (efeec01b1d3cf84f16ddd24d9d9d8f99) C:\WINDOWS\system32\DRIVERS\raspptp.sys
2011/07/16 20:15:31.0531 4576 Processor (a32bebaf723557681bfc6bd93e98bd26) C:\WINDOWS\system32\DRIVERS\processr.sys
2011/07/16 20:15:31.0562 4576 PSched (09298ec810b07e5d582cb3a3f9255424) C:\WINDOWS\system32\DRIVERS\psched.sys
2011/07/16 20:15:31.0625 4576 Ptilink (80d317bd1c3dbc5d4fe7b1678c60cadd) C:\WINDOWS\system32\DRIVERS\ptilink.sys
2011/07/16 20:15:31.0687 4576 ql1080 (0a63fb54039eb5662433caba3b26dba7) C:\WINDOWS\system32\DRIVERS\ql1080.sys
2011/07/16 20:15:31.0703 4576 Ql10wnt (6503449e1d43a0ff0201ad5cb1b8c706) C:\WINDOWS\system32\DRIVERS\ql10wnt.sys
2011/07/16 20:15:31.0734 4576 ql12160 (156ed0ef20c15114ca097a34a30d8a01) C:\WINDOWS\system32\DRIVERS\ql12160.sys
2011/07/16 20:15:31.0750 4576 ql1240 (70f016bebde6d29e864c1230a07cc5e6) C:\WINDOWS\system32\DRIVERS\ql1240.sys
2011/07/16 20:15:31.0781 4576 ql1280 (907f0aeea6bc451011611e732bd31fcf) C:\WINDOWS\system32\DRIVERS\ql1280.sys
2011/07/16 20:15:31.0812 4576 RasAcd (fe0d99d6f31e4fad8159f690d68ded9c) C:\WINDOWS\system32\DRIVERS\rasacd.sys
2011/07/16 20:15:31.0843 4576 Rasl2tp (11b4a627bc9614b885c4969bfa5ff8a6) C:\WINDOWS\system32\DRIVERS\rasl2tp.sys
2011/07/16 20:15:31.0984 4576 RasPppoe (5bc962f2654137c9909c3d4603587dee) C:\WINDOWS\system32\DRIVERS\raspppoe.sys
2011/07/16 20:15:32.0031 4576 Raspti (fdbb1d60066fcfbb7452fd8f9829b242) C:\WINDOWS\system32\DRIVERS\raspti.sys
2011/07/16 20:15:32.0187 4576 Rdbss (7ad224ad1a1437fe28d89cf22b17780a) C:\WINDOWS\system32\DRIVERS\rdbss.sys
2011/07/16 20:15:32.0265 4576 RDPCDD (4912d5b403614ce99c28420f75353332) C:\WINDOWS\system32\DRIVERS\RDPCDD.sys
2011/07/16 20:15:32.0359 4576 rdpdr (15cabd0f7c00c47c70124907916af3f1) C:\WINDOWS\system32\DRIVERS\rdpdr.sys
2011/07/16 20:15:32.0453 4576 RDPWD (6728e45b66f93c08f11de2e316fc70dd) C:\WINDOWS\system32\drivers\RDPWD.sys
2011/07/16 20:15:32.0515 4576 redbook (f828dd7e1419b6653894a8f97a0094c5) C:\WINDOWS\system32\DRIVERS\redbook.sys
2011/07/16 20:15:32.0640 4576 Secdrv (90a3935d05b494a5a39d37e71f09a677) C:\WINDOWS\system32\DRIVERS\secdrv.sys
2011/07/16 20:15:32.0734 4576 serenum (0f29512ccd6bead730039fb4bd2c85ce) C:\WINDOWS\system32\DRIVERS\serenum.sys
2011/07/16 20:15:32.0796 4576 Serial (cca207a8896d4c6a0c9ce29a4ae411a7) C:\WINDOWS\system32\DRIVERS\serial.sys
2011/07/16 20:15:32.0906 4576 Sfloppy (8e6b8c671615d126fdc553d1e2de5562) C:\WINDOWS\system32\drivers\Sfloppy.sys
2011/07/16 20:15:33.0078 4576 sisagp (6b33d0ebd30db32e27d1d78fe946a754) C:\WINDOWS\system32\DRIVERS\sisagp.sys
2011/07/16 20:15:33.0156 4576 smwdm (b911c822922cf62df83ad36d5c9775cc) C:\WINDOWS\system32\drivers\smwdm.sys
2011/07/16 20:15:33.0265 4576 Sparrow (83c0f71f86d3bdaf915685f3d568b20e) C:\WINDOWS\system32\DRIVERS\sparrow.sys
2011/07/16 20:15:33.0390 4576 splitter (ab8b92451ecb048a4d1de7c3ffcb4a9f) C:\WINDOWS\system32\drivers\splitter.sys
2011/07/16 20:15:33.0437 4576 sr (76bb022c2fb6902fd5bdd4f78fc13a5d) C:\WINDOWS\system32\DRIVERS\sr.sys
2011/07/16 20:15:33.0578 4576 Srv (3bb03f2ba89d2be417206c373d2af17c) C:\WINDOWS\system32\DRIVERS\srv.sys
2011/07/16 20:15:33.0734 4576 STHDA (951801dfb54d86f611f0af47825476f9) C:\WINDOWS\system32\drivers\sthda.sys
2011/07/16 20:15:33.0812 4576 swenum (3941d127aef12e93addf6fe6ee027e0f) C:\WINDOWS\system32\DRIVERS\swenum.sys
2011/07/16 20:15:33.0859 4576 swmidi (8ce882bcc6cf8a62f2b2323d95cb3d01) C:\WINDOWS\system32\drivers\swmidi.sys
2011/07/16 20:15:33.0921 4576 symc810 (1ff3217614018630d0a6758630fc698c) C:\WINDOWS\system32\DRIVERS\symc810.sys
2011/07/16 20:15:33.0953 4576 symc8xx (070e001d95cf725186ef8b20335f933c) C:\WINDOWS\system32\DRIVERS\symc8xx.sys
2011/07/16 20:15:34.0062 4576 sym_hi (80ac1c4abbe2df3b738bf15517a51f2c) C:\WINDOWS\system32\DRIVERS\sym_hi.sys
2011/07/16 20:15:34.0109 4576 sym_u3 (bf4fab949a382a8e105f46ebb4937058) C:\WINDOWS\system32\DRIVERS\sym_u3.sys
2011/07/16 20:15:34.0156 4576 sysaudio (8b83f3ed0f1688b4958f77cd6d2bf290) C:\WINDOWS\system32\drivers\sysaudio.sys
2011/07/16 20:15:34.0265 4576 Tcpip (9aefa14bd6b182d61e3119fa5f436d3d) C:\WINDOWS\system32\DRIVERS\tcpip.sys
2011/07/16 20:15:34.0328 4576 TcUsb (fc6fe02f400308606a911640e72326b5) C:\WINDOWS\system32\Drivers\tcusb.sys
2011/07/16 20:15:34.0406 4576 TDFSD (9b6f2ebd3d6f5852b1dd46f1d7ca2ef2) C:\WINDOWS\System32\Drivers\TDFSD.sys
2011/07/16 20:15:34.0703 4576 TDPIPE (6471a66807f5e104e4885f5b67349397) C:\WINDOWS\system32\drivers\TDPIPE.sys
2011/07/16 20:15:34.0921 4576 TDTCP (c56b6d0402371cf3700eb322ef3aaf61) C:\WINDOWS\system32\drivers\TDTCP.sys
2011/07/16 20:15:35.0187 4576 TermDD (88155247177638048422893737429d9e) C:\WINDOWS\system32\DRIVERS\termdd.sys
2011/07/16 20:15:35.0296 4576 TosIde (f2790f6af01321b172aa62f8e1e187d9) C:\WINDOWS\system32\DRIVERS\toside.sys
2011/07/16 20:15:35.0546 4576 Udfs (5787b80c2e3c5e2f56c2a233d91fa2c9) C:\WINDOWS\system32\drivers\Udfs.sys
2011/07/16 20:15:35.0656 4576 ultra (1b698a51cd528d8da4ffaed66dfc51b9) C:\WINDOWS\system32\DRIVERS\ultra.sys
2011/07/16 20:15:35.0734 4576 Update (402ddc88356b1bac0ee3dd1580c76a31) C:\WINDOWS\system32\DRIVERS\update.sys
2011/07/16 20:15:35.0843 4576 usbccgp (173f317ce0db8e21322e71b7e60a27e8) C:\WINDOWS\system32\DRIVERS\usbccgp.sys
2011/07/16 20:15:35.0890 4576 usbehci (65dcf09d0e37d4c6b11b5b0b76d470a7) C:\WINDOWS\system32\DRIVERS\usbehci.sys
2011/07/16 20:15:35.0921 4576 usbhub (1ab3cdde553b6e064d2e754efe20285c) C:\WINDOWS\system32\DRIVERS\usbhub.sys
2011/07/16 20:15:35.0953 4576 usbprint (a717c8721046828520c9edf31288fc00) C:\WINDOWS\system32\DRIVERS\usbprint.sys
2011/07/16 20:15:36.0093 4576 usbscan (a0b8cf9deb1184fbdd20784a58fa75d4) C:\WINDOWS\system32\DRIVERS\usbscan.sys
2011/07/16 20:15:36.0171 4576 USBSTOR (a32426d9b14a089eaa1d922e0c5801a9) C:\WINDOWS\system32\DRIVERS\USBSTOR.SYS
2011/07/16 20:15:36.0296 4576 usbuhci (26496f9dee2d787fc3e61ad54821ffe6) C:\WINDOWS\system32\DRIVERS\usbuhci.sys
2011/07/16 20:15:36.0328 4576 VgaSave (0d3a8fafceacd8b7625cd549757a7df1) C:\WINDOWS\System32\drivers\vga.sys
2011/07/16 20:15:36.0375 4576 viaagp (754292ce5848b3738281b4f3607eaef4) C:\WINDOWS\system32\DRIVERS\viaagp.sys
2011/07/16 20:15:36.0484 4576 ViaIde (3b3efcda263b8ac14fdf9cbdd0791b2e) C:\WINDOWS\system32\DRIVERS\viaide.sys
2011/07/16 20:15:36.0531 4576 VolSnap (4c8fcb5cc53aab716d810740fe59d025) C:\WINDOWS\system32\drivers\VolSnap.sys
2011/07/16 20:15:36.0640 4576 vpnva (1b7c80c66742dafaa31f98af4c3a5bc2) C:\WINDOWS\system32\DRIVERS\vpnva.sys
2011/07/16 20:15:36.0781 4576 Wanarp (e20b95baedb550f32dd489265c1da1f6) C:\WINDOWS\system32\DRIVERS\wanarp.sys
2011/07/16 20:15:36.0906 4576 wdmaud (6768acf64b18196494413695f0c3a00f) C:\WINDOWS\system32\drivers\wdmaud.sys
2011/07/16 20:15:37.0093 4576 winachsf (96aff1738271755a39b52eef7e35f98f) C:\WINDOWS\system32\DRIVERS\HSF_CNXT.sys
2011/07/16 20:15:37.0281 4576 WmiAcpi (c42584fd66ce9e17403aebca199f7bdb) C:\WINDOWS\system32\DRIVERS\wmiacpi.sys
2011/07/16 20:15:37.0390 4576 WudfPf (f15feafffbb3644ccc80c5da584e6311) C:\WINDOWS\system32\DRIVERS\WudfPf.sys
2011/07/16 20:15:37.0484 4576 WudfRd (28b524262bce6de1f7ef9f510ba3985b) C:\WINDOWS\system32\DRIVERS\wudfrd.sys
2011/07/16 20:15:37.0687 4576 {6080A529-897E-4629-A488-ABA0C29B635E} (981210ddf5f7ed0cdf9f407999b3080c) C:\WINDOWS\system32\drivers\ialmsbw.sys
2011/07/16 20:15:37.0796 4576 {D31A0762-0CEB-444e-ACFF-B049A1F6FE91} (7ba8437f4e9db34ac602ffb66ca7120f) C:\WINDOWS\system32\drivers\ialmkchw.sys
2011/07/16 20:15:37.0828 4576 MBR (0x1B8) (8f558eb6672622401da993e1e865c861) \Device\Harddisk0\DR0
2011/07/16 20:15:38.0000 4576 Boot (0x1200) (6dd8ecb2b65522e1e501a4b429e7ba41) \Device\Harddisk0\DR0\Partition0
2011/07/16 20:15:38.0031 4576 Boot (0x1200) (850f35dc3c0fe4a9705335ad56dd1146) \Device\Harddisk0\DR0\Partition1
2011/07/16 20:15:38.0062 4576 Boot (0x1200) (53bd6f91e59b48a2be2ee52e408c787a) \Device\Harddisk0\DR0\Partition2
2011/07/16 20:15:38.0062 4576 ================================================================================
2011/07/16 20:15:38.0062 4576 Scan finished
2011/07/16 20:15:38.0062 4576 ================================================================================
2011/07/16 20:15:38.0078 4496 Detected object count: 1
2011/07/16 20:15:38.0078 4496 Actual detected object count: 1
2011/07/16 20:16:20.0906 4496 Aha154x (9d863e368ef1258065c07f95b85f91a3) C:\WINDOWS\system32\DRIVERS\aha154x.sys
2011/07/16 20:16:20.0906 4496 Suspicious file (Forged): C:\WINDOWS\system32\DRIVERS\aha154x.sys. Real md5: 9d863e368ef1258065c07f95b85f91a3, Fake md5: c23ea9b5f46c7f7910db3eab648ff013
2011/07/16 20:16:21.0312 4496 Backup copy found, using it..
2011/07/16 20:16:21.0312 4496 C:\WINDOWS\system32\DRIVERS\aha154x.sys - will be cured after reboot
2011/07/16 20:16:21.0312 4496 Rootkit.Win32.TDSS.tdl3(Aha154x) - User select action: Cure
2011/07/16 20:16:49.0453 4116 Deinitialize success

Malwarebytes' Anti-Malware 1.51.1.1800
www.malwarebytes.org

Database version: 7173

Windows 5.1.2600 Service Pack 3
Internet Explorer 6.0.2900.5512

7/17/2011 6:03:48 AM
mbam-log-2011-07-17 (06-03-48).txt

Scan type: Quick scan
Objects scanned: 1
Time elapsed: 3 minute(s), 7 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)

#4 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,534 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:02 AM

Posted 17 July 2011 - 04:04 PM

Wow We killed the Rootkit.Win32.TDSS.tdl3 and still have it.

We need a deeper look. 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

#5 hampmeister

hampmeister
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:01:02 AM

Posted 17 July 2011 - 05:44 PM

I saw the rootkit and was sure we got it. The reports are w

#6 hampmeister

hampmeister
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:01:02 AM

Posted 17 July 2011 - 05:49 PM

...way too big as there are LOTS of qttask processes

#7 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,534 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:02 AM

Posted 17 July 2011 - 05:53 PM

This is why we need those new logs as it may be regenerating,
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

#8 Zoooma

Zoooma

  • Members
  • 23 posts
  • OFFLINE
  •  
  • Local time:04:02 AM

Posted 18 July 2011 - 08:30 AM

Hello.

I might be in the same predicament as Hampmeister.

After running TDSSKiller.exe and then MBAM, when rebooting in Normal Mode, the Hello4 garbage starts right back up.

Should I proceed to Steps 6-9 as recommended and then post a new topic??

This hello4 thing is killin' me! I hope you can help.

THANKS!!!!!!!

#9 hampmeister

hampmeister
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:01:02 AM

Posted 18 July 2011 - 08:52 AM

I deinstalled QuickTime (the source of qttask) and I'll reboot, then run DSS and qmer again, and post the logs separately.

#10 hampmeister

hampmeister
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:01:02 AM

Posted 18 July 2011 - 09:03 AM

@Zooma I found it in my registry too, masquerading under some entry called Search (something). Search your registry for hello4. I backed up my registry (years of troubleshooting computers have taught me to be VERY cautious) then deleted the whole key with no ill effects.

#11 Zoooma

Zoooma

  • Members
  • 23 posts
  • OFFLINE
  •  
  • Local time:04:02 AM

Posted 18 July 2011 - 09:08 AM

@Zooma I found it in my registry too, masquerading under some entry called Search (something). Search your registry for hello4. I backed up my registry (years of troubleshooting computers have taught me to be VERY cautious) then deleted the whole key with no ill effects.


Hampmeister -- Thanks but i have no idea how to search my registry.
My knowledge is basic so I've just got to follow simple instructions here to get rid of this thing.

I've been working on those Steps 6-9 and I guess I'll have to post my logs in a new topic.

#12 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,534 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:02 AM

Posted 18 July 2011 - 09:30 AM

If you are not comfortable in the registry stay out! Follow the Prep guide and you will be helped.


For future references..A suggestion has been made that involves modifying the registry. Modifying the registry can be dangerous (and can render your system unbootable) so it's advisable that you make a backup of the registry before proceeding.
Modification of the registry can be EXTREMELY dangerous if you do not know exactly what you are doing so follow the steps that are listed below EXACTLY. if you cannot perform some of these steps or if you have ANY questions please ask BEFORE proceeding.

Backing Up Your Registry
  • Go Here and download ERUNT
    (ERUNT (Emergency Recovery Utility NT) is a free program that allows you to keep a complete backup of your registry and restore it when needed.)
  • Install ERUNT by following the prompts
    (use the default install settings but say no to the portion that asks you to add ERUNT to the start-up folder, if you like you can enable this option later)
  • Start ERUNT
    (either by double clicking on the desktop icon or choosing to start the program at the end of the setup)
  • Choose a location for the backup
    (the default location is C:\WINDOWS\ERDNT which is acceptable).
  • Make sure that at least the first two check boxes are ticked
  • Press OK
  • Press YES to create the folder.
Registry Modifications

For more information about modifying the registry, see this Microsoft article: http://support.microsoft.com/default.aspx/kb/256986
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

#13 hampmeister

hampmeister
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:01:02 AM

Posted 18 July 2011 - 10:02 AM

I want to echo and reemphasize boopme's warning. There's no shame in being a newbie, and much wisdom in knowing it and acting accordingly. I've been troubleshooting IS issues for 30 years...and I deal mostly with UNIX-based systems and humbly ask help from the gurus here when I need it. *And* I preach backup endlessly to my customers.

#14 hampmeister

hampmeister
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:01:02 AM

Posted 18 July 2011 - 01:10 PM

A new error since running DSS and qmer: Inetcpl.cpl Missing entry: ClearMyTracksByProcess

I am at work nos so running Cisco VPN. Can I still run those programs?

#15 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,534 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:03:02 AM

Posted 18 July 2011 - 02:52 PM

This would mean your Inetcpl.cpl file got corrupted ,this file belongs to Internet Explorer,Uninstall and reinstall Internet Explorer that will fix the problem.

OR
If you cannot get DDS to work, please try this instead.

Please download RSIT by random/random from the link provided for your operating system and save it to your desktop.
Link 1 for 32-bit version
Link 2 for 32-bit version

Link 1 for 64-bit version
Link 2 for 64-bit versionThis tool needs to run while the computer is connected to the Internet so it can download HijackThis if it is not located on your system. If you get a warning from your firewall or other security programs regarding RSIT attempting to contact the Internet, please allow the connection.

  • Close all applications and windows so that you have nothing open and are at your Desktop.
  • Double-click on RSIT.exe to start the program.
    If using Windows Vista, be sure to Run As Administrator.
  • Read the disclaimer and click Continue.
  • When the scan is complete, a text file named log.txt will automatically open in Notepad.
  • Another text file named info.txt will open minimized.
  • Save the log files to your desktop and copy/paste the contents of log.txt by highlighting everything and pressing Ctrl+C.
  • After highlighting, right-click, choose Copy and then paste the contents into a new topic in the Virus, Trojan, Spyware, and Malware Removal Logs forum, NOT here.
  • Copies of both log files are automatically saved in the C:\RSIT folder which the tool creates during the scan.
-- Note: Do not post the contents of info.txt in your reply. Instead, just include it as an attachment to upload using the "Browse" button in the text editor when making your reply.

Important: Be sure to mention that you tried to follow the Prep Guide but were unable to get DDS to run. If RSIT did not work, then reply back here.
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