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

Zlob.Downloader.bs


  • Please log in to reply
21 replies to this topic

#1 healer

healer

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:12:12 AM

Posted 22 April 2009 - 07:36 PM

One of my computers has Zlob.Downloader.bs found by SpyBot. Spybot couldn't remove it but hung on it. Every time I had to force-terminate the SpyBot program. None of AVG, SuperAntiSpyware, Dr Web CureIt discovered this file. I unhid all the files including system files in the computer and searched for it but found nothing. The computer runs very slow. I am not too sure if this is the major cause.

BC AdBot (Login to Remove)

 


#2 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,489 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:10:12 AM

Posted 22 April 2009 - 08:41 PM

Hello and welcome. i am moving this ti the Am I Infected forum for tests.

Please run part 1 of S!Ri's SmitfraudFix
Please download SmitfraudFix

Double-click SmitfraudFix.exe
Select option #1 - Search by typing 1 and press "Enter"; a text file will appear, which lists infected files (if present).
Please copy/paste the content of that report into your next reply.

Note : process.exe is detected by some antivirus programs (AntiVir, Dr.Web, Kaspersky) as a "RiskTool"; it is not a virus, but a program used to stop system processes. Antivirus programs cannot distinguish between "good" and "malicious" use of such programs, therefore they may alert the user.
http://www.beyondlogic.org/consulting/proc...processutil.htm
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 healer

healer
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:12:12 AM

Posted 23 April 2009 - 08:52 AM

Here is the content of the report. I thank you in anticipation of your help.

SmitFraudFix v2.412

Scan done at 23:09:44.53, Thu 23/04/2009
Run from C:\Documents and Settings\SysAdmin\desktop\SmitfraudFix
OS: Microsoft Windows XP [Version 5.1.2600] - Windows_NT
The filesystem type is NTFS
Fix run in normal mode

Process

C:\WINDOWS\System32\smss.exe
C:\WINDOWS\system32\winlogon.exe
C:\WINDOWS\system32\services.exe
C:\WINDOWS\system32\lsass.exe
C:\WINDOWS\system32\svchost.exe
C:\WINDOWS\system32\svchost.exe
C:\WINDOWS\system32\svchost.exe
C:\WINDOWS\system32\spoolsv.exe
C:\PROGRA~1\AVG\AVG8\avgwdsvc.exe
C:\Program Files\Java\jre6\bin\jqs.exe
C:\PROGRA~1\AVG\AVG8\avgemc.exe
C:\PROGRA~1\AVG\AVG8\avgrsx.exe
C:\PROGRA~1\AVG\AVG8\avgnsx.exe
C:\WINDOWS\Explorer.EXE
C:\Program Files\AVG\AVG8\avgcsrvx.exe
C:\Program Files\Synaptics\SynTP\SynTPEnh.exe
C:\PROGRA~1\AVG\AVG8\avgtray.exe
C:\acer\Empowering Technology\ePower\epm-dm.exe
C:\WINDOWS\system32\ctfmon.exe
C:\WINDOWS\system32\cmd.exe

hosts


C:\


C:\WINDOWS


C:\WINDOWS\system


C:\WINDOWS\Web


C:\WINDOWS\system32


C:\WINDOWS\system32\LogFiles


C:\Documents and Settings\SysAdmin


C:\DOCUME~1\SysAdmin\LOCALS~1\Temp


C:\Documents and Settings\SysAdmin\Application Data


Start Menu


C:\DOCUME~1\SysAdmin\FAVORI~1


Desktop


C:\Program Files


Corrupted keys


Desktop Components

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Desktop\Components\0]
"Source"="About:Home"
"SubscribedURL"="About:Home"
"FriendlyName"="My Current Home Page"


o4Patch
!!!Attention, following keys are not inevitably infected!!!

o4Patch
Credits: Malware Analysis & Diagnostic
Code: S!Ri



IEDFix
!!!Attention, following keys are not inevitably infected!!!

IEDFix
Credits: Malware Analysis & Diagnostic
Code: S!Ri



Agent.OMZ.Fix
!!!Attention, following keys are not inevitably infected!!!

Agent.OMZ.Fix
Credits: Malware Analysis & Diagnostic
Code: S!Ri


VACFix
!!!Attention, following keys are not inevitably infected!!!

VACFix
Credits: Malware Analysis & Diagnostic
Code: S!Ri


