False positive: MachineLearning/Anomalous.100%

[tpreese]

This is a C# program that I write.  Development happens on a machine with limited network access and no software but a very specific development profile.  MalwareBytes flagged the file right after it was compiled by the compiler. 

When I recompile with the code-signing certificate, the false positive goes away, but this happens at the last step obviously -- not during testing or debugging.

This software has close to 50,000 active academic users.  It's been in development for over 19 years as part of a larger project, marcedit (http://marcedit.reeset.net), a suite of library metadata tools.  I sign all my code in current versions, but not past versions [I'm a researcher -- I started the practice because Windows 10 is getting more picky].  I'd appreciate this being corrected.

 

--tr

false_positive.txt

me_tabbed.zip

[thisisu]

Hi,

This is detected by our MachineLearning engine, which helps to protect even better against 0day threats. Unfortunately, as this is a heuristic engine, it's possible False Positives happen. Thanks for reporting these, as this helps to finetune the engine, so these won't be detected in the future anymore.

This should be fixed by now. Please give it some time (max 10 minutes) in order to have it populate, so detection won't happen anymore.
If there is still a problem, perform the steps below:

1. Totally exit/shutdown Malwarebytes.
2. Go to here in explorer:
3. C:\ProgramData\Malwarebytes\MBAMService
4. Delete the following file only: hubblecache
5. Then you can restart MBAM and the cache file will rebuild on the next scan.