Anyone else getting Win10 Defender Alerts for the client?


#1

First time I’ve seen this, still running 2.2.11 on server.

I’m thinking this is a false positive reporting Win32/Cloxer.D!cl
Sent to virustotal as well:
https://www.virustotal.com/#/file/125c2cba249a17df7f14d3266a0b179da3d3917947ccb24bcf0d73c61b8ac6bc/detection

Also doing web based analysis:
https://www.hybrid-analysis.com/sample/125c2cba249a17df7f14d3266a0b179da3d3917947ccb24bcf0d73c61b8ac6bc


#2

Submit it to https://www.microsoft.com/en-us/wdsi/filesubmission and they’ll hopefully fix it


#3

Did that.

Actually created a new client with slightly different name and that didn’t trigger Defender. Must have been unlucky some combination of the name and other created some false-positive hash-match.