Jump to content
Sign in to follow this  
snakedoctor

(Rogue.Installer)

Recommended Posts

No reports from kaspersky

XP

Malwarebytes' Anti-Malware 1.30

Database version: 1312

Windows 5.1.2600 Service Pack 2

24/10/2008 11:47:16

mbam-log-2008-10-24 (11-47-09).txt

Scan type: Quick Scan

Objects scanned: 55783

Time elapsed: 3 minute(s), 48 second(s)

Memory Processes Infected: 0

Memory Modules Infected: 0

Registry Keys Infected: 1

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:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\Stats\{00000000-0000-0000-0000-100005000004} (Rogue.Installer) -> No action taken. [4054423730518072867015427984856677777083130192171717171717171714171717171417171

71714171717171418171717172217171717172194]

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)

Share this post


Link to post
Share on other sites

I gave MBAM additional places to look for malware GUIDS , this is nothing more than a trace from a long dead infection in your case .

If it were a real infection {00000000-0000-0000-0000-100005000004} would be a CLSID as well and point to a dll , it does not look that way in your log so everything is fine here .

Share this post


Link to post
Share on other sites
I gave MBAM additional places to look for malware GUIDS , this is nothing more than a trace from a long dead infection in your case .

If it were a real infection {00000000-0000-0000-0000-100005000004} would be a CLSID as well and point to a dll , it does not look that way in your log so everything is fine here .

ok thanks nosirrah, would you suggest fixing it? as it shows up on each scan

Share this post


Link to post
Share on other sites

Its just a trace and safe to either fix or ignore , I would fix it though so that it does not come back in future scans .

Share this post


Link to post
Share on other sites
Its just a trace and safe to either fix or ignore , I would fix it though so that it does not come back in future scans .

will do & thanks for a great free app your work is appreciated.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.