Jump to content

autorun.inf; Worm.Agent.H


MAM

Recommended Posts

Malwarebytes' Anti-Malware 1.41

Datenbank Version: 2805

Windows 5.1.2600 Service Pack 3

15.09.2009 22:03:10

mbam-log-2009-09-15 (22-03-08).txt

Scan-Methode: Quick-Scan

Durchsuchte Objekte: 92220

Laufzeit: 3 minute(s), 25 second(s)

Infizierte Speicherprozesse: 0

Infizierte Speichermodule: 0

Infizierte Registrierungsschl

Link to post
Share on other sites

What is about my issue, is this a "big government mystery" ???

:

16.09.2009 21:25:52

mbam-log-2009-09-16 (21-25-48).txt

Scan-Methode: Quick-Scan

Durchsuchte Objekte: 92614

Laufzeit: 3 minute(s), 56 second(s)

Infizierte Speicherprozesse: 0

Infizierte Speichermodule: 0

Infizierte Registrierungsschl

Link to post
Share on other sites

Still the same by me ;)

Malwarebytes' Anti-Malware 1.41

Datenbank Version: 2872

Windows 5.1.2600 Service Pack 3

29.09.2009 19:14:33

mbam-log-2009-09-29 (19-14-32).txt

Scan-Methode: Quick-Scan

Durchsuchte Objekte: 93770

Laufzeit: 3 minute(s), 41 second(s)

Infizierte Speicherprozesse: 0

Infizierte Speichermodule: 0

Infizierte Registrierungsschl

Link to post
Share on other sites

Hi guys,

1) The bug has been reported to the developers but my guess is they have been busy with work on 1.4/1.41/1.42 and so on but i will post again in our dev's forum to try to attract attention to this.

2)Until Nosirrah decides to pull the signature form the database you will continue to receive the F/p warning.

The problem we have currently is that if we remove any Autorun worms from rootdrive without removing their autorun.inf then we lock folks from manually going into their C:\ via the drive icon.

So the with that there is no way we are dropping detection of Autorun worms and todate are not happy to remove them only to cripple manual navigation by leaving intact autorun.inf(lockout).

As we dont have the technology yet to differentiate between a custom autorun.inf and a malicious autorun.inf please take this into consideration when viewing this F/p.

Thanks for your understanding on this ;)

Link to post
Share on other sites

No... i have same problem since weeks ! ;)

The autorun.inf that is being flagged belongs to Vistamizer ( a vista styliser for xp). The autorun enables the vista.ico to run at start up. It's innocuous so just click ignore :o

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • 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.