Home > Uncategorized > ESET Nod32 False Alarm Morning

ESET Nod32 False Alarm Morning

The antivirus scanners need to put in an “o sorry, we really didn’t mean that” clause when they find outbreaks of variants that they haven’t quite identified.   The virus scanner rarely trips on the servers, but this morning we had ESET’s NOD32 tripping on a variant of Win32/Kryptik.JX Trojan, that it supposedly found in msdtc.exe.   Luckily for us it was unable to clean the file, as apparently there was a large portion of the world today working to recover all of files it did delete.  The particular file we had mis-categorized was msdtc.exe.

Listening to the tubes, there was more of an official response to the problem from an ESET rep posted here…

http://www.wilderssecurity.com/showpost.php?p=1419988&postcount=6

Then there was the official response and apparently the entire incident happened within a 10 minute span before they released an update.  

http://kb.eset.com/esetkb/index?page=content&id=SOLN2181&actp=LIST_RECENT

Basically make sure you have the advanced heuristics module updated up to 1092 then RESTORE any deleted files from the Quarantine menu.   I figured I would add to the search string by posting something up, as I rarely get to witness the mistakes come in and out of view so early in the morning.  

Categories: Uncategorized Tags: