Windows Defender finds trojan from build made by 2018.1.0b2

[fatbeat]

Hi!

I made windows build with Unity 2018.1.0b2 and Windows Defender flags the Exe as "Trojan:Win32/Azden.A!“cl”. This been happening for 4-5 different users on different computers.

When I made the first build everything went just fine. I shared the demo for my friends and they can’t play it cause Defender says there is a trojan.

[LeonhardP]

Please have a look at the reply in this thread:

Unity Beta 2017.2.0b7 & b8 virus ?

It is common to have False Positives with new unseen binaries, but to be sure, I would recommend in this case to file a False Positive report to BitDefender here: “https://www.bitdefender.com/submit” . And attach to the report a copy of the file “UnitySetup-WebGL-Support-for-Editor-2017.2.0b10.exe” from your computer. This way BitDefender will have a closer look and inform you with the verdict, most likely it will be indeed a False Positive. And we will do the same with a trusted copy of this …

[qqquantum]

We are having the same problem in my organization. This is regardless of the project build. Windows Defender also detected that the Playback Engine of mono had the player infected (WindowsPlayer.exe). I am not so sure it’s a false positive, since WindowsPlayer.exe is the base of the executable Unity apps for Windows and is known to the system.