system
2
I am having exactly the same problem, but with binaries compiled with Visual Basic 6. But there seems to be no pattern to it at all - several programs are affected, yet two programs that are almost identical (including having the same dependencies) are treated differently. One is always detected as Win32:Evo-gen[susp], the other is not.
Like you, when the suspicious executable is scanned there is no threat found (although in my case this isn’t caught when compiling, but only when executing).
If I “add the file to the scan exclusion list” it still gets detected.
The only solution has been to add the executable’s folder to the Global Exclusions list, but this is far from satisfactory.
This only started happening in the past couple of days. I did notice that my Avast version was out of date, so I updated to the latest and it is still happening (so is as a result of a very recent virus update rather than being a problem with Avasy itself).
Unfortunately, for legal reasons, I can’t submit the actual binaries as false positives.
GE