Program installed with Inno Setup seen as Trojan (Wacatac.B!ml)

2
votes

My software is a .NET application. The original .exe compiled with Visual Studio works fine and Microsoft Defender has nothing to say about it or any of the dependencies.

I made an installer with INNO Setup, that has been working fine until now, on a bunch of different machines.

The installer deploys my two .exe (the main app and an admin tool) and my own libraries, a few other libraries (Helix Toolkit, Triangles.net), and some libraries from .NET 5.0 (so that the framework is not needed for an offline install).

Since this morning, I have the following :

  • one of the installed .exe is seen as a Trojan by Microsoft Defender, and is put in quarantine ;
  • when I put the original .exe back in the Program Files directory manually, no Trojan is detected (even when i manually test the directory).

EDIT To be clear :

  • no malware is detected in the installer
  • no malware is detected in the original file
  • only the file installed by INNO SETUP is concerned

Is it possible that Inno Setup put that Trojan in my exe ? If so, what could I do to prevent or circumvent it ?

EDIT The more I investigate this, the less I understand what Inno Setup does. My original exe file weighs only 280 Ko, and the exe file installed by Inno Setup weighs 132 Mo. And, again, the Trojan is ONLY detected in the exe installed by inno setup.

Screen cap

sorry for the french OS

enter image description here

The trojan description is :

https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-description?name=Trojan%3aScript%2fWacatac.B!ml&threatid=2147735503

EDIT : the inno setup installer is now seen as containing the trojan and put in quarantine. enter image description here

2
inno-setupwindows-defendertrojan
If the anti-malware engine thinks your executable looks suspicious, then sure, it would block it. You would need to inform the vendor of a false-positive or manually unblock in that case. (Digitially signing your executables and installers using a code-signing certificate from a validated CA is another very good solution, although this is not free.) – Bill_Stewart
I pay for a 3 year code signing certificate and whitelist each installer with the avast ftp server. – Andrew Truckle
salut ;) Which version of Inno Setup Compiler ? I have the same problème with 5.x. – Jerry

2 Answers

1
votes

This is a false positive alarm.

Report your software as safe to several AV companies and wait till the update their databases.

Also it helps if the software is signed with certificate, has many users/downloads and everyone reports it as safe.

0
votes

My .net 6 app was flagged with the same Trojan. Defender had no issues when my code was just in the bin\release folder, but after publishing it to a folder and letting Visual Studio create a single executable, Defender started showing this false positive. For me the solution was simply to strong name my main exe assembly. This seemed to change the final resulting exe signature enough as to not get flagged anymore.