pbust

Staff
  • Content count

    3,311
  • Joined

  • Last visited

6 Followers

About pbust

  • Rank
    Staff

Profile Information

  • Location
    Earth

Recent Profile Visitors

107,983 profile views
  1. We're two weeks away from the next scheduled release for MB3, but we'll be discussing an emergency AeSdk-only Component Update tomorrow. Please stand by and thanks for your patience.
  2. This is a false positive by Spyshelter. See if you can exclude MBAE from Spyshelter.
  3. Thanks! It is not unheard of for signature-based products to trigger on certain characteristics of an exploit mitigation product. But that's just it, another draw-back of failed attempts of using signature approaches to trying to detect exploits, like the vast majority of the traditional AV vendors do.
  4. We're in touch with Grammarly and hope to have a more permanent solution for our common customers soon. Please stay tuned.
  5. Hi, try this: https://forums.malwarebytes.com/forum/225-malwarebytes-incident-response-beta/
  6. Can you please post the MBAE logs? Instructions in my signature.
  7. Our Research Team has been monitoring this application for some time and has decided to add detection based on triggers against our PUP detection criteria. https://blog.malwarebytes.com/malwarebytes-news/2016/10/malwarebytes-gets-tougher-on-pups/ The detection is correct and not a false positive. We will continue monitoring this application and if we notice a change in the behavior we will review it again.
  8. Unfortunately this is the nature of our generic/signatureless remediation technology (i.e. linking engine) which finds malware artifacts related to the original detected malware/PUP. There are some PUPs that are very large in size and this is an unfortunate side effect. On the positive side, it allows us to be really good at malware remediation. We do have an internal project ongoing to takes a different approach that might solve this for PUPs, but that project is still in incubation.
  9. Our Research Team has been monitoring this application for some time and has decided to add detection based on triggers against our PUP detection criteria. https://blog.malwarebytes.com/malwarebytes-news/2016/10/malwarebytes-gets-tougher-on-pups/ The detection is correct and not a false positive. We will continue monitoring this application and if we notice a change in the behavior we will review it again. If for whatever reason you want to continue using Advanced SystemCare, you can simply uncheck the detections and click Next after a scan with MBAM, and the prompt will ask you if you want to "Ignore Once" or "Ignore Always". If you Ignore Always it won't be detected any more.
  10. We are happy to announce the public beta of our upcoming cloud-based platform for Incident Response for companies. Malwarebytes Incident Response incorporates the following key high-level features: Cloud-based management console Dashboard views Endpoint & asset management Policy and group management Scheduled scans Malware discovery and remediation This is a great opportunity for you to get an early glimpse of our new Malwarebytes Incident Response built on our new Cloud Platform. We are looking for beta testers who can deploy Malwarebytes Incident Response in a business environment to at least 5 endpoint Windows machines. If you want to become a Beta tester we will set you up with an account and instructions on how to get started. To sign up simply send an email to DL-NebulaBeta@malwarebytes.com.
  11. EMET has some EMET-specific mitigations and limited in nature as compared to MBAE. For example, EMET has ASR which basically disables a bunch of content in certain applications. They do this since they cannot protect from exploits through those applications, while MBAE's Layer3 can (think Java exploits, application design abuses, etc.). OTOH EMET has some anti-detouring since it uses Detours. But MBAE does not need those since it uses a different approach. Last but not least, MBAE uses a multi layer approach to mitigations and the mitigations we have in place are the ones that make the most amount of sense to us to deal with exploits ITW. MBAE is also supported and maintained actively, while EMET is not.
  12. Thanks for confirming hfike. I pushed a global exclusion a few mins ago so you don't need your local exclusion anymore. We're reaching out to Grammarly folks to see if they can give us a heads up next time before they release a new version so we can exclude it beforehand.
  13. Thanks, should be fixed already!
  14. Can you please post the C:\ProgramData\Malwarebytes\MBAMService\logs\mbae-default.log and mbae-default.log.bak?