Jump to content

shadowwar

Staff
  • Content Count

    8,494
  • Joined

  • Last visited

About shadowwar

  • Rank
    Forum Deity

Recent Profile Visitors

64,775 profile views
  1. This should be fixed in about 10 mins. If still detected on your end after ~10 minutes from now. Perform the following steps: Totally exit/shutdown Malwarebytes. Go to here in explorer: C:\ProgramData\Malwarebytes\MBAMService Delete the following file only: hubblecache Then you can restart MBAM and the cache file will rebuild on the next scan.
  2. can you please zip and attach the files detected here? Thanks!
  3. This seems to be detected properly. Without the executable file i cant be 100% sure. If you want to use it then you can add it to your exclusions in mbam. PUP means potentially unwanted program. Thanks for reporting.
  4. we need the actual scan log and the actual file being detected. Screenshots wont help us unfortunately.
  5. After some time it automatically refreshes the cache file. It would of fixed itself after 24 hours.
  6. This will be fixed next update. about 2 hours from now. Thanks for reporting!
  7. The offending def was removed. Being its a microsoft trusted file it would of been prevented from detection on mbam 3 and 4 at all. 2 doesn't have the cloud built in thus mbam 3 and 4 are more robust in detection's and fp preventions because of the cloud components of it.
  8. This should be fixed now. What version of mbam are you running? The older versions simply don't have the robust fp protection and the newer engines to detect more recent malware.
  9. Do you have the scan log? I do not see this detected here and has been whitelisted for some time on mbam 3 and 4.
  10. I am not sure what you are asking here. This is for false positive reports with MBAM. Are you seeing any detections? If you disable web blocking does the error go away?
  11. This should no longer be detected. It was fixed yesterday. Please let me know if not the case.
  12. this file isnt currently detected. There was a fp over the weekend but it should of been fixed already. IF still detected on your end please provide us with a scan log. Thanks.
  13. This is fixed already. Please make sure you have the latest database. Thanks for reporting.
  14. Thanks for reporting. This should no longer be detected.
  15. Thanks for reporting. This should no longer be detected.
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.