404Fix
!!!Attention, following keys are not inevitably infected!!!

404Fix
Credits: Malware Analysis & Diagnostic
Code: S!Ri


Sharedtaskscheduler
!!!Attention, following keys are not inevitably infected!!!

SrchSTS.exe by S!Ri
Search SharedTaskScheduler's .dll


AppInit_DLLs
!!!Attention, following keys are not inevitably infected!!!

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows]
"AppInit_DLLs"=""
"LoadAppInit_DLLs"=dword:00000001


Winlogon
!!!Attention, following keys are not inevitably infected!!!

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"Userinit"="C:\\WINDOWS\\system32\\userinit.exe,"

RK

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"System"=""




DNS

Description: Atheros AR5005G Wireless Network Adapter - Packet Scheduler Miniport
DNS Server Search Order: 61.9.195.193
DNS Server Search Order: 61.9.194.49

HKLM\SYSTEM\CCS\Services\Tcpip\..\{7AB33EFD-ABDC-4AFE-A8F7-0E9E6BEE42B8}: DhcpNameServer=61.9.195.193 61.9.194.49
HKLM\SYSTEM\CS1\Services\Tcpip\..\{7AB33EFD-ABDC-4AFE-A8F7-0E9E6BEE42B8}: DhcpNameServer=61.9.195.193 61.9.194.49
HKLM\SYSTEM\CS3\Services\Tcpip\..\{7AB33EFD-ABDC-4AFE-A8F7-0E9E6BEE42B8}: DhcpNameServer=61.9.195.193 61.9.194.49
HKLM\SYSTEM\CCS\Services\Tcpip\Parameters: DhcpNameServer=61.9.195.193 61.9.194.49
HKLM\SYSTEM\CS1\Services\Tcpip\Parameters: DhcpNameServer=61.9.195.193 61.9.194.49
HKLM\SYSTEM\CS3\Services\Tcpip\Parameters: DhcpNameServer=61.9.195.193 61.9.194.49


Scanning for wininet.dll infection


End

#4 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,489 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:10:12 AM

Posted 23 April 2009 - 03:55 PM

Okay ,let's do part 2,Cleaning..
You should print out these instructions, or copy them to a Notepad file for reading while in Safe Mode, because you will not be able to connect to the Internet to read from this site.

Please reboot your computer in Safe Mode by doing the following :
  • Restart your computer
  • After hearing your computer beep once during startup, but before the Windows icon appears, tap the F8 key continually;
  • Instead of Windows loading as normal, a menu with options should appear;
  • Select the first option, to run Windows in Safe Mode, then press "Enter".
  • Choose your usual account.
Once in Safe Mode, double-click SmitfraudFix.exe
Select option #2 - Clean by typing 2 and press "Enter" to delete infected files.

You will be prompted : "Registry cleaning - Do you want to clean the registry ?"; answer "Yes" by typing Y and press "Enter" in order to remove the Desktop background and clean registry keys associated with the infection.

The tool will now check if wininet.dll is infected. You may be prompted to replace the infected file (if found); answer "Yes" by typing Y and press "Enter".

The tool may need to restart your computer to finish the cleaning process; if it doesn't, please restart anyway into normal Windows. A text file will appear onscreen, with results from the cleaning process; please copy/paste the content of that report into your next reply.
The report can also be found at the root of the system drive, usually at C:\rapport.txt


Next Rerun MBAM like this

Open MBAM in normal mode and click Update tab, select Check for Updates,when done
click Scanner tab,select Quick scan and scan.
After scan click Remove Selected, Post new scan log and Reboot into normal mode.
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 healer

healer
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:12:12 AM

Posted 24 April 2009 - 06:33 PM

Hi boopme,

From the first report of SmitFraudFix in my previous post, could we tell whether the computer had been infected?

I have done the first part of your instruction given in your last post. Below is the report. I didn't do the second part because I wasn't sure what MBAM referred to. I thought when you said "rerun" it should be the same program and somehow an acronym of SmitFraudFix, then I couldn't find the "update" tab. By the way is "update" updating the some sort of definition from the Internet? Please tell me also whether the following report indicates anything about the infection state of the computer.

Regards

SmitFraudFix v2.412

Scan done at 8:41:23.73, Sat 25/04/2009
Run from C:\Documents and Settings\SysAdmin\Desktop\SmitfraudFix
OS: Microsoft Windows XP [Version 5.1.2600] - Windows_NT
The filesystem type is NTFS
Fix run in safe mode

