When I heard this news, it reminded me of a bit of a horror story in one of my former CISO positions where our antivirus vendor also sent out a buggy DAT file that wrought havoc on our computers and system operations.
The story goes like this: Because of concerns with the rapid distribution of worms, malware, botnets, etc., our organization had decided to allow automated antivirus updates of all enterprise systems whenever a DAT file was uploaded to our antivirus system server.
caused Windows XP Service Pack 3 (SP3) systems to crash and reboot repeatedly.
Apparently Mc Afee blamed the update problem on a bad DAT file that inadvertently quarantined a critical Windows process called
Mc Afee Labs researchers use these files in their own work to ensure that they have the absolute latest detection and removal capabilities for Mc Afee anti-virus software.
DAT, files contain up-to-date Virus signatures and other information that Mc Afee anti-virus products use to protect your computer against virus attacks.
Mc Afee Labs now provides Beta pre-release, beta, or test versions of these .
I've removed and reinstalled Mc Afee Agent and Virus Scan Enterprise on a few of these systems with some success, but there are a few systems that it doesn't help on.
My current DAT file is 6039 when it should be 6042 by now.