Well, its still on my system and infecting the same drive. Downloaded, among other things, the Avast cleaner tool, and around 10 am yesterday Avast reported that it was infected, along with any of the .exe's I had replaced.
In researching the "Release" date, near as I can decipher, I misunderstood the "Affects computers without Windows updates released in 2003" to mean they released the patches in response to the Tenga. I am mistaken... not the first time, so don't get excited.
My win2k Advanced server machine on my network (office surplus machines and cobbled together junk is all I own) is the only one not protected with Avast, and it runs my E-mule client, so I suspect it is the source of the infection. But fact is, I am just guessing here. Avast's Home (free) edition won't scan it across my network.
I have downloaded AVG and am running it on the win2k machine now. Any other suggestions to find the source of this infection? I have not opened E-mule since discovering the infection, but need to run it to replace my xp home disc so I can reinstall on my ICS machine. I'm on Dialup, so the Jotti upload of every file is out of the question, and the Avast Cleaner found nothing.
Also, as a second question I have been meaning to ask all along... the P2P shield lists many fileshare clients, but does not specificly mention E-mule. Is it covered in the P2P sheild, and will running Avast on the ICS host protect me with the E-mule client being run on a network machine?