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

feifeipingping


  • Please log in to reply
1 reply to this topic

#1 feifeipingping

feifeipingping

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:01:28 PM

Posted 11 October 2009 - 11:11 AM

I had the same problem. Google will redirect the website sometime to http://z43523673.cn, sometime to others.
This is the report. thanks

ROOTREPEAL © AD, 2007-2009
==================================================
Scan Start Time: 2009/10/11 10:47
Program Version: Version 1.3.5.0
Windows Version: Windows Vista SP1
==================================================

Drivers
-------------------
Name: dump_iaStor.sys
Image Path: C:\Windows\System32\Drivers\dump_iaStor.sys
Address: 0x91CB8000 Size: 778240 File Visible: No Signed: -
Status: -

Name: rootrepeal[1].sys
Image Path: C:\Windows\system32\drivers\rootrepeal[1].sys
Address: 0xA4D91000 Size: 49152 File Visible: No Signed: -
Status: -

Hidden/Locked Files
-------------------
Path: C:\hiberfil.sys
Status: Locked to the Windows API!

Path: C:\System Volume Information\{3808876b-c176-4e48-b7ae-04046e6cc752}
Status: Locked to the Windows API!

Path: C:\System Volume Information\{822bb5cf-b66b-11de-ac6c-001f3ad891a0}{3808876b-c176-4e48-b7ae-04046e6cc752}
Status: Locked to the Windows API!

Path: C:\System Volume Information\{86f1635c-b460-11de-a377-001f3ad891a0}{3808876b-c176-4e48-b7ae-04046e6cc752}
Status: Locked to the Windows API!

Path: C:\System Volume Information\{dbf3835c-b353-11de-9ee1-00219bd786f7}{3808876b-c176-4e48-b7ae-04046e6cc752}
Status: Locked to the Windows API!

Path: C:\System Volume Information\{dbf38362-b353-11de-9ee1-00219bd786f7}{3808876b-c176-4e48-b7ae-04046e6cc752}
Status: Locked to the Windows API!

Path: c:\programdata\mcafee\desktopprotection\onaccessscanlog.txt
Status: Allocation size mismatch (API: 991232, Raw: 987136)

Path: C:\Windows\winsxs\Catalogs\x86_policy.8.0.microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.762_none_8dd7dea5d5a7a18a.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.762_none_43efccf17831d131.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d1c738ec43578ea1.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022.8_none_60a5df56e60dc5df.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_policy.8.0.microsoft.vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.762_none_abac38a907ee8801.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_9193a620671dde41.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_microsoft.vc80.openmp_1fc8b3b9a1e18e3b_8.0.50727.762_none_7b33aa7d218504d2.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.2600.5581_none_ca930398c2d6127e.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_policy.1.0.microsoft.windows.gdiplus_6595b64144ccf1df_1.0.2600.5581_none_f6010a964b58ac52.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.762_none_8a14c0566bec5b24.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_4ddfc6cd11929a02.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.762_none_0c178a139ee2a7ed.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_8e053e8c6967ba9d.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Catalogs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022.8_none_bcb86ed6ac711f91.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Manifests\4849d54916203321a96dae7bbaa6534bad8527ac43ad476284d52f87f763b384.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Manifests\bd83dce340498e7c363093c2fc74dfb58e1ec17770453905172c7471fadd9333.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Manifests\989e628160e12c984a435d2bb2a335ad043e006646150c7b1f3bb52dccd842cc.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Manifests\71503c1b988fb27a41668f3ba35468d268daf07e8e79cf7b82a1ef64a8d213a1.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Manifests\d5ecf2ab9387e082648bbcccd6eceb9d67b096939150833d0ae3066b3a1a676e.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Manifests\ea23c2347043051e35d7731754b9494bbc1a5f4c767e23e9809936f02340620d.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Manifests\935df4549e21123a2efb986a707f54475380a037519679510e4b4dfc4bdb5767.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Manifests\b080e112e69d2e9c8e71acd39a81f0d469d837625ceb8ed73b5b87da1fd1424c.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Manifests\8b414e757cb8b153bff77dd00a36556aea3adab25ce15f3e8b184ffbf41ba7a2.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\Manifests\ef483ae0673e2975dd4224fe26749623c1c702b8b3fded10161417459e1771a7.cat
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\x86_microsoft-windows-m..-downlevelmanifests_31bf3856ad364e35_6.0.6001.18000_none_0278b57e8399bfdb\MI2095~1.MAN
Status: Locked to the Windows API!

Path: C:\Windows\winsxs\x86_policy.1.2.microsof..op.security.azroles_31bf3856ad364e35_6.0.6000.16386_none_ea83414c2e75b887\Microsoft.Interop.Security.AzRoles.config
Status: Locked to the Windows API!

Path: C:\Windows\Microsoft.NET\Framework\v2.0.50727\SYSTEM~1.DLL
Status: Locked to the Windows API!

Path: C:\Windows\System32\migwiz\dlmanifests\MI2095~1.MAN
Status: Locked to the Windows API!

Path: C:\Windows\assembly\GAC_32\Policy.1.2.Microsoft.Interop.Security.AzRoles\6.0.6000.16386__31bf3856ad364e35\Microsoft.Interop.Security.AzRoles.config
Status: Locked to the Windows API!

Path: C:\Windows\Microsoft.NET\Framework\v3.0\WPF\PRESEN~1.CON
Status: Locked to the Windows API!

Path: c:\windows\system32\driverstore\filerepository\winmobil.inf_a7c8ce31\wmdsynce.man
Status: Allocation size mismatch (API: 4096, Raw: 688)

Path: C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTDiagLog.etl
Status: Locked to the Windows API!

Path: C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTEventLog-Application.etl
Status: Locked to the Windows API!

