This content has been marked as final. Show 2 replies
-- Update May 22, 2009 --
McAfee Avert Labs received reports of an incorrect identification for this threat in the 5622 DATs. The issue is corrected in the 5623 DAT release, which is currently available for all products.
same problem here, but hope that the update to 5623 will fix it.