-
-
Notifications
You must be signed in to change notification settings - Fork 51
Detected as trojan by Windows Defender #53
Comments
v1.1.5 seems to be causing fits. It was caught by Bitdefender Advanced Threat Defense (admittedly prone to false positives) as Gen:Variant.Ursu.637702, Trojan.GenericKD.41851507, and a few other things that I ignored. When I tried to reinstall, the download was flagged by Bitdefender Web Security, but v1.1.4 checked out. |
I noticed the same thing, but was hoping that it was only me. I already have investigated this a little bit. VirusTotal scores don't look good either. I switched the compiler to MSVC++ 2019, and I think that's what causing the issues. I don't know what compiler I was using to distribute the older versions because having it not be on 2019 was a mistake. I think LDC2 found some compiler and linker from MinGW-64 for versions prior to 1.1.5, and Defender did not flag that. I will also look into changes and see if I introduced some algorithm that the antiviruses don't like. I thought that it may be detecting some new code in Aside from fixing whatever caused the program to be detected, does anybody know how to file a false-positive with Microsoft? It's also strange that the same binary is approved by MS in the store version. If you want to use the one that's already signed and vetted by MS, get a free license. |
I don't know what to do about this other than ask you all to report false-positives. |
dec 2019, a shit ton of trojans detected in virustotal |
Perhaps we need to roll back to 1.1.4 or release 1.1.5 again without |
@xmha97 If you want to pay for it, I will sign the installer. If you want a signed APPX, go get it from the Microsoft Store. Otherwise, change the action to "Allow on device" |
Link to older issue, this is a duplicate: #37 |
In the wiki you say
I'm afraid Microsoft Defender detected it as a trojan just today. This is the alert:
The text was updated successfully, but these errors were encountered: