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

Google redirect virus or cookies or whatever


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

#1 psseashore

psseashore

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:11:40 PM

Posted 13 February 2011 - 12:01 PM

Like so many others, I have been plagued now for about 2 months with the Google redirect virus. When using Explorer or Mozilla, selecting the results from a Google search takes me to the most unexpected and unintended websites. Most often the redirect is to another search engine or on line yellow pages. I think it started when I accidentally activated "White Smoke", but I'm not totally sure. I have run Malewarebtyes anti-maleware numerous times. Sometimes it finds stuff, sometimes it doesn't. I have changed over to Norton 360. The scans find cookies but no viruses. I have spelunked around a little but just cannot shake this thing. Help would most certainly be appreciated. Thank you!

BC AdBot (Login to Remove)

 


#2 psseashore

psseashore
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:11:40 PM

Posted 13 February 2011 - 02:20 PM

Here is the last Malewarebytes log:

Malwarebytes' Anti-Malware 1.50.1.1100
www.malwarebytes.org

Database version: 5751

Windows 5.1.2600 Service Pack 3
Internet Explorer 8.0.6001.18702

2/13/2011 1:28:57 AM
mbam-log-2011-02-13 (01-28-57).txt

Scan type: Full scan (C:\|D:\|)
Objects scanned: 378661
Time elapsed: 1 hour(s), 19 minute(s), 55 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)

#3 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,331 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:11:40 PM

Posted 13 February 2011 - 03:16 PM

Hello,please run these next.

