Hi, I am using Inkscape 0.46dev+devel, built Dec 24 2007,
and my antivirusprogram (Norman) give me this popup.

"Norman Virus Control detected a trojan and
removed it to the quarantine.
>ink\inkscape\gspawn~2.exe
Trojan: w32/Tibs.BKHQ"

Is this documented?

Greenfield

I recommend you report this to the developers - viewtopic.php?f=5&t=484

can you confirm where you got this from please? We need to be able to investigate.

This happend yesterday, when I updated my antivirusprogram
Norman 5.91.10, it detected this trojan?

Possibly the same as the problem discussed in this thread: http://forums.extremeoverclocking.com/showthread.php?p=2537842 - this appears to be the same file (a GTK file?), though not in Inkscape.

Perhaps you should report it to the antivirus company, as it may well be a false positive. But in case it isn't, I would uninstall the version of Inkscape you're using and try the latest pre-release version (and file a bug report if you have the same problem with that version).

My F-Secure antivirus reports a Trojan in the Inkscape 0.91 installer (inkscape-0.91.msi) and the portable app too. According to the AV its a "Trojan:W32/Zhulu.ae74a970f3!Online" located in the Inkscape.com file (InkscapePortable\App\Inkscape\inkscape.com). Whether this is a false positive or the real thing I can't say.

The file was downloaded from: https://inkscape.org/en/gallery/item/3950/download/

A virus scan of the version 0.48.5 (more precisely InkscapePortable_0.48.5-1.paf.exe from http://sourceforge.net/projects/inkscap ... e/download) does not raise this issue.

I get clean scans from ESET, MBAM, and Sypbot S&D. I'm not familiar with F-Secure, never heard of.....but a little research shows that it uses Bitdefender for av, which I have heard of.

I don't know what to suggest. Until we get confirmation from a different av program, I don't think we should "raise the red flag". Maybe you could contact F-Secure and ask them to investigate?

Ok, that was for the file at the link you gave. For the portable, ESET reports some damaged archives which can't be extracted. So maybe there's an issue there? I'm not really sure what that means, but ESET did declare the file safe.