mtagliaferri

Hello, We apologise for the inconvenience. This is now resolved. Cheers

Hi, Sorry for the inconvenience. The software had already been whitelisted by my colleagues. From what I can see in the logs this looks more like an internet error, probably during the scan the internet failed and this created a small bug with the whitelisting. Again, sorry for the inconvenience, but now if you restore the file everything should be fine. If not, please reach out to me here and I will try to assist you. Cheers

Hi, thank you for reaching out to us. This is now fixed! Cheers,

Hi Reese, Thank you for your clarification and sorry for the late reply. If I understand correctly, the problem occurs in the final distribution, after one of your clients has used your software to build something for his customers. So after this evaluation, and the tests I have run, I am pretty confident that the problem does not depend on your software or your driver. With the detection logs I can see what is actually being detected, so I thank you for trying to get them. I will wait your reply and the logs, in the meantime I will try some more tests. Cheers,

Hi Reese, I have done several tests but your software seems to install without any problems on my computer. No detection at all. I am unsure that the software you shared with us is responsible for the detection. To help you further I need the detection logs, with those I can solve the issue. Please, ask your customer if they can share them. Cheers, Marco

Hello, Yes, this was an FP. Thanks for reporting it to us, we have now fixed it.

Hello, Thank you for your report. This is now fixed. Cheers.

The resolution is immadiate in these circumstances, it is already currently not detected on my PC. Cheers :D

Hello, Thank you for reaching out to us. Yes, it was an FP, it has now been fixed! Thanks for your notification! Cheers

Hello, Thank you for reaching out to us. This is now fixed! Cheers

Hello, thank you for reaching out to us. Yes, there are FPs, I have handled them. Thank you for your report! Cheers.

Hi Ryan, Thank you for reaching out to us. The .appinstaller you linked does not seem to be detected by us. The detection logs you have shared are related to another file. The actual detected file has a strange signature, which looks similar to a cloudflare signature but is not. Furthermore, this signature is invalid. If this is your software, may I ask why this strange invalid signature? Thank you! Cheers

Hello Gabrielle, The detection is correct but Riskware is a generic detection that is not strictly malicious. Malwarebytes uses the detection name "Riskware" to indicate a category of programs that put the users at risk in some way. Programs might be defined as “riskware” because they: Violate the terms of service (ToS) of other software or a user platform. Block another application or software from being updated and patched. Could be used as a backdoor for other malware. Are indicative of the presence of other malware. This means that if you are aware of this .zip there is nothing to worry about, but because of what I wrote just before I will leave the detection of this "hacktool". If you wish to create an exclusion for this software and use it, you can go under 'Settings' -> 'Allow List' -> 'Add' and select the file. After doing this, you will no longer receive detection. If you still need help, please do not hesitate reach out us. Cheers

Hello, Thank you for the help! This is now fixed. Cheers

Hello, Thanks for reporting to us this FP. Now it's fixed! Cheers.

Hello, on the github you indicated I could not find the file that corresponds to this hash. In case you still need it could you kindly share the file? Thank you!

The important thing is that you do not have detection anymore. I will close the case but if you have any other problems please do not hesitate to contact us. Cheers.

I mean that the file you are sharing with us and the file detected by the antivirus are two different files. I can see that from the logs you shared with us earlier. So since the files are different, I cannot help you any more than that. To be sure, please go to this path (C:\ProgramData\Malwarebytes\MBAMService\Quarantine) and tell me if the directory is empty or not. If not, please share the files with us. Thank you.

Hi, thanks for reaching us. From the data you provided I can tell that it is actually strange, because, the file you provided is a legitimate AMD software but the detection file is on another one. Without the file that was actually detected, I don't have enough data to help you at the moment. Try rescanning the entire computer to make sure everything is OK.

No, everything should be fine. Malwarebytes has blocked the threat, that's why you got the pop-up. Open Malwarebytes and run another scan, meanwhile check that all buttons are enabled under RealTime Protection.

Hello, thank you for reaching out to us. Based on what I can see, this seems to be a good detection and not a false positive. The good thing is that we have blocked it. Are you aware of this file? Did you run anything before the detection was shown? Thank you

Hi, thanks for the example! I whitelisted the software, thanks for reporting it.

Hello, we apologise for the inconvenience. I've whitelisted your software. Thank you for your report.

Hi, Please provide the sample for which you require a review. Thanks

Hi, we are sorry for the inconvenience. I've whitelisted your software. Thank you for reporting it to us.