Please download the TDSS Rootkit Removing Tool (TDSSKiller.exe) and save it to your Desktop. <-Important!!!
Be sure to download TDSSKiller.exe (v2.4.0.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.


Please perform a scan with Eset Online Antiivirus Scanner.
This scan requires Internet Explorer,Opera or Firefox 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.
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

#4 psseashore

psseashore
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:11:40 PM

Posted 13 February 2011 - 03:20 PM

2011/02/13 15:27:21.0750 2972 TDSS rootkit removing tool

2.4.17.0 Feb 10 2011 11:07:20
2011/02/13 15:27:21.0890 2972

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

==============
2011/02/13 15:27:21.0890 2972 SystemInfo:
2011/02/13 15:27:21.0890 2972
2011/02/13 15:27:21.0890 2972 OS Version: 5.1.2600 ServicePack:

3.0
2011/02/13 15:27:21.0890 2972 Product type: Workstation
2011/02/13 15:27:21.0890 2972 ComputerName: HP_MEDIA_CENTER
2011/02/13 15:27:21.0890 2972 UserName: Seashore
2011/02/13 15:27:21.0890 2972 Windows directory: C:\WINDOWS
2011/02/13 15:27:21.0890 2972 System windows directory:

C:\WINDOWS
2011/02/13 15:27:21.0890 2972 Processor architecture: Intel x86
2011/02/13 15:27:21.0890 2972 Number of processors: 2
2011/02/13 15:27:21.0890 2972 Page size: 0x1000
2011/02/13 15:27:21.0890 2972 Boot type: Normal boot
2011/02/13 15:27:21.0890 2972

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

==============
2011/02/13 15:27:22.0203 2972 Initialize success
2011/02/13 15:27:25.0968 2556

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

==============
2011/02/13 15:27:25.0968 2556 Scan started
2011/02/13 15:27:25.0968 2556 Mode: Manual;
2011/02/13 15:27:25.0968 2556

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

==============
2011/02/13 15:27:26.0515 2556 ACPI

(8fd99680a539792a30e97944fdaecf17)

C:\WINDOWS\system32\DRIVERS\ACPI.sys
2011/02/13 15:27:26.0593 2556 ACPIEC

(9859c0f6936e723e4892d7141b1327d5)

C:\WINDOWS\system32\drivers\ACPIEC.sys
2011/02/13 15:27:26.0703 2556 aec

(8bed39e3c35d6a489438b8141717a557)

C:\WINDOWS\system32\drivers\aec.sys
2011/02/13 15:27:26.0734 2556 AFD

(7e775010ef291da96ad17ca4b17137d7)

C:\WINDOWS\System32\drivers\afd.sys
2011/02/13 15:27:26.0796 2556 AgereSoftModem

(51a66c689ad9b9a953f75496209ae520)

C:\WINDOWS\system32\DRIVERS\AGRSM.sys
2011/02/13 15:27:27.0000 2556 ALCXWDM

(7f26d024355cbadb60838f53dfb171ec)

C:\WINDOWS\system32\drivers\ALCXWDM.SYS
2011/02/13 15:27:27.0296 2556 AmdK8

(59301936898ae62245a6f09c0aba9475)

C:\WINDOWS\system32\DRIVERS\AmdK8.sys
2011/02/13 15:27:27.0375 2556 aracpi

(00523019e3579c8f8a94457fe25f0f24)

C:\WINDOWS\system32\DRIVERS\aracpi.sys
2011/02/13 15:27:27.0406 2556 arhidfltr

(9fedaa46eb1a572ac4d9ee6b5f123cf2)

C:\WINDOWS\system32\DRIVERS\arhidfltr.sys
2011/02/13 15:27:27.0437 2556 arkbcfltr

(82969576093cd983dd559f5a86f382b4)

C:\WINDOWS\system32\DRIVERS\arkbcfltr.sys
2011/02/13 15:27:27.0484 2556 armoucfltr

(9b21791d8a78faece999fadbebda6c22)

C:\WINDOWS\system32\DRIVERS\armoucfltr.sys
2011/02/13 15:27:27.0515 2556 Arp1394

(b5b8a80875c1dededa8b02765642c32f)

C:\WINDOWS\system32\DRIVERS\arp1394.sys
2011/02/13 15:27:27.0578 2556 ARPolicy

(7a2da7c7b0c524ef26a79f17a5c69fde)

C:\WINDOWS\system32\DRIVERS\arpolicy.sys
2011/02/13 15:27:27.0687 2556 AsyncMac

(b153affac761e7f5fcfa822b9c4e97bc)

C:\WINDOWS\system32\DRIVERS\asyncmac.sys
2011/02/13 15:27:27.0718 2556 atapi

(9f3a2f5aa6875c72bf062c712cfa2674)

C:\WINDOWS\system32\DRIVERS\atapi.sys
2011/02/13 15:27:27.0828 2556 ati2mtag

(7a6cf9f411a9c5bd5c442a1cd46af401)

C:\WINDOWS\system32\DRIVERS\ati2mtag.sys
2011/02/13 15:27:27.0890 2556 Atmarpc

(9916c1225104ba14794209cfa8012159)

C:\WINDOWS\system32\DRIVERS\atmarpc.sys
2011/02/13 15:27:27.0921 2556 audstub

(d9f724aa26c010a217c97606b160ed68)

C:\WINDOWS\system32\DRIVERS\audstub.sys
2011/02/13 15:27:27.0953 2556 Beep

(da1f27d85e0d1525f6621372e7b685e9)

C:\WINDOWS\system32\drivers\Beep.sys
2011/02/13 15:27:28.0156 2556 BHDrvx86

(83a2fec59a0a0fc73bf6598e901b2fbd) C:\Documents and Settings\All

Users\Application

Data\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\N360_4.1.0.32\D

efinitions\BASHDefs\20110114.001\BHDrvx86.sys
2011/02/13 15:27:28.0296 2556 BVRPMPR5

(248dfa5762dde38dfddbbd44149e9d7a)

C:\WINDOWS\system32\drivers\BVRPMPR5.SYS
2011/02/13 15:27:28.0343 2556 cbidf2k

(90a673fc8e12a79afbed2576f6a7aaf9)

C:\WINDOWS\system32\drivers\cbidf2k.sys
2011/02/13 15:27:28.0421 2556 CCDECODE

(0be5aef125be881c4f854c554f2b025c)

C:\WINDOWS\system32\DRIVERS\CCDECODE.sys
2011/02/13 15:27:28.0531 2556 ccHP

(e941e709847fa00e0dd6d58d2b8fb5e1)

C:\WINDOWS\system32\drivers\N360\0403000.005\ccHPx86.sys
2011/02/13 15:27:28.0671 2556 Cdaudio

(c1b486a7658353d33a10cc15211a873b)

C:\WINDOWS\system32\drivers\Cdaudio.sys
2011/02/13 15:27:28.0734 2556 Cdfs

(c885b02847f5d2fd45a24e219ed93b32)

C:\WINDOWS\system32\drivers\Cdfs.sys
2011/02/13 15:27:28.0796 2556 Cdrom

(1f4260cc5b42272d71f79e570a27a4fe)

C:\WINDOWS\system32\DRIVERS\cdrom.sys
2011/02/13 15:27:29.0031 2556 CXFALCON

(047360193298e8abe8e0d978cc1a21c6)

C:\WINDOWS\system32\drivers\cxfalcon.sys
2011/02/13 15:27:29.0187 2556 Disk

(044452051f3e02e7963599fc8f4f3e25)

C:\WINDOWS\system32\DRIVERS\disk.sys
2011/02/13 15:27:29.0281 2556 dmboot

(d992fe1274bde0f84ad826acae022a41)

C:\WINDOWS\system32\drivers\dmboot.sys
2011/02/13 15:27:29.0359 2556 dmio

(7c824cf7bbde77d95c08005717a95f6f)

C:\WINDOWS\system32\drivers\dmio.sys
2011/02/13 15:27:29.0406 2556 dmload

(e9317282a63ca4d188c0df5e09c6ac5f)

C:\WINDOWS\system32\drivers\dmload.sys
2011/02/13 15:27:29.0468 2556 DMusic

(8a208dfcf89792a484e76c40e5f50b45)

C:\WINDOWS\system32\drivers\DMusic.sys
2011/02/13 15:27:29.0593 2556 drmkaud

(8f5fcff8e8848afac920905fbd9d33c8)

C:\WINDOWS\system32\drivers\drmkaud.sys
2011/02/13 15:27:29.0687 2556 eeCtrl

(089296aedb9b72b4916ac959752bdc89) C:\Program Files\Common

Files\Symantec Shared\EENGINE\eeCtrl.sys
2011/02/13 15:27:29.0734 2556 EraserUtilRebootDrv

(850259334652d392e33ee3412562e583) C:\Program Files\Common

Files\Symantec Shared\EENGINE\EraserUtilRebootDrv.sys
2011/02/13 15:27:29.0875 2556 Fastfat

(38d332a6d56af32635675f132548343e)

C:\WINDOWS\system32\drivers\Fastfat.sys
2011/02/13 15:27:29.0937 2556 Fdc

(92cdd60b6730b9f50f6a1a0c1f8cdc81)

C:\WINDOWS\system32\DRIVERS\fdc.sys
2011/02/13 15:27:30.0000 2556 Fips

(d45926117eb9fa946a6af572fbe1caa3)

C:\WINDOWS\system32\drivers\Fips.sys
2011/02/13 15:27:30.0062 2556 Flpydisk

(9d27e7b80bfcdf1cdd9b555862d5e7f0)

C:\WINDOWS\system32\DRIVERS\flpydisk.sys
2011/02/13 15:27:30.0093 2556 FltMgr

(b2cf4b0786f8212cb92ed2b50c6db6b0)

C:\WINDOWS\system32\drivers\fltmgr.sys
2011/02/13 15:27:30.0171 2556 Fs_Rec

(3e1e2bd4f39b0e2b7dc4f4d2bcc2779a)

C:\WINDOWS\system32\drivers\Fs_Rec.sys
2011/02/13 15:27:30.0203 2556 Ftdisk

(6ac26732762483366c3969c9e4d2259d)

C:\WINDOWS\system32\DRIVERS\ftdisk.sys
2011/02/13 15:27:30.0250 2556 gagp30kx

(3a74c423cf6bcca6982715878f450a3b)

C:\WINDOWS\system32\DRIVERS\gagp30kx.sys
2011/02/13 15:27:30.0296 2556 GEARAspiWDM

(8182ff89c65e4d38b2de4bb0fb18564e)

C:\WINDOWS\system32\Drivers\GEARAspiWDM.sys
2011/02/13 15:27:30.0343 2556 Gpc

(0a02c63c8b144bd8c86b103dee7c86a2)

C:\WINDOWS\system32\DRIVERS\msgpc.sys
2011/02/13 15:27:30.0421 2556 HidIr

(bb1a6fb7d35a91e599973fa74a619056)

C:\WINDOWS\system32\DRIVERS\hidir.sys
2011/02/13 15:27:30.0437 2556 HidUsb

(ccf82c5ec8a7326c3066de870c06daf1)

C:\WINDOWS\system32\DRIVERS\hidusb.sys
2011/02/13 15:27:30.0562 2556 HTTP

(f80a415ef82cd06ffaf0d971528ead38)

C:\WINDOWS\system32\Drivers\HTTP.sys
2011/02/13 15:27:30.0687 2556 i8042prt

(4a0b06aa8943c1e332520f7440c0aa30)

C:\WINDOWS\system32\DRIVERS\i8042prt.sys
2011/02/13 15:27:30.0734 2556 iaStor

(9a65e42664d1534b68512caad0efe963)

C:\WINDOWS\system32\DRIVERS\iaStor.sys
2011/02/13 15:27:30.0890 2556 IDSxpx86

(0308238c582a55d83d34feee39542793) C:\Documents and Settings\All

Users\Application

Data\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\N360_4.1.0.32\D

efinitions\IPSDefs\20110211.002\IDSxpx86.sys
2011/02/13 15:27:31.0000 2556 Imapi

(083a052659f5310dd8b6a6cb05edcf8e)

C:\WINDOWS\system32\DRIVERS\imapi.sys
2011/02/13 15:27:31.0125 2556 IntelIde

(b5466a9250342a7aa0cd1fba13420678)

C:\WINDOWS\system32\DRIVERS\intelide.sys
2011/02/13 15:27:31.0187 2556 intelppm

(8c953733d8f36eb2133f5bb58808b66b)

C:\WINDOWS\system32\DRIVERS\intelppm.sys
2011/02/13 15:27:31.0250 2556 Ip6Fw

(3bb22519a194418d5fec05d800a19ad0)

C:\WINDOWS\system32\drivers\ip6fw.sys
2011/02/13 15:27:31.0343 2556 IpFilterDriver

(731f22ba402ee4b62748adaf6363c182)

C:\WINDOWS\system32\DRIVERS\ipfltdrv.sys
2011/02/13 15:27:31.0390 2556 IpInIp

(b87ab476dcf76e72010632b5550955f5)

C:\WINDOWS\system32\DRIVERS\ipinip.sys
2011/02/13 15:27:31.0421 2556 IpNat

(cc748ea12c6effde940ee98098bf96bb)

C:\WINDOWS\system32\DRIVERS\ipnat.sys
2011/02/13 15:27:31.0453 2556 IPSec

(23c74d75e36e7158768dd63d92789a91)

C:\WINDOWS\system32\DRIVERS\ipsec.sys
2011/02/13 15:27:31.0515 2556 IrBus

(b43b36b382aea10861f7c7a37f9d4ae2)

C:\WINDOWS\system32\DRIVERS\IrBus.sys
2011/02/13 15:27:31.0546 2556 IRENUM

(c93c9ff7b04d772627a3646d89f7bf89)

C:\WINDOWS\system32\DRIVERS\irenum.sys
2011/02/13 15:27:31.0593 2556 isapnp

(05a299ec56e52649b1cf2fc52d20f2d7)

C:\WINDOWS\system32\DRIVERS\isapnp.sys
2011/02/13 15:27:31.0656 2556 Kbdclass

(463c1ec80cd17420a542b7f36a36f128)

C:\WINDOWS\system32\DRIVERS\kbdclass.sys
2011/02/13 15:27:31.0687 2556 kbdhid

(9ef487a186dea361aa06913a75b3fa99)

C:\WINDOWS\system32\DRIVERS\kbdhid.sys
2011/02/13 15:27:31.0718 2556 kmixer

(692bcf44383d056aed41b045a323d378)

C:\WINDOWS\system32\drivers\kmixer.sys
2011/02/13 15:27:31.0781 2556 KSecDD

(b467646c54cc746128904e1654c750c1)

C:\WINDOWS\system32\drivers\KSecDD.sys
2011/02/13 15:27:31.0921 2556 LMIInfo

(4f69faaabb7db0d43e327c0b6aab40fc) C:\Program

Files\LogMeIn\x86\RaInfo.sys
2011/02/13 15:27:32.0046 2556 lmimirr

(4477689e2d8ae6b78ba34c9af4cc1ed1)

C:\WINDOWS\system32\DRIVERS\lmimirr.sys
2011/02/13 15:27:32.0140 2556 LMIRfsDriver

(3faa563ddf853320f90259d455a01d79)

C:\WINDOWS\system32\drivers\LMIRfsDriver.sys
2011/02/13 15:27:32.0218 2556 MCSTRM

(5bb01b9f582259d1fb7653c5c1da3653)

C:\WINDOWS\system32\drivers\MCSTRM.sys
2011/02/13 15:27:32.0328 2556 MHNDRV

(7f2f1d2815a6449d346fcccbc569fbd6)

C:\WINDOWS\system32\DRIVERS\mhndrv.sys
2011/02/13 15:27:32.0390 2556 mnmdd

(4ae068242760a1fb6e1a44bf4e16afa6)

C:\WINDOWS\system32\drivers\mnmdd.sys
2011/02/13 15:27:32.0437 2556 Modem

(dfcbad3cec1c5f964962ae10e0bcc8e1)

C:\WINDOWS\system32\drivers\Modem.sys
2011/02/13 15:27:32.0484 2556 Mouclass

(35c9e97194c8cfb8430125f8dbc34d04)

C:\WINDOWS\system32\DRIVERS\mouclass.sys
2011/02/13 15:27:32.0500 2556 mouhid

(b1c303e17fb9d46e87a98e4ba6769685)

C:\WINDOWS\system32\DRIVERS\mouhid.sys
2011/02/13 15:27:32.0562 2556 MountMgr

(a80b9a0bad1b73637dbcbba7df72d3fd)

C:\WINDOWS\system32\drivers\MountMgr.sys
2011/02/13 15:27:32.0640 2556 MRxDAV

(11d42bb6206f33fbb3ba0288d3ef81bd)

C:\WINDOWS\system32\DRIVERS\mrxdav.sys
2011/02/13 15:27:32.0687 2556 MRxSmb

(f3aefb11abc521122b67095044169e98)

C:\WINDOWS\system32\DRIVERS\mrxsmb.sys
2011/02/13 15:27:32.0734 2556 Msfs

(c941ea2454ba8350021d774daf0f1027)

C:\WINDOWS\system32\drivers\Msfs.sys
2011/02/13 15:27:32.0765 2556 MSKSSRV

(d1575e71568f4d9e14ca56b7b0453bf1)

C:\WINDOWS\system32\drivers\MSKSSRV.sys
2011/02/13 15:27:32.0796 2556 MSPCLOCK

(325bb26842fc7ccc1fcce2c457317f3e)

C:\WINDOWS\system32\drivers\MSPCLOCK.sys
2011/02/13 15:27:32.0859 2556 MSPQM

(bad59648ba099da4a17680b39730cb3d)

C:\WINDOWS\system32\drivers\MSPQM.sys
2011/02/13 15:27:32.0890 2556 mssmbios

(af5f4f3f14a8ea2c26de30f7a1e17136)

C:\WINDOWS\system32\DRIVERS\mssmbios.sys
2011/02/13 15:27:32.0937 2556 MSTEE

(e53736a9e30c45fa9e7b5eac55056d1d)

C:\WINDOWS\system32\drivers\MSTEE.sys
2011/02/13 15:27:32.0968 2556 Mup

(2f625d11385b1a94360bfc70aaefdee1)

C:\WINDOWS\system32\drivers\Mup.sys
2011/02/13 15:27:33.0015 2556 NABTSFEC

(5b50f1b2a2ed47d560577b221da734db)

C:\WINDOWS\system32\DRIVERS\NABTSFEC.sys
2011/02/13 15:27:33.0140 2556 NAVENG

(c8ef74e4d8105b1d02d58ea4734cf616) C:\Documents and Settings\All

Users\Application

Data\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\N360_4.1.0.32\D

efinitions\VirusDefs\20110213.003\NAVENG.SYS
2011/02/13 15:27:33.0203 2556 NAVEX15

(94b3164055d821a62944d9fe84036470) C:\Documents and Settings\All

Users\Application

Data\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\N360_4.1.0.32\D

efinitions\VirusDefs\20110213.003\NAVEX15.SYS
2011/02/13 15:27:33.0312 2556 NDIS

(1df7f42665c94b825322fae71721130d)

C:\WINDOWS\system32\drivers\NDIS.sys
2011/02/13 15:27:33.0359 2556 NdisIP

(7ff1f1fd8609c149aa432f95a8163d97)

C:\WINDOWS\system32\DRIVERS\NdisIP.sys
2011/02/13 15:27:33.0421 2556 NdisTapi

(1ab3d00c991ab086e69db84b6c0ed78f)

C:\WINDOWS\system32\DRIVERS\ndistapi.sys
2011/02/13 15:27:33.0453 2556 Ndisuio

(f927a4434c5028758a842943ef1a3849)

C:\WINDOWS\system32\DRIVERS\ndisuio.sys
2011/02/13 15:27:33.0515 2556 NdisWan

(edc1531a49c80614b2cfda43ca8659ab)

C:\WINDOWS\system32\DRIVERS\ndiswan.sys
2011/02/13 15:27:33.0593 2556 NDProxy

(9282bd12dfb069d3889eb3fcc1000a9b)

C:\WINDOWS\system32\drivers\NDProxy.sys
2011/02/13 15:27:33.0656 2556 NetBIOS

(5d81cf9a2f1a3a756b66cf684911cdf0)

C:\WINDOWS\system32\DRIVERS\netbios.sys
2011/02/13 15:27:33.0687 2556 NetBT

(74b2b2f5bea5e9a3dc021d685551bd3d)

C:\WINDOWS\system32\DRIVERS\netbt.sys
2011/02/13 15:27:33.0765 2556 NIC1394

(e9e47cfb2d461fa0fc75b7a74c6383ea)

C:\WINDOWS\system32\DRIVERS\nic1394.sys
2011/02/13 15:27:33.0828 2556 Npfs

(3182d64ae053d6fb034f44b6def8034a)

C:\WINDOWS\system32\drivers\Npfs.sys
2011/02/13 15:27:33.0890 2556 Ntfs

(78a08dd6a8d65e697c18e1db01c5cdca)

C:\WINDOWS\system32\drivers\Ntfs.sys
2011/02/13 15:27:33.0968 2556 Null

(73c1e1f395918bc2c6dd67af7591a3ad)

C:\WINDOWS\system32\drivers\Null.sys
2011/02/13 15:27:34.0109 2556 nv

(ba1b732c1a70cfea0c1b64f2850bf44f)

C:\WINDOWS\system32\DRIVERS\nv4_mini.sys
2011/02/13 15:27:34.0187 2556 NwlnkFlt

(b305f3fad35083837ef46a0bbce2fc57)

C:\WINDOWS\system32\DRIVERS\nwlnkflt.sys
2011/02/13 15:27:34.0234 2556 NwlnkFwd

(c99b3415198d1aab7227f2c88fd664b9)

C:\WINDOWS\system32\DRIVERS\nwlnkfwd.sys
2011/02/13 15:27:34.0312 2556 ohci1394

(ca33832df41afb202ee7aeb05145922f)

C:\WINDOWS\system32\DRIVERS\ohci1394.sys
2011/02/13 15:27:34.0375 2556 Parport

(5575faf8f97ce5e713d108c2a58d7c7c)

C:\WINDOWS\system32\DRIVERS\parport.sys
2011/02/13 15:27:34.0421 2556 PartMgr

(beb3ba25197665d82ec7065b724171c6)

C:\WINDOWS\system32\drivers\PartMgr.sys
2011/02/13 15:27:34.0500 2556 ParVdm

(70e98b3fd8e963a6a46a2e6247e0bea1)

C:\WINDOWS\system32\drivers\ParVdm.sys
2011/02/13 15:27:34.0578 2556 PCI

(a219903ccf74233761d92bef471a07b1)

C:\WINDOWS\system32\DRIVERS\pci.sys
2011/02/13 15:27:34.0656 2556 PCIIde

(ccf5f451bb1a5a2a522a76e670000ff0)

C:\WINDOWS\system32\DRIVERS\pciide.sys
2011/02/13 15:27:34.0703 2556 Pcmcia

(9e89ef60e9ee05e3f2eef2da7397f1c1)

C:\WINDOWS\system32\drivers\Pcmcia.sys
2011/02/13 15:27:35.0046 2556 PptpMiniport

(efeec01b1d3cf84f16ddd24d9d9d8f99)

C:\WINDOWS\system32\DRIVERS\raspptp.sys
2011/02/13 15:27:35.0093 2556 Processor

(a32bebaf723557681bfc6bd93e98bd26)

C:\WINDOWS\system32\DRIVERS\processr.sys
2011/02/13 15:27:35.0187 2556 Ps2

(390c204ced3785609ab24e9c52054a84)

C:\WINDOWS\system32\DRIVERS\PS2.sys
2011/02/13 15:27:35.0218 2556 PSched

(09298ec810b07e5d582cb3a3f9255424)

C:\WINDOWS\system32\DRIVERS\psched.sys
2011/02/13 15:27:35.0281 2556 Ptilink

(80d317bd1c3dbc5d4fe7b1678c60cadd)

C:\WINDOWS\system32\DRIVERS\ptilink.sys
2011/02/13 15:27:35.0359 2556 PxHelp20

(86724469cd077901706854974cd13c3e)

C:\WINDOWS\system32\Drivers\PxHelp20.sys
2011/02/13 15:27:35.0562 2556 RasAcd

(fe0d99d6f31e4fad8159f690d68ded9c)

C:\WINDOWS\system32\DRIVERS\rasacd.sys
2011/02/13 15:27:35.0640 2556 Rasl2tp

(11b4a627bc9614b885c4969bfa5ff8a6)

C:\WINDOWS\system32\DRIVERS\rasl2tp.sys
2011/02/13 15:27:35.0687 2556 RasPppoe

(5bc962f2654137c9909c3d4603587dee)

C:\WINDOWS\system32\DRIVERS\raspppoe.sys
2011/02/13 15:27:35.0703 2556 Raspti

(fdbb1d60066fcfbb7452fd8f9829b242)

C:\WINDOWS\system32\DRIVERS\raspti.sys
2011/02/13 15:27:35.0765 2556 Rdbss

(7ad224ad1a1437fe28d89cf22b17780a)

C:\WINDOWS\system32\DRIVERS\rdbss.sys
2011/02/13 15:27:35.0828 2556 RDPCDD

(4912d5b403614ce99c28420f75353332)

C:\WINDOWS\system32\DRIVERS\RDPCDD.sys
2011/02/13 15:27:35.0906 2556 rdpdr

(15cabd0f7c00c47c70124907916af3f1)

C:\WINDOWS\system32\DRIVERS\rdpdr.sys
2011/02/13 15:27:35.0953 2556 RDPWD

(6728e45b66f93c08f11de2e316fc70dd)

C:\WINDOWS\system32\drivers\RDPWD.sys
2011/02/13 15:27:35.0984 2556 redbook

(f828dd7e1419b6653894a8f97a0094c5)

C:\WINDOWS\system32\DRIVERS\redbook.sys
2011/02/13 15:27:36.0078 2556 RTL8023xp

(7889e3981e0a5d347e037abd467d53a5)

C:\WINDOWS\system32\DRIVERS\Rtnicxp.sys
2011/02/13 15:27:36.0125 2556 rtl8139

(d507c1400284176573224903819ffda3)

C:\WINDOWS\system32\DRIVERS\RTL8139.SYS
2011/02/13 15:27:36.0171 2556 Secdrv

(90a3935d05b494a5a39d37e71f09a677)

C:\WINDOWS\system32\DRIVERS\secdrv.sys
2011/02/13 15:27:36.0203 2556 Serenum

(0f29512ccd6bead730039fb4bd2c85ce)

C:\WINDOWS\system32\DRIVERS\serenum.sys
2011/02/13 15:27:36.0250 2556 Serial

(cca207a8896d4c6a0c9ce29a4ae411a7)

C:\WINDOWS\system32\DRIVERS\serial.sys
2011/02/13 15:27:36.0328 2556 Sfloppy

(8e6b8c671615d126fdc553d1e2de5562)

C:\WINDOWS\system32\drivers\Sfloppy.sys
2011/02/13 15:27:36.0453 2556 SISNIC

(3fbb6ef8b5a71a2fa11f5f461bb73219)

C:\WINDOWS\system32\DRIVERS\sisnic.sys
2011/02/13 15:27:36.0515 2556 SLIP

(866d538ebe33709a5c9f5c62b73b7d14)

C:\WINDOWS\system32\DRIVERS\SLIP.sys
2011/02/13 15:27:36.0609 2556 splitter

(ab8b92451ecb048a4d1de7c3ffcb4a9f)

C:\WINDOWS\system32\drivers\splitter.sys
2011/02/13 15:27:36.0671 2556 sr

(76bb022c2fb6902fd5bdd4f78fc13a5d)

C:\WINDOWS\system32\DRIVERS\sr.sys
2011/02/13 15:27:36.0750 2556 SRTSP

(ec5c3c6260f4019b03dfaa03ec8cbf6a)

C:\WINDOWS\System32\Drivers\N360\0403000.005\SRTSP.SYS
2011/02/13 15:27:36.0781 2556 SRTSPX

(55d5c37ed41231e3ac2063d16df50840)

C:\WINDOWS\system32\drivers\N360\0403000.005\SRTSPX.SYS
2011/02/13 15:27:36.0828 2556 Srv

(0f6aefad3641a657e18081f52d0c15af)

C:\WINDOWS\system32\DRIVERS\srv.sys
2011/02/13 15:27:36.0937 2556 streamip

(77813007ba6265c4b6098187e6ed79d2)

C:\WINDOWS\system32\DRIVERS\StreamIP.sys
2011/02/13 15:27:36.0984 2556 swenum

(3941d127aef12e93addf6fe6ee027e0f)

C:\WINDOWS\system32\DRIVERS\swenum.sys
2011/02/13 15:27:37.0046 2556 swmidi

(8ce882bcc6cf8a62f2b2323d95cb3d01)

C:\WINDOWS\system32\drivers\swmidi.sys
2011/02/13 15:27:37.0171 2556 SymDS

(56890bf9d9204b93042089d4b45ae671)

C:\WINDOWS\system32\drivers\N360\0403000.005\SYMDS.SYS
2011/02/13 15:27:37.0203 2556 SymEFA

(1c91df5188150510a6f0cf78f7d94b69)

C:\WINDOWS\system32\drivers\N360\0403000.005\SYMEFA.SYS
2011/02/13 15:27:37.0250 2556 SymEvent

(961b48b86f94d4cc8ceb483f8aa89374)

C:\WINDOWS\system32\Drivers\SYMEVENT.SYS
2011/02/13 15:27:37.0296 2556 SymIRON

(dc80fbf0a348e54853ef82eed4e11e35)

C:\WINDOWS\system32\drivers\N360\0403000.005\Ironx86.SYS
2011/02/13 15:27:37.0343 2556 SYMTDI

(41aad61f87ca8e3b5d0f7fe7fba0797d)

C:\WINDOWS\System32\Drivers\N360\0403000.005\SYMTDI.SYS
2011/02/13 15:27:37.0921 2556 sysaudio

(8b83f3ed0f1688b4958f77cd6d2bf290)

C:\WINDOWS\system32\drivers\sysaudio.sys
2011/02/13 15:27:38.0203 2556 Tcpip

(9aefa14bd6b182d61e3119fa5f436d3d)

C:\WINDOWS\system32\DRIVERS\tcpip.sys
2011/02/13 15:27:38.0578 2556 TDPIPE

(6471a66807f5e104e4885f5b67349397)

C:\WINDOWS\system32\drivers\TDPIPE.sys
2011/02/13 15:27:38.0781 2556 TDTCP

(c56b6d0402371cf3700eb322ef3aaf61)

C:\WINDOWS\system32\drivers\TDTCP.sys
2011/02/13 15:27:38.0875 2556 TermDD

(88155247177638048422893737429d9e)

C:\WINDOWS\system32\DRIVERS\termdd.sys
2011/02/13 15:27:39.0000 2556 Udfs

(5787b80c2e3c5e2f56c2a233d91fa2c9)

C:\WINDOWS\system32\drivers\Udfs.sys
2011/02/13 15:27:39.0093 2556 Update

(402ddc88356b1bac0ee3dd1580c76a31)

C:\WINDOWS\system32\DRIVERS\update.sys
2011/02/13 15:27:39.0156 2556 USBAAPL

(5c2bdc152bbab34f36473deaf7713f22)

C:\WINDOWS\system32\Drivers\usbaapl.sys
2011/02/13 15:27:39.0203 2556 usbccgp

(173f317ce0db8e21322e71b7e60a27e8)

C:\WINDOWS\system32\DRIVERS\usbccgp.sys
2011/02/13 15:27:39.0250 2556 usbehci

(65dcf09d0e37d4c6b11b5b0b76d470a7)

C:\WINDOWS\system32\DRIVERS\usbehci.sys
2011/02/13 15:27:39.0281 2556 usbhub

(1ab3cdde553b6e064d2e754efe20285c)

C:\WINDOWS\system32\DRIVERS\usbhub.sys
2011/02/13 15:27:39.0328 2556 usbohci

(0daecce65366ea32b162f85f07c6753b)

C:\WINDOWS\system32\DRIVERS\usbohci.sys
2011/02/13 15:27:39.0375 2556 usbprint

(a717c8721046828520c9edf31288fc00)

C:\WINDOWS\system32\DRIVERS\usbprint.sys
2011/02/13 15:27:39.0421 2556 usbscan

(a0b8cf9deb1184fbdd20784a58fa75d4)

C:\WINDOWS\system32\DRIVERS\usbscan.sys
2011/02/13 15:27:39.0468 2556 usbstor

(a32426d9b14a089eaa1d922e0c5801a9)

C:\WINDOWS\system32\DRIVERS\USBSTOR.SYS
2011/02/13 15:27:39.0531 2556 usbuhci

(26496f9dee2d787fc3e61ad54821ffe6)

C:\WINDOWS\system32\DRIVERS\usbuhci.sys
2011/02/13 15:27:39.0578 2556 VgaSave

(0d3a8fafceacd8b7625cd549757a7df1)

C:\WINDOWS\System32\drivers\vga.sys
2011/02/13 15:27:39.0609 2556 ViaIde

(3b3efcda263b8ac14fdf9cbdd0791b2e)

C:\WINDOWS\system32\DRIVERS\viaide.sys
2011/02/13 15:27:39.0656 2556 VolSnap

(4c8fcb5cc53aab716d810740fe59d025)

C:\WINDOWS\system32\drivers\VolSnap.sys
2011/02/13 15:27:39.0765 2556 wacmoumonitor

(026d58e9d7701f6b26b0b499f1705334)

C:\WINDOWS\system32\DRIVERS\wacmoumonitor.sys
2011/02/13 15:27:39.0812 2556 wacommousefilter

(427a8bc96f16c40df81c2d2f4edd32dd)

C:\WINDOWS\system32\DRIVERS\wacommousefilter.sys
2011/02/13 15:27:39.0875 2556 wacomvhid

(846b58ea44bf8c92e4b59f4e2252c4c0)

C:\WINDOWS\system32\DRIVERS\wacomvhid.sys
2011/02/13 15:27:39.0953 2556 Wanarp

(e20b95baedb550f32dd489265c1da1f6)

C:\WINDOWS\system32\DRIVERS\wanarp.sys
2011/02/13 15:27:40.0046 2556 wdmaud

(6768acf64b18196494413695f0c3a00f)

C:\WINDOWS\system32\drivers\wdmaud.sys
2011/02/13 15:27:40.0171 2556 WN5301

(b72d232e46ff5ee2bd8f61498b748df7)

C:\WINDOWS\system32\DRIVERS\wn5301.sys
2011/02/13 15:27:40.0203 2556 WpdUsb

(cf4def1bf66f06964dc0d91844239104)

C:\WINDOWS\system32\DRIVERS\wpdusb.sys
2011/02/13 15:27:40.0234 2556 WSTCODEC

(c98b39829c2bbd34e454150633c62c78)

C:\WINDOWS\system32\DRIVERS\WSTCODEC.SYS
2011/02/13 15:27:40.0296 2556 WudfPf

(f15feafffbb3644ccc80c5da584e6311)

C:\WINDOWS\system32\DRIVERS\WudfPf.sys
2011/02/13 15:27:40.0343 2556 WudfRd

(28b524262bce6de1f7ef9f510ba3985b)

C:\WINDOWS\system32\DRIVERS\wudfrd.sys
2011/02/13 15:27:40.0406 2556

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

==============
2011/02/13 15:27:40.0406 2556 Scan finished
2011/02/13 15:27:40.0406 2556

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

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

Edited by psseashore, 13 February 2011 - 03:28 PM.


#5 psseashore

psseashore
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:11:40 PM

Posted 13 February 2011 - 08:14 PM

ESETSmartInstaller@High as downloader log:
all ok
# version=7
# OnlineScannerApp.exe=1.0.0.1
# OnlineScanner.ocx=1.0.0.6419
# api_version=3.0.2
# EOSSerial=f8e318b0ac88804ab064f529a33a1783
# end=finished
# remove_checked=true
# archives_checked=true
# unwanted_checked=true
# unsafe_checked=false
# antistealth_checked=true
# utc_time=2011-02-13 11:19:29
# local_time=2011-02-13 06:19:29 (-0500, Eastern Standard Time)
# country="United States"
# lang=1033
# osver=5.1.2600 NT Service Pack 3
# compatibility_mode=512 16777215 100 0 4142597 4142597 0 0
# compatibility_mode=3589 16777213 100 86 3886685 60907539 0 0
# compatibility_mode=8192 67108863 100 0 1819404 1819404 0 0
# scanned=172037
# found=0
# cleaned=0
# scan_time=9926
ESETSmartInstaller@High as downloader log:
all ok

#6 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,331 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:11:40 PM

Posted 13 February 2011 - 10:07 PM

I'm amazed but glad there were no more whitsmoke infections.

If still redirecting>>>
Change your DNS Servers:
  • Go to Posted Image > Run... and in the open box, type: cmd
  • Press OK or Hit Enter.
  • At the command prompt, type or copy/paste: ipconfig /flushdns
  • Hit Enter.
  • You will get a confirmation that the flush was successful.
  • Close the command box.
If the above commands did not resolve the problem, the next thing to try is to reset your network settings and Configure TCP/IP to use DNS.
  • Go to Posted Image > Control Panel, and choose Network Connections.
  • Right-click on your default connection, usually Local Area Connection or Dial-up Connection if you are using Dial-up, and and choose Properties.
  • Double-click on Internet Protocol (TCP/IP) or highlight it and select Properties.
  • Under the General tab, write down any settings in case you should need to change them back.
  • Select the button that says "Obtain an IP address automatically" or make sure the DNS server IP address is the same as provided by your ISP.
  • Select the button that says "Obtain DNS servers automatically".
  • If unknown Preferred or Alternate DNS servers are listed, uncheck the box that says "Use the following DNS server address".
  • Click OK twice to get out of the properties screen and restart your computer. If not prompted to reboot go ahead and reboot manually.
-- Vista users can refer to How to Change TCP/IP settings

CAUTION: It's possible that your ISP (Internet Service Provider) requires specific DNS settings here. Make sure you know if you need these settings or not BEFORE you make any changes or you may lose your Internet connection. If you're sure you do not need a specific DNS address,
then you may proceed.

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 psseashore

psseashore
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:11:40 PM

Posted 14 February 2011 - 05:44 PM

ipconfig /flushdns did not correct it.
Moving on to try the next suggestion.

Followed the next step: checked my Network connections for both the Local Area Connection and the Wireless Connection. Both were already set to "Obtain an IP address automatically" and "Obtain DNS servers automatically".

Unfortunately I am still experiencing the Google redirect, even through my Norton Safe Search. For example: did a google search, selected a legit site from the Google search, and got redirected to www.search.pro

Edited by psseashore, 14 February 2011 - 05:51 PM.


#8 psseashore

psseashore
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:11:40 PM

Posted 14 February 2011 - 06:16 PM

After continuing to get "redirected" in Mozilla Firefox, I thought I would try Windows Explorer 8 and much to my surprise I was not redirected. Closed out Windows Explorer 8, went back to Mozilla Firefox, and did not get redirected. I don't know if it is too early to declare a victory because I have had intermittent failures before, but so far so good. Now, any tips on what to do should the redirect come back?

#9 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,331 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:11:40 PM

Posted 14 February 2011 - 08:26 PM

You may have cleared it. But since your PC is running well and it will take 2 days to get a reply why not ask if you are clean here.
We'll get 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

#10 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:40 PM

Posted 15 February 2011 - 04:33 PM

Malware topic here: http://www.bleepingcomputer.com/forums/topic379670.html

Now that your log is properly posted, you should NOT make further changes to your computer (install/uninstall programs, use special fix tools, delete files, edit the registry, etc) unless advised by a 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 log you already posted. Further, any modifications you make on your own may cause confusion for the helper assisting you and could complicate the malware removal process which would extend the time it takes to clean your computer.

From this point on the 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. Once you have made your post and are waiting, please DO NOT make another reply until it has been responded to by a member of the 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 MR Team member is already assisting you and not open the thread to respond.

To avoid confusion, I am closing this topic.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users