SharedTaskScheduler Before SmitFraudFix
!!!Attention, following keys are not inevitably infected!!!

SrchSTS.exe by S!Ri
Search SharedTaskScheduler's .dll

Killing process


hosts


127.0.0.1 localhost
127.0.0.1 www.007guard.com
127.0.0.1 007guard.com
127.0.0.1 008i.com
127.0.0.1 www.008k.com
127.0.0.1 008k.com
127.0.0.1 www.00hq.com
127.0.0.1 00hq.com
127.0.0.1 010402.com
127.0.0.1 www.032439.com
...

VACFix

VACFix
Credits: Malware Analysis & Diagnostic
Code: S!Ri


Winsock2 Fix

S!Ri's WS2Fix: LSP not Found.


Generic Renos Fix

GenericRenosFix by S!Ri


Deleting infected files


IEDFix

IEDFix
Credits: Malware Analysis & Diagnostic
Code: S!Ri



Agent.OMZ.Fix

Agent.OMZ.Fix
Credits: Malware Analysis & Diagnostic
Code: S!Ri


404Fix

404Fix
Credits: Malware Analysis & Diagnostic
Code: S!Ri


RK


DNS

HKLM\SYSTEM\CCS\Services\Tcpip\..\{7AB33EFD-ABDC-4AFE-A8F7-0E9E6BEE42B8}: DhcpNameServer=61.9.195.193 61.9.194.49
HKLM\SYSTEM\CS1\Services\Tcpip\..\{7AB33EFD-ABDC-4AFE-A8F7-0E9E6BEE42B8}: DhcpNameServer=61.9.195.193 61.9.194.49
HKLM\SYSTEM\CS3\Services\Tcpip\..\{7AB33EFD-ABDC-4AFE-A8F7-0E9E6BEE42B8}: DhcpNameServer=61.9.195.193 61.9.194.49
HKLM\SYSTEM\CCS\Services\Tcpip\Parameters: DhcpNameServer=61.9.195.193 61.9.194.49
HKLM\SYSTEM\CS1\Services\Tcpip\Parameters: DhcpNameServer=61.9.195.193 61.9.194.49
HKLM\SYSTEM\CS3\Services\Tcpip\Parameters: DhcpNameServer=61.9.195.193 61.9.194.49


Deleting Temp Files


Winlogon.System
!!!Attention, following keys are not inevitably infected!!!

"System"=""


RK.2



Registry Cleaning

Registry Cleaning done.

SharedTaskScheduler After SmitFraudFix
!!!Attention, following keys are not inevitably infected!!!

SrchSTS.exe by S!Ri
Search SharedTaskScheduler's .dll


End

#6 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,489 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:10:12 AM

Posted 24 April 2009 - 07:23 PM

Hello healer, my bad I erred thinking I already had you run MBAM once. So we will run it next. We have removed some but i want to see if there is a DNS changer infection. It should show up with the scan if there. I was referencing updating the MBAM (Malwarebytes Anti-Malware) program.


Next run MBAM:
Please download Malwarebytes Anti-Malware (v1.36) and save it to your desktop.
alternate download link 1
alternate download link 2
If you have a previous version of MBAM, remove it via Add/Remove Programs and download a fresh copy.
  • Make sure you are connected to the Internet.
  • Double-click on mbam-setup.exe to install the application.
  • 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 updates, manually download them from here and just double-click on mbam-rules.exe to install. Alternatively, you can update through MBAM's interface from a clean computer, copy the definitions (rules.ref) located in C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malwarebytes' Anti-Malware from that system to a usb stick or CD and then copy it to the infected machine.
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 and exit MBAM.
Note: If MBAM encounters a file that is difficult to remove, you may be asked to reboot your computer so it can proceed with the disinfection process. Regardless if prompted to restart the computer or not, please do so immediately. Failure to reboot normally (not into safe mode) will prevent MBAM from removing all the malware. MBAM 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 after scanning with MBAM. Please temporarily disable such programs or permit them to allow the changes.
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 healer

healer
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:12:12 AM

Posted 24 April 2009 - 10:04 PM

Thanks boopme,

I have done what you said. Here below is the report. It has found 145 objects infected. I wonder what Rogue.RegTool is. Why none of other programs detected them. By the way the Zlob.Downloader.bs is still nowhere to be found.

