Jump to content
Sign in to follow this  
Foolrex

Trojan.Agent in MS Visual Studio? FP?

Recommended Posts

I am not a sophisticated user of such stuff, just downloaded and updated Malware Bytes and in my first scan got the following:

Malwarebytes' Anti-Malware 1.41

Database version: 2910

Windows 6.0.6002 Service Pack 2

10/5/2009 12:10:00 PM

mbam-log-2009-10-05 (12-09-46).txt

Scan type: Quick Scan

Objects scanned: 177264

Time elapsed: 11 minute(s), 22 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: 2

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:

C:\install.exe (Trojan.Agent) -> No action taken.

C:\Uninstall.exe (Trojan.Agent) -> No action taken.

I looked at the location for each and, according to the file properties, the installer is Microsoft

Share this post


Link to post
Share on other sites

I believe these are both FPs generated by using root as a storage folder . MBAM is aggressive again MZ header files in root as this is such a common launching point for malware and should never be used as a storage folder . If you want to use root as a storage folder please use the ignore function .

To double check this relocate these files to a different folder and run another scan , I believe we wont hit them .

Share this post


Link to post
Share on other sites
I believe these are both FPs generated by using root as a storage folder . MBAM is aggressive again MZ header files in root as this is such a common launching point for malware and should never be used as a storage folder . If you want to use root as a storage folder please use the ignore function .

To double check this relocate these files to a different folder and run another scan , I believe we wont hit them .

That did it! Thank you so much for helping me clear that up.

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.