It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
The executable keeps getting flagged as Malware by Windows Defender on my system. Anyone else have this?
I assume I can safely tell it to ignore it but just want to make sure. (see screenshot)

Running Win 10 2004. Last definition update was on 17/12.
Attachments:
malware.jpg (30 Kb)
No posts in this topic were marked as the solution yet. If you can help, add your reply
The game passed the virus check with only three minor engines flagging it as a false-positive threat. You can see the results over here: https://www.virustotal.com/gui/file/c6e13ead79025ed52fc4f2bd746390e4a44ba853238db38c0bde894fa9ee1680/detection
Post edited December 17, 2020 by snow_panda
Thank you for the response.

Just wanted to let you know that I've reinstalled Windows two days ago and even on a fresh install I still get the same malware detection by Windows Defender.

I've installed the game again (while pausing Defender) and have uploaded the EXE to the same website. I do get a different result though:
https://www.virustotal.com/gui/file/7b0c8565a5d83d11e6128f3f0ebebd66646bb3570b654dba0239ee769d23d8a9/detection

The cryptinject shows up there for Microsoft
Post edited December 21, 2020 by Yannos.548
I got Trojan:Win32/CryptInject!ml warning by Windows Defender
avatar
Gurthfin: I got Trojan:Win32/CryptInject!ml warning by Windows Defender
Yeah that's the one I am getting too.
avatar
Gurthfin: I got Trojan:Win32/CryptInject!ml warning by Windows Defender
avatar
Yannos.548: Yeah that's the one I am getting too.
I'm getting this too.

I submitted it to Microsoft for review.
Post edited December 21, 2020 by guynamedbilly
So I submitted it to MS and they said the file is not malware and they cannot reproduce a detection on the file. This morning, I let the game update again and then ran a scan on the folder. This time it did not detect anything. Seems like it was simply a false positive as suspected. I scanned it on another computer also and it wasn't detected there either.

I can only suspect it was a problem with the definition update for the day.