Malwarebytes' Anti-Malware 1.36
Database version: 2039
Windows 5.1.2600 Service Pack 3

25/04/2009 12:51:10 PM
mbam-log-2009-04-25 (12-51-10).txt

Scan type: Quick Scan
Objects scanned: 92439
Time elapsed: 20 minute(s), 23 second(s)

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

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
HKEY_LOCAL_MACHINE\SOFTWARE\RegTool (Rogue.RegTool) -> Quarantined and deleted successfully.
HKEY_CURRENT_USER\SOFTWARE\RegTool (Rogue.RegTool) -> Quarantined and deleted successfully.

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
C:\Documents and Settings\SysAdmin\Application Data\RegTool (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\Logs (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490 (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-06-150 (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\Results (Rogue.RegTool) -> Quarantined and deleted successfully.

Files Infected:
C:\Documents and Settings\SysAdmin\Application Data\RegTool\Logs\2009-04-19 14-52-570.log (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\filelist.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-0.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-1.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-10.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-100.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-101.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-102.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-103.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-104.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-105.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-106.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-107.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-108.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-109.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-11.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-110.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-111.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-112.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-113.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-114.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-115.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-116.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-117.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-118.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-119.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-12.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-120.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-121.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-122.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-123.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-124.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-125.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-126.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-127.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-128.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-13.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-14.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-15.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-16.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-17.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-18.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-19.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-2.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-20.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-21.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-22.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-23.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-24.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-25.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-26.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-27.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-28.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-29.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-3.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-30.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-31.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-32.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-33.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-34.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-35.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-36.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-37.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-38.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-39.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-4.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-40.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-41.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-42.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-43.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-44.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-45.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-46.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-47.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-48.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-49.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-5.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-50.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-51.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-52.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-53.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-54.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-55.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-56.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-57.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-58.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-59.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-6.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-60.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-61.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-62.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-63.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-64.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-65.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-66.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-67.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-68.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-69.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-7.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-70.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-71.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-72.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-73.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-74.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-75.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-76.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-77.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-78.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-79.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-8.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-80.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-81.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-82.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-83.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-84.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-85.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-86.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-87.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-88.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-89.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-9.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-90.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-91.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-92.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-93.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-94.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-95.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-96.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-97.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-98.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-00-490\regb-99.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\QuarantineW\2009-04-19 15-06-150\filelist.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\Results\Evidence.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\Results\Junk.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\Results\Registry.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\Documents and Settings\SysAdmin\Application Data\RegTool\Results\Update.db (Rogue.RegTool) -> Quarantined and deleted successfully.
C:\WINDOWS\Tasks\RegTool Scan.job (Rogue.RegTool) -> Quarantined and deleted successfully.

#8 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,489 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:10:12 AM

Posted 24 April 2009 - 10:56 PM

Hi, The Malwarebytes research team has determined that RegTool is a fake anti-malware application.

Rogue software uses intentional false positives to convince the user that their system has been compromised and then demands money to remove these false threats. In extreme cases the false threats are actually the very trojans that advertise or even directly install the rogue.*** MBAM forum


I was looking at alot ot things and decided to run
ATF and SAS:

From your regular user account..
Download Attribune's ATF Cleaner and then SUPERAntiSpyware , Free Home Version. Save both to desktop ..
DO NOT run yet.
Open SUPER from icon and install and Update it
Under Scanner Options make sure the following are checked (leave all others unchecked):
Close browsers before scanning.
Scan for tracking cookies.
Terminate memory threats before quarantining
.
Click the "Close" button to leave the control center screen and exit the program. DO NOT run yet.

Now reboot into Safe Mode: How to enter safe mode(XP)
Using the F8 Method
Restart your computer.
When the machine first starts again it will generally list some equipment that is installed in your machine, amount of memory, hard drives installed etc. At this point you should gently tap the F8 key repeatedly until you are presented with a Windows XP Advanced Options menu.
Select the option for Safe Mode using the arrow keys.
Then press enter on your keyboard to boot into Safe Mode
.

Double-click ATF-Cleaner.exe to run the program.
Under Main "Select Files to Delete" choose: Select All.
Click the Empty Selected button.

If you use Firefox or Opera browser click that browser at the top and choose: Select All
Click the Empty Selected button.
If you would like to keep your saved passwords, please click No at the prompt.
Click Exit on the Main menu to close the program
.

NOW Scan with SUPER
Open from the desktop icon or the program Files list
On the left, make sure you check C:\Fixed Drive.
Perform a Complete scan. After scan,Verify they are all checked.
Click OK on the summary screen to quarantine all found items.
If asked if you want to reboot, click "Yes" and reboot normally.

To retrieve the removal information after reboot, launch SUPERAntispyware again.
Click Preferences, then click the Statistics/Logs tab.
Under Scanner Logs, double-click SUPERAntiSpyware Scan Log.
If there are several logs, click the current dated log and press View log.
A text file will open in your default text editor.
Please copy and paste the Scan Log results in your next reply.
Click Close to exit the program.


Please ask any needed questions,post log and Let us know how the PC is running now.
How do I get help? Who is helping me?For the time will come when men will not put up with sound doctrine. Instead, to suit their own desires, they will gather around them a great number of teachers to say what their itching ears want to hear....Become a BleepingComputer fan: Facebook

#9 healer

healer
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:12:12 AM

Posted 25 April 2009 - 03:27 AM

To do the scan, do I need to log on as an administrator. I usually log on as a limited user. I have found a lot of anti-virus programs and anti-spyware programs do not work as well if I do not log on as an administrator.

#10 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,489 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:10:12 AM

Posted 25 April 2009 - 09:17 AM

This is true many time.It's OK to do so.
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

#11 healer

healer
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:12:12 AM

Posted 26 April 2009 - 08:25 PM

Hi boopme,

The computer is very slow, not very responsive though it might have been very slightly improved. Anyway I am not too sure as nothing is obvious at the moment. I did the SuperAntiSpyware test as an administrator on the safe mode but the computer turned off itself after the process running for a while. It just wouldn't finish the process. I ran the Spybot again on the safe mode to see if the Zlob.Downloader.bs had gone. The computer also switched off itself about one quarter of the way. I did 3 times and it happened 3 times. All were done on the safe mode.

Then I ran the SuperAntiSpyware test on the regular (non-safe) mode. The SuperAntiSpyware finished the process and found no problem. The report is pasted below. The Spybot ran alright on regular mode but still hung on Zlob.Downloader.bs nearly at the end of the process. The message on the bottom of the window is Running bot-check (499467/525010: Zlob.Downloader.bs)

I personally think some virus or spyware still likely causes the problem. If it is the hardware problem the computer would switch off in any mode not just in safe mode. In fact at one time some time ago the computer switched off repeatedly not long after boot-up on normal mode. Then I booted up the computer with a BartPE CD, then the computer stayed up.

SUPERAntiSpyware Scan Log
http://www.superantispyware.com

Generated 04/26/2009 at 07:31 PM

Application Version : 4.26.1000

Core Rules Database Version : 3863
Trace Rules Database Version: 1815

Scan type : Complete Scan
Total Scan Time : 02:07:02

Memory items scanned : 350
Memory threats detected : 0
Registry items scanned : 5168
Registry threats detected : 0
File items scanned : 56676
File threats detected : 0

#12 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,489 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:10:12 AM

Posted 26 April 2009 - 10:38 PM

Yes we do have malware. I want ti run 2 more scans.

Rerun MBAM like this:

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


Now run SDFix:
Please print out and follow these instructions: "How to use SDFix". <- This program is for Windows 2000/XP ONLY.
When using this tool, you must use the Administrator's account or an account with "Administrative rights"
  • Disconnect from the Internet and temporarily disable your anti-virus, script blocking and any real time protection programs before performing a scan.
  • When done, the SDFix report log will open in notepad and automatically be saved in the SDFix folder as Report.txt.
  • If SDFix is unable to run after rebooting from Safe Mode, run SDFix in either Mode, and type F, then press Enter for it to finish the final stage and produce the report.
  • Please copy and paste the contents of Report.txt in your next reply.
  • Be sure to renable you anti-virus and and other security programs before connecting to the Internet.
-- If the computer has been infected with the VirusAlert! malware warning from the clock and the Start Menu icons or drives are not visible, open the SDFix folder, right-click on either the XP_VirusAlert_Repair.inf or W2K VirusAlert_Repair.inf (depending on your version of Windows) and select Install from the Context menu. Then reboot to apply the changes.
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 healer

healer
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:12:12 AM

Posted 28 April 2009 - 07:39 AM

I ran MBAM first in normal mode then in safe mode. Both found no problem. Here are the logs.

Malwarebytes' Anti-Malware 1.36
Database version: 2053
Windows 5.1.2600 Service Pack 3

28/04/2009 8:12:55 PM
mbam-log-2009-04-28 (20-12-55).txt

Scan type: Quick Scan
Objects scanned: 80722
Time elapsed: 10 minute(s), 8 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)

Malwarebytes' Anti-Malware 1.36
Database version: 2053
Windows 5.1.2600 Service Pack 3

28/04/2009 8:30:03 PM
mbam-log-2009-04-28 (20-30-03).txt

Scan type: Quick Scan
Objects scanned: 80051
Time elapsed: 9 minute(s), 17 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)

I then ran SDFix in safe mode. Below is the report. I ran the SpyBot straight after this also in safe mode. It finished the whole process and found no problem. I witnessed the process went through Zlob.Downloader.bs and a few others with different extensions. Are they files? I wondered. I didn't find any file with such name when I tried to search for it.


SDFix: Version 1.240
Run by SysAdmin on Tue 28/04/2009 at 21:14

Microsoft Windows XP [Version 5.1.2600]
Running From: C:\SDFix

Checking Services :


Restoring Default Security Values
Restoring Default Hosts File

Rebooting


Checking Files :

No Trojan Files Found






Removing Temp Files

ADS Check :



Final Check :

catchme 0.3.1361.2 W2K/XP/Vista - rootkit/stealth malware detector by Gmer, http://www.gmer.net
Rootkit scan 2009-04-28 21:24:35
Windows 5.1.2600 Service Pack 3 NTFS

scanning hidden processes ...

scanning hidden services & system hive ...

scanning hidden registry entries ...

scanning hidden files ...

scan completed successfully
hidden processes: 0
hidden services: 0
hidden files: 0


Remaining Services :




Authorized Application Key Export:

[HKEY_LOCAL_MACHINE\system\currentcontrolset\services\sharedaccess\parameters\firewallpolicy\standardprofile\authorizedapplications\list]
"%windir%\\system32\\sessmgr.exe"="%windir%\\system32\\sessmgr.exe:*:enabled:@xpsp2res.dll,-22019"
"C:\\Program Files\\Acer\\Acer Arcade\\PCMService.exe"="C:\\Program Files\\Acer\\Acer Arcade\\PCMService.exe:*:Enabled:CyberLink PowerCinema Resident Program"
"C:\\StubInstaller.exe"="C:\\StubInstaller.exe:*:Enabled:LimeWire swarmed installer"
"C:\\Program Files\\LimeWire\\LimeWire.exe"="C:\\Program Files\\LimeWire\\LimeWire.exe:*:Enabled:LimeWire"
"%windir%\\Network Diagnostic\\xpnetdiag.exe"="%windir%\\Network Diagnostic\\xpnetdiag.exe:*:Enabled:@xpsp3res.dll,-20000"
"C:\\Program Files\\Bonjour\\mDNSResponder.exe"="C:\\Program Files\\Bonjour\\mDNSResponder.exe:*:Enabled:Bonjour"
"C:\\Program Files\\iTunes\\iTunes.exe"="C:\\Program Files\\iTunes\\iTunes.exe:*:Enabled:iTunes"
"C:\\Program Files\\AVG\\AVG8\\avgemc.exe"="C:\\Program Files\\AVG\\AVG8\\avgemc.exe:*:Enabled:avgemc.exe"
"C:\\Program Files\\AVG\\AVG8\\avgupd.exe"="C:\\Program Files\\AVG\\AVG8\\avgupd.exe:*:Enabled:avgupd.exe"
"C:\\Program Files\\AVG\\AVG8\\avgnsx.exe"="C:\\Program Files\\AVG\\AVG8\\avgnsx.exe:*:Enabled:avgnsx.exe"
"C:\\Program Files\\Mozilla Firefox\\firefox.exe"="C:\\Program Files\\Mozilla Firefox\\firefox.exe:*:Enabled:Firefox"
"C:\\Program Files\\MSN Messenger\\msnmsgr.exe"="C:\\Program Files\\MSN Messenger\\msnmsgr.exe:*:Enabled:Windows Live Messenger 8.1"
"C:\\Program Files\\MSN Messenger\\livecall.exe"="C:\\Program Files\\MSN Messenger\\livecall.exe:*:Enabled:Windows Live Messenger 8.1 (Phone)"

[HKEY_LOCAL_MACHINE\system\currentcontrolset\services\sharedaccess\parameters\firewallpolicy\domainprofile\authorizedapplications\list]
"%windir%\\system32\\sessmgr.exe"="%windir%\\system32\\sessmgr.exe:*:enabled:@xpsp2res.dll,-22019"
"%windir%\\Network Diagnostic\\xpnetdiag.exe"="%windir%\\Network Diagnostic\\xpnetdiag.exe:*:Enabled:@xpsp3res.dll,-20000"
"C:\\Program Files\\MSN Messenger\\msnmsgr.exe"="C:\\Program Files\\MSN Messenger\\msnmsgr.exe:*:Enabled:Windows Live Messenger 8.1"
"C:\\Program Files\\MSN Messenger\\livecall.exe"="C:\\Program Files\\MSN Messenger\\livecall.exe:*:Enabled:Windows Live Messenger 8.1 (Phone)"

Remaining Files :



Files with Hidden Attributes :

Mon 14 Apr 2008 60,416 A.SH. --- "C:\Program Files\Outlook Express\msimn.exe"
Mon 26 Jan 2009 1,740,632 A.SHR --- "C:\Program Files\Spybot - Search & Destroy\SDUpdate.exe"
Mon 26 Jan 2009 5,365,592 A.SHR --- "C:\Program Files\Spybot - Search & Destroy\SpybotSD.exe"
Thu 24 Nov 2005 1,024 ...HR --- "C:\WINDOWS\system32\NTIBUN4.dll"
Thu 24 Nov 2005 1,024 ...HR --- "C:\WINDOWS\system32\NTICDMK7.dll"
Thu 24 Nov 2005 1,024 ...HR --- "C:\WINDOWS\system32\NTIFCD3.dll"
Thu 24 Nov 2005 1,024 ...HR --- "C:\WINDOWS\system32\NTIMP3.dll"
Thu 24 Nov 2005 1,024 ...HR --- "C:\WINDOWS\system32\NTIMPEG2.dll"
Sun 3 Dec 2006 4,348 ..SH. --- "C:\Documents and Settings\All Users\DRM\DRMv1.bak"

Finished!

#14 boopme

boopme

    To Insanity and Beyond


  • Global Moderator
  • 73,489 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ USA
  • Local time:10:12 AM

Posted 28 April 2009 - 09:19 AM

Hi, we have this beat,but do a file search for these, In the system root.
DO NOT delete anything..Post back with their full path if found.

FIRST ...Show hidden files .

Close all programs so that you are at your desktop.
Double-click on the My Computer icon.
Select the Tools menu and click Folder Options.
After the new window appears select the View tab.
Put a checkmark in the checkbox labeled Display the contents of system folders.
Under the Hidden files and folders section select the radio button labeled Show hidden files and folders.
Remove the checkmark from the checkbox labeled Hide file extensions for known file types.
Remove the checkmark from the checkbox labeled Hide protected operating system files.
Press the Apply button and then the OK button and shutdown My Computer.
Now your computer is configured to show all hidden files.

Search for:

vbgtorfd.dll".
rs.txt".
rs.txt".
bdmanager.dll".



Next Please install RootRepeal

Go HERE, and download RootRepeal.zip to your Desktop.
Tutorial with images ,if needed >> L@@K.
Unzip that,(7-zip tool if needed) and then click RootRepeal.exe to open the scanner.
Next click on the Report tab, now click on Scan. A Window will open asking what to include in the scan. Check all of the below and then click OK.

Drivers
Files
Processes
SSDT
Stealth Objects
Hidden Services


Now you'll be asked which drive to scan. Check C: and click OK again and the scan will start. Please be patient as the scan runs. When the scan has finished, click on Save Report.
Name the log RootRepeal.txt and save it to your Documents folder (it should automatically save it there).
Please copy and paste that into your next reply.
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

#15 healer

healer
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:12:12 AM

Posted 28 April 2009 - 08:33 PM

Hi boopme,

The RootRepeal program crashed every time I tried to run it in normal mode. When I ran it in safe mode, a message came up saying something to the effect that the program was not supposed to run in safe mode and there might be undesirable effect. I have done the search. it couldn't find any of the three you specified.

ROOTREPEAL CRASH REPORT
-------------------------
Exception Code: 0xc0000094
Exception Address: 0x004eb6c9




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users