Jump to content

ClamAV detecting part of MBAM


Recommended Posts

Got a reply from Fortinet. They have removed the detection. And running the file throug VT confirms this :)http://www.virustotal.com/analisis/a551202...b6899e29f49b527

Welcome to the world of cutthroat Antivirus. :)

Basically, when one major player decides to detect something, the others tend to follow suit until/unless it's brought to their attention that the suspect file isn't bad at all. The only recourse for the user is to wait for their av to fix the issue, or switch to another av. Neither of which is what I would call, excellent as your at the avers mercy at that point.

Link to post
  • 2 weeks later...
ClamAV update process started at Thu Oct 16 12:40:03 2008

main.cld is up to date (version: 48, sigs: 399264, f-level: 35, builder: sven)

daily.cld is up to date (version: 8433, sigs: 48055, f-level: 35, builder: guitar)

2 weeks has passed. False positive detection involving mbam-dor.exe remains.

They obviously place high priority on fixing false positives :blink: Lucky for us MBAM users Clam-derivates enjoy such widespread usage in the Windows world

Link to post
  • 1 month later...

(I just had to resurrect this thread :) )

Ah! The ultimate in irony :)

I did a memory scan with ClamWin, witness the shocking result:

D:\Program Files\ClamWinPortable\ClamWinPortable.exe: Trojan.Agent-65355 FOUND

:) Seems it happens even to the best of us.

Link to post
Guest
This topic is now closed to further replies.
  • 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.