False positive Win32:Evo-gen [Susp] from my exes built with Visual Studio 2012

Viruses and worms
1

Avast Professional 7.0.1474, virus definitions 130109-01.

The popup says:
Infection: Win32:Evo-gen [Susp]
The threat was detected and blocked just before the file was executed.

Today I sent 7 executable files to the virus lab by using the Avast tool.
The executable files were built by me by using Visual Studio 2012 (update 1) from the C/C++ sources.
I already sent a couple of files 3 Dec 2012 but the problem has persisted.
I believe that this is a false positive because the on demand scan does not find anything (only the realtime scan, when trying to execute or copy the file). Also McAfee virus scan does not detect anything (Enterprise 8.8.0 (8.8.0.849), DAT version: 6948.0000, 1/7/2013).
Small modifications to the program cause that the problem goes away (however, I have not invented any deterministic method that would help).

The infection is reported for some files with the Debug/Win32 configuration. I have not seen any reports from release configurations or for x64 platform builds.

Any chance that this could be fixed quickly?
The files belong to software product of a large company that sells the software all over the world, and this is now blocking the release of our product. (Well, these are debug versions that are not actually used in the production, but the installation kit has an option to install also debug versions, and in any case, there can be an virus infection message if the setup kit is being copied).

2

Hello,
send us (virus@avast.com) the file to analyze, please. Put “False positive” to email body or use http://www.avast.com/contact-form.php

Milos

3

Hello,
false positive will be fixed in next VPS update.

Milos

4

Thanks!
However, I hope that the solution is not to have checksums of these 7 files put into the white list.
If it is, you will be having much more e-mail from me in future when we build new release candidates.

5

No worries! With the updated virus definitions, there were no false alarms even for the new build.

6

No, it was fix of generic detection, not adding files to whitelist.

Milos