Avast Home detects non existant Win32:Trojan-gen in HeidiSQL

The antivirus software Avast Home Edition does a false positive detection of the above mentioned virus in any HeidiSQL installer. If you downloaded HeidiSQL from a Sourceforge mirror, you can be sure that the file is not infected.

I contacted the Avast support and they promptly replied that they'll check that.

As a workaround, you can add these files to the Standard Shield provider (on-access scanning) exclusion list.
Left click the 'a' blue icon, click on the provider icon at left and then Customize. Go to Advanced tab and click on Add button...
You can use wildcards like * and ?. But be carefull, you should 'exclude' that many files that let your system in danger.
After that, please, periodically check it - scan it into Chest, right clicking the file - there should still be a copy in the chest even though you restored it to the original location. When it is no longer detected as being infected then you can also remove it from the Exclusion list.

I've been using HeidiSQL and avast for a 3 weeks or so without problems until today it started screaming that trojan horse was found in heidisql.exe nightly build

I'll check the build server for viruses. Could you do the same on your harddisks please? Could be that heidisql.exe was infected after it was downloaded.

I do not have much time at the moment, i will scan my PC at the evening.
If it helps: I tried to delete tables from remote server and it crashed, after restart Avast started to "scream" about trojan.

Hmm, no, does not help :)

The installer from
http://heidisql.googlecode.com/files/HeidiSQL_4.0_Setup.exe available now is identical to the one I got on April. I looks like a false positive in Avast's heuristics. Has any one handled them a sample? (I'm not an Avast user.)

Avast Antivirus Has Gone Mad

Lol :)

well... i guess that explains everything ;)