Jump to content

Resident shield issue? Or just different OS behaviour?


Recommended Posts

Hi All,

I have a Windows XP Virtual Machine with MalwareBytes Pro on it that I use for security research.

When the Resident Shield is enabled on the VM, as soon as a file is displayed (not clicked, or accessed) in Explorer then the resident shield popup is displayed as shown in this example:

MalwareBytesXP.png

However, when exactly the same Malware sample is presented to a machine running MalwareBtyes Pro on Windows 7, then the resident shield popup is not shown. You can even select the file in Explorer without any effect:

MalwareBytes7.png

If you right click the file, and select Properties then the resident shield does detect it. But until you actually do that (or attempt to start the program) as far as MalwareBytes does not detect it.

Is this simply a difference in OS behaviour (Windows XP vs Windows 7) or is there something odd going on with the resident shield on Windows 7?

Many Thanks,

Ron

Link to post
Share on other sites

Greetings,

The behavior is indeed different because of the operating system. On Windows XP, when the view for a folder is set to tiled view, it accesses the file's version info and other data. Doing this causes it to be checked by Malwarebytes' Anti-Malware's protection module, so the item may be detected without actually attempting to execute the file. On Vista and 7, explorer does not do this so the item actually has to try to execute to be detected.

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.