Does malwarebytes pick up normal files?

[Slify]

I just used malwarebytes for the first time and it picked up 57 infected files. A lot of them look normal, for instance C:\Program Files\setup.exe. So I was wondering, are there any files that are commonly detected by malwarebytes that should not be deleted?

[kangaroo]

ummmm

That is not a normal file "C:\Program Files\setup.exe."

setup.exe should be with a another extension like another folder in program files such as "C:\Program Files\ScanSoft\setup.exe"

If that setup.exe is just under the folder "Program Files" then it is a virus even better yet dude upload that file to virustotal.com it will tell you what type of anti-virus detects it as a virus.

[Slify]

Are you sure? I thought setup.exe was just the standard name for an installation file. The one for malwarebytes was mbam-setup-1.46.exe.

[mountaintree16]

I think what kangaroo was trying to say is that that is NOT a normal place for a legitimate .exe file to be and this is why Malwarebytes would have picked it up

[Slify]

not only that this post http://forums.malwarebytes.org/index.php?s...ost&p=19864 says that {7e853d72-626a-48ec-a868-ba8d5e23e045} is not malicious, and mbam detected files that look like that on my computer too, so I'm wondering if it's not okay to delete them

[mountaintree16]

Well Slify, firstly, that is a detection from 2008 so if you haven't updated since the date of that old post then you should remove it (and if you indeed haven't updated since then you need to), otherwise if you do believe it to be a FP, please make a new post in the FP forum after following the directions here:

http://forums.malwarebytes.org/index.php?showtopic=3228

[mountaintree16]

Silfy,

The developers do need a full log from you actually (just saw your post in the FP forum), a developers log as outlined in the directions

A full log looks like this (however this log is clean so no detections present):

Malwarebytes' Anti-Malware 1.46

www.malwarebytes.org

Database version: 4104

Windows 5.1.2600 Service Pack 3

Internet Explorer 8.0.6001.18702

5/15/2010 1:26:28 PM

mbam-log-2010-05-15 (13-26-28).txt

Scan type: Quick scan

Objects scanned: 125471

Time elapsed: 10 minute(s), 53 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)

And please see here on how to run the developer's log:

http://forums.malwarebytes.org/index.php?s...ost&p=11731

However, wait until requested from one of the developers to provide the additional information; if they need it for sure they will let you know; you don't want to post back in your own thread until you get a reply from one of the developers; this can make it look as though you are already getting help and take longer for you to get a reply.

Thank you

[mountaintree16]

Slify,

I was just keeping an eye on your False Positives post; please DO post a FULL developers log as outline here in reply to Nosirrah in your thread:

http://forums.malwarebytes.org/index.php?s...ost&p=11731

Thank you

[Supernovasky]

Are you sure? I thought setup.exe was just the standard name for an installation file. The one for malwarebytes was mbam-setup-1.46.exe.

Its also important to note many viruses and trojans and other junk will create files with the same name as something you think is normal, this is often true when people are infected and look at their Processes tab under the Task Manager.

So just because you think its normal Malwarebytes is probably detecting a real threat especially as your example is located directly within the Program Files folder and not a subfolder that is rather unusual.