I've used NOD32 for years and been very happy with it; but of late I've been seeing a rash of new baddies on Qwest's (admittedly terrible) news server in a number of newsgroups. They are pretty obvious, and I suppose anyone who opens a file called topless.scr gotten from a newsgroup deserves to get bit, but I'm bothered that it is taking ESET so long to add them to their definitions. KAV's online scanner has already identified them as: topless._scr - infected by Backdoor.Loony.g PamAndersonNude._scr - infected by Backdoor.Hackarmy.n but NOD32 still declares them clean even after today's update (v.1.762 (20040516) ). I submitted the latter file to ESET two days ago. I suppose they'll catch it in the next set of definitions, or the one after that, but it makes me wonder where the heuristics (which I won't pretent to understand) come in. All in all, a bit disappointing. john s.