miekiemoes

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.

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.

Hi, The new database is available now, so this won't be detected anymore: MBAM2 Version: v2018.06.09.03 MBAM3 Version: 1.0.5414

Thanks, this looks like a false positive indeed and will get fixed in next database update that will go out in 15 minutes. Thanks for reporting!!

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.

Hi, I assume this was an Anti-ransomware False Positive? This should have been fixed in a meanwhile.

Given attachements are currently broken in this forum (they are working on this), I'll send you a private message via this forum with my mailaddress, so you can send it to there. Was the file quarantined? If so, please unquarantine the key and file and send me the file. I don't really need the key.

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.. We do however need the files that are detected, so these can be added to our additional learning, so these won't be detected in the future anymore. Thanks!

Hi, Please read and follow the steps here in case you want to dispute this: Thanks!

Hi, Please see here: Thanks!

Ok, so no detection is occurring anymore, so that means it has learned from it already.

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. I however can't reproduce detection anymore. Is the detection still happening on your end?

Hi, Please see here for the actions to take for reconsideration:

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 as I can't reproduce detection anymore. In case it's still detected, Quit malwarebytes from the systemtray. Then navigate to the following folder: C:\ProgramData\Malwarebytes\MBAMService In there, locate the file HubbleCache and delete it. Restart Malwarebytes again. A new Hubblecache will then be created again, so it will properly pick it up and remember to not detect this anymore.

I guess it was a machinelearning/suspicious detection? This new engine helps to protect even better against 0day threats. Unfortunately, as this is a heuristic engine, it's possible False Positives happen. Because of the Machinelearning, it learns from this and finetunes, so a next time, it's not detected anymore if a False Positive indeed. So that might explain your situation, it was detected before, but it learned from it so it knows now not to detect this anymore as it wasn't a malicious file.