Inkscape-0.46.win32.exe was installed last night.

This morning AdAware discovered IAMFAMOUS.DLL and RESYCLED trojan running on my computer.

I ran ClamWin Antivirus which found Trojan.Downloader-65039 associated or within Inkscape-0.46.win32.exe.

I've read that some virus scanners have had trouble with Inkscape, however it seems like more than a coincidence that a trojan horse was found the morning after installing Inkscape-0.46.win32.exe.

Any advice would be appreciated.

Provided you downloaded Inkscape from sourceforge (linked from the official Inkscape website) then you shouldn't have got the virus from it. If you had, I would expect a lot of other reports by now (that file on Sourceforge would not have been touched since it was originally released).

I think that you have AdAware finding one set of viruses and ClamWin finding another throws doubt onto the reports. I would at least expect an overlap. I would do a google search on those names and it'll probably help you identify how you caught them.

also.. win32.exe is not an inkscape file as far as I know.. in fact I believe its a windows file.

the .win32.exe is part of the filename of the inkscape installer.
Can you confirm you got it from sourceforge? as that files been there since march last year, and has had over 3 million downloads. if you got it somewhere else please let us know asap.

/edit
just downloaded the sourceforge installer, and clamwin, and it is flagging the file with the Trojan.Downloader-65039 I still believe its a false positive, but I'm looking into it.

i have it from sourceforge and got same virus alert from clamwin some mins ago.
have read about a new wurm called "conficker". could this be the reason? (sorry, me is a total noob)
http://tech.yahoo.com/blogs/null/116396
http://news.bbc.co.uk/2/hi/technology/7832652.stm
http://vil.nai.com/vil/content/v_153464.htm
[...]

I've now checked it with both AVG and F-Secure with their latest virus definitions and both come back clean for that file.
I'm going to report it to Clamwin as well as a false positive and let them check it too.

I got the same report from clamwin this morning after its scheduled overnight run. It updated definitions beforehand. The clamwin installation is one minor revision behind current (0.94.1 instead of 0.94.2) and it's giving me an apparently-related message that my functionality level is one behind current (37 instead of 38). I have a suspicion that a new virus definition is interacting badly with the previous version of the code.

I've been in touch with the ClamAV people, and the next update of the definitions should get rid of the false positive.

Simarilius wrote:I've now checked it with both AVG and F-Secure with their latest virus definitions and both come back clean for that file.
I'm going to report it to Clamwin as well as a false positive and let them check it too.