Discussion in 'NOD32 version 2 Forum' started by Caine, Sep 28, 2006.
Is this covered by NOD32?
Yes, it is now Caine!
Definition is highlighted: W97M/TrojanDropper.Lafool.F
hmm...it seems they've added it actually today.
I think this are the right definitions: PP97M/TrojanDropper.PPDrop.F, PP97M/TrojanDropper.PPDrop.NAA (2), PP97M/TrojanDropper.PPDrop.NAB
Nice one! Thanks for that pykko.
Is this sort of behaviour common with Microsoft? Pretty sneaky carry-on altogether.
Well, generally there are many exploits on MS products because many use them and hackers try to exploit evry little bug from them.
True that, but still though it's not so much the volume of exploits that MS inevitably have to battle with. It's the way they fixed up their own Security software defs and said nothing to the others. That's the bit that bugs me. Aw well, worrying over nothing since it's not an issue now.
Well, yes, basically if a new dangerous threat appear AV companies should be willing to exchange defs.
Separate names with a comma.