msherwood

Want to let everyone know that we resolved the corrupt database issue on Jun 6, 2023 at 9:58:12a UTC. No action is required on your part. Our teams are currently investigating the incident and we’ll be in touch with more info shortly. Thanks for your patience as we sort through this.

We're seeing some issues with our notification system and mostly for trial users and marketing messages. We targeted this build to rule out a variety of changes we made related to these issues. We also pushed this build for new users / installs to help accelerate our learnings. It will remain up on our site for at least the next few days as we continue to troubleshoot. You can safely use the versions higher than 4.5.24. :)

Hey everyone. We're currently testing a few things with our 4.5.24 and 4.5.27 builds and the experience you're seeing here is expected. As of late Thursday (Apr 27) and still today, what's being served up by malwarebytes.com and our support tool is version 4.5.24 and this will not upgrade past this version (for now). Prior to that, it was version 4.5.27. Both versions get regular definition updates and you'll remain protected.

Please see our Root Cause Analysis (RCA) for yesterday’s false positive. RCA - Web Protection False Positive - Sept 22, 2022.pdf

This morning, you may have experienced an issue with the real-time web filtering component of our product blocking certain domains, including http://google.com. In addition, the Nebula console itself may have experienced slowdowns, as it was dealing with a high volume of alert traffic from the web filter. Once alerted to the problem, our product team resolved the issue and released an update to our web protection database (version 1.0.60360). This update is applied during the normal update process, and the issue should automatically resolve. In some cases, updating to the latest database may require temporarily disabling the web filtering feature. Why did this happen? This morning, during a routine update, an error was introduced into the Malwarebytes web filtering database which caused various domains to be inadvertently blocked. We are performing an exhaustive analysis of our process to ensure an issue of this type does not affect our customers again, and we will be putting in place new procedures as a result. We apologize for the inconvenience this may have caused you and your organization and remain committed to the highest standards of product quality and technical excellence.

Thank ya, @David H. Lipman!

Thanks for the quick call. Figured out it was routed incorrectly due to the company's splitting. So we never got a notice that you need something. Watch for an email in the next few minutes.

Sorry to hear this, @BotenRedWolf. Sending you a direct email now.

Hi @changingtide. Checking on this and will be back in touch shortly. Edit: someone from Support will be reaching out to you shortly.

Please do! Thanks for your support!

@SunGirl - please ignore the post with the "1-855" Malwarebytes support number. It was a spam post and is not legit. @nasdaq will be able to help you.

@Agus - please ignore the post with the "1-855" Malwarebytes support number. It was a spam post and is not legit. @nasdaq will be able to help you.

Hi @cc123! You're most likely fine. Make sure you're using unique and complex passwords on all of your accounts. Also, use two-factor authentication (2FA) wherever possible and a password manager. Take a look over here at this post:

Hi and welcome to the forums, @xolobi96! Thanks for your feedback. The flow limitation is on the IPS platform side; we can share your feedback with them. On the reCAPTCHA, that's a step we must require as it helps keep the spam down as we get a grip of it.

Thanks for sharing this! @PhilStophas been given a proper "Atta Boy" by our team here!

Great to hear! Thanks for checking and staying on top of this one.

It was our understanding that this one (and some of the other longer standing ones) may be fixed in the 4.3.x update. We haven't moved to that and are working on a deployment plan. We're targeting to be on 4.3.x within this month.

Done!

Hi @LouisAZ. Unfortunately, the company you worked with is not us and they are running a scam. Our official support team doesn't offer chat on the weekends (you can see options here). Wanted to share this ASAP so you know what's up. As far as your machine and what's going on, hang tight and one of our community members here will jump in and help you. Please make sure you complete the steps above as those will help us serve you better.

Yep. We'll get it removed!

Dev team is reviewing this. I removed your link.

Two things: Can you send your browser console logs? PM to me please. After capturing logs, can you try using just our extension?

We're not able to reproduce this in any way. What version of the extension are you using?

Perfect, thanks for the details.

Thanks. Our extension team will review this a bit more and get back to you.