Xabot

[Geekgirl]

Hey, now its my turn

Yeah yeah I ran the usual tools, found error in Spybot scan that included Xabot.
Ran Housecall and found 11 files infected with Trojans. All different Trojans for each file. Deleted them all then rebooted.
Had BSOD after rebooting but is up and running.

I know Weatherbug and AIM are not good and this is my sons computer.
I think Kazza is the culprit (via P2P)

Not to metion I do have N.A.V. updated and installed.



Do you see anything in my logfile?

Logfile of HijackThis v1.98.0
Scan saved at 12:22:48 AM, on 7/21/2004
Platform: Windows 2000 SP4 (WinNT 5.00.2195)
MSIE: Internet Explorer v6.00 SP1 (6.00.2800.1106)

Running processes:
C:\WINNT\System32\smss.exe
C:\WINNT\system32\winlogon.exe
C:\WINNT\system32\services.exe
C:\WINNT\system32\lsass.exe
C:\WINNT\system32\svchost.exe
C:\WINNT\system32\spoolsv.exe
C:\WINNT\System32\svchost.exe
C:\PROGRA~1\Navnt\navapsvc.exe
C:\PROGRA~1\Navnt\npssvc.exe
C:\WINNT\system32\nvsvc32.exe
C:\WINNT\system32\regsvc.exe
C:\WINNT\system32\MSTask.exe
C:\WINNT\System32\tcpsvcs.exe
C:\WINNT\System32\snmp.exe
C:\WINNT\System32\WBEM\WinMgmt.exe
C:\WINNT\System32\mspmspsv.exe
C:\WINNT\system32\svchost.exe
C:\WINNT\Explorer.EXE
C:\PROGRA~1\Navnt\alertsvc.exe
C:\WINNT\System32\P2P Networking\P2P Networking.exe
C:\Program Files\AWS\WeatherBug\Weather.exe
C:\Program Files\Navnt\navapw32.exe
C:\Program Files\WinZip\WZQKPICK.EXE
C:\Documents and Settings\Administrator\My Documents\HJT\HijackThis.exe

R0 - HKCU\Software\Microsoft\Internet Explorer\Main,Start Page = http://www.yuyuhakusho.com/index.cfm?flash=true
O2 - BHO: (no name) - {53707962-6F74-2D53-2644-206D7942484F} - C:\Program Files\Spybot - Search & Destroy\SDHelper.dll
O3 - Toolbar: @msdxmLC.dll,-1@1033,&Radio - {8E718888-423F-11D2-876E-00A0C9082467} - C:\WINNT\System32\msdxm.ocx
O4 - HKLM\..\Run: [Synchronization Manager] mobsync.exe /logon
O4 - HKLM\..\Run: [DispDir] C:\Program Files\Creative\Display Director\DispDir.exe -s
O4 - HKLM\..\Run: [P2P Networking] C:\WINNT\System32\P2P Networking\P2P Networking.exe /AUTOSTART
O4 - HKLM\..\Run: [NvCplDaemon] RUNDLL32.EXE C:\WINNT\system32\NvCpl.dll,NvStartup
O4 - HKLM\..\Run: [nwiz] nwiz.exe /install
O4 - HKLM\..\Run: [QuickTime Task] "C:\Program Files\QuickTime\qttask.exe" -atboottime
O4 - HKLM\..\Run: [NPS Event Checker] C:\PROGRA~1\Navnt\npscheck.exe
O4 - HKLM\..\Run: [NAV DefAlert] C:\PROGRA~1\Navnt\defalert.exe
O4 - HKCU\..\Run: [Weather] C:\Program Files\AWS\WeatherBug\Weather.exe 1
O4 - Global Startup: Microsoft Office.lnk = C:\Program Files\Microsoft Office\Office\OSA9.EXE
O4 - Global Startup: Norton AntiVirus AutoProtect.lnk = C:\Program Files\Navnt\navapw32.exe
O4 - Global Startup: WinZip Quick Pick.lnk = C:\Program Files\WinZip\WZQKPICK.EXE
O9 - Extra button: AIM - {AC9E2541-2814-11d5-BC6D-00B0D0A1DE45} - C:\Program Files\AIM95\aim.exe
O9 - Extra button: WeatherBug - {AF6CABAB-61F9-4f12-A198-B7D41EF1CB52} - C:\Program Files\AWS\WeatherBug\Weather.exe (HKCU)
O16 - DPF: {74D05D43-3236-11D4-BDCD-00C04F9A3B61} (HouseCall Control) - http://a840.g.akamai.net/7/840/537/2004 ... scan53.cab
O16 - DPF: {77E32299-629F-43C6-AB77-6A1E6D7663F6} (Groove Control) - http://www.nick.com/common/groove/gx/GrooveAX.cab

[brad]

Did you reboot since cleaning and the BSOD? Nothing real strange is showing.
Try rebooting and compare a fresh Log to this one. If they have different entrees, post it.
If it were mine or in a New Member's Topic, WeatherBug, Kazza and p2p networking would be removed through Add/Remove and deleted from the Machine.



brad

[Geekgirl]

[Geekgirl]

Gotta tell ya, my son was not a happy camper when he booted up his machine today

Anyhow, I ran Housecall again, came out clean.

Unfortunately, he got another BSOD. He said the blue screen flashed then it rebooted on its own. I restarted it and disk check ran.

I tried using Error-Checking and also got an error. "The disk check could not be performed because exclusive access to the drive could not be obtained "......obviously the volume was in use so it will run at next boot. Which it already ran as stated above after restart.

Question.... whats the difference between the disk check at restart and the error checking at next boot? Nothing I can see other than a deeper scan and the option to fix bad sectors. Is this right?


Any suggestions are welcome

[brad]

[Geekgirl]

I apologize for not replying sooner, I wanted to let you know what I found and did.

I took some of my own advise and set the h.d.d. as slave and used error-checking as I often suggest in my posts and scanned for errors. Haven't had a BSOD since.
So I guess I will go with my own instincts next time.........they seem to always work