Path: C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTEventlog-Security.etl
Status: Locked to the Windows API!

Path: C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTEventLog-System.etl
Status: Locked to the Windows API!

Path: C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTMsMpPsSession.etl
Status: Locked to the Windows API!

Path: C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTMuroc System Trace.etl
Status: Locked to the Windows API!

Path: c:\users\shuo\appdata\roaming\tencent\logs\qq.tlg
Status: Size mismatch (API: 4181280, Raw: 4178772)

Path: c:\windows\system32\driverstore\filerepository\prnhp001.inf_2ade4966\i386\hpfdj920.gpd
Status: Allocation size mismatch (API: 4096, Raw: 648)

Path: c:\programdata\microsoft\search\data\applications\windows\gatherlogs\systemindex\systemindex.21.gthr
Status: Allocation size mismatch (API: 16384, Raw: 4096)

Path: C:\Users\shuo\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\fla6581.tmp
Status: Visible to the Windows API, but not on disk.

Path: c:\users\shuo\appdata\local\microsoft\windows live contacts\{7b7b16c5-7b05-4635-a6fc-a8e330c338dc}\dbstore\tempedb.edb
Status: Allocation size mismatch (API: 262144, Raw: 131072)

Path: c:\users\shuo\appdata\local\microsoft\windows live contacts\{c49b4f29-d80c-45d7-8c66-e7cfe1a2b6d4}\dbstore\tempedb.edb
Status: Allocation size mismatch (API: 262144, Raw: 131072)

Path: c:\users\shuo\appdata\roaming\microsoft\windows\cookies\low\shuo@bleepingcomputer[1].txt
Status: Size mismatch (API: 569, Raw: 568)

Path: C:\Users\shuo\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5\3AIYCFPA\15747141[1].flv
Status: Visible to the Windows API, but not on disk.

Path: C:\Users\shuo\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5\3AIYCFPA\addPlayerDurationReport[2].htm
Status: Visible to the Windows API, but not on disk.

Path: C:\Users\shuo\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5\3AIYCFPA\addPlayerDurationReport[5].htm
Status: Visible to the Windows API, but not on disk.

Path: C:\Users\shuo\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5\3AIYCFPA\index[1].gif
Status: Visible to the Windows API, but not on disk.

Path: C:\Users\shuo\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5\MMYO62AP\index[1].gif
Status: Invisible to the Windows API!

Path: C:\Users\shuo\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5\MMYO62AP\aff_tick[1].gif
Status: Visible to the Windows API, but not on disk.

Path: C:\Users\shuo\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5\MMYO62AP\cdn[1].xml
Status: Visible to the Windows API, but not on disk.

Path: C:\Users\shuo\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5\MMYO62AP\index[2].htm
Status: Visible to the Windows API, but not on disk.

Path: C:\Users\shuo\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5\MMYO62AP\index[3].htm
Status: Visible to the Windows API, but not on disk.

Path: C:\Users\shuo\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5\NPLW1U88\addPlayerDurationReport[2].htm
Status: Visible to the Windows API, but not on disk.

Path: C:\Users\shuo\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5\NPLW1U88\ipb_register[1].js
Status: Visible to the Windows API, but not on disk.

Path: C:\Users\shuo\AppData\Local\Microsoft\Windows\Temporary Internet Files\Low\Content.IE5\NPLW1U88\valo[1].htm
Status: Visible to the Windows API, but not on disk.

Processes
-------------------
Path: System
PID: 4 Status: Locked to the Windows API!

Path: C:\Windows\System32\audiodg.exe
PID: 1280 Status: Locked to the Windows API!

Stealth Objects
-------------------
Object: Hidden Module [Name: tdlcmd.dll]
Process: svchost.exe (PID: 892) Address: 0x10000000 Size: 24576

Object: Hidden Module [Name: tdlwsp.dll]
Process: Explorer.EXE (PID: 2188) Address: 0x10000000 Size: 28672

Object: Hidden Module [Name: tdlwsp.dll]
Process: iexplore.exe (PID: 2736) Address: 0x10000000 Size: 28672

Object: Hidden Module [Name: msgsres.dll]
Process: msnmsgr.exe (PID: 4268) Address: 0x632c0000 Size: 11403264

Object: Hidden Module [Name: msgslang.14.0.8089.0726.dll]
Process: msnmsgr.exe (PID: 4268) Address: 0x675e0000 Size: 315392

Object: Hidden Module [Name: msgrvsta.thm]
Process: msnmsgr.exe (PID: 4268) Address: 0x6df90000 Size: 20480

==EOF==

BC AdBot (Login to Remove)

 


#2 garmanma

garmanma

    Computer Masochist


  • Members
  • 27,809 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cleveland, Ohio
  • Local time:02:28 PM

Posted 11 October 2009 - 04:03 PM

Now that you were successful in creating a log you need to post it in our HJT forum There they will help you with the removal through some custom scripts and programs that we cannot run here in this forum

First, try to run a DDS / HJT log as outlined in our preparation guide:
http://www.bleepingcomputer.com/forums/t/34773/preparation-guide-for-use-before-using-malware-removal-tools-and-requesting-help/

If it won't run, don't worry, just give a brief description and tell them that these logs were all you could get to run successfully

Post them here:
http://www.bleepingcomputer.com/forums/f/22/virus-trojan-spyware-and-malware-removal-logs/


The HJT team is extremely busy, so be patient and good luck

Please start your own topic. Do not hijack someone else's topic
Mark
Posted Image
why won't my laptop work?

Having grandkids is God's way of giving you a 2nd chance because you were too busy working your butt off the 1st time around
Do not send me PMs with problems that should be posted in the forums. Keep it in the forums, so everyone benefits
Become a BleepingComputer fan: Facebook and Twitter




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users