Malwarebyes Signature Definitions Quality Control CONCERN!!!

[vane]

Hi,

As of yesterday Webroot had a serious of issues with their definitions they issued out to their customers that caused Windows System Files being quarantined and many many many legitimate soft wares as well. You can read the comments from these links below.

My question is - does Malwarebytes has some type of quality control in place to make sure this type of catastrophic will never happens to us concerned customers.

https://community.webroot.com/t5/Announcements/W32-Trojan-Gen-False-Positive-Fix-April-24/td-p/290198

https://www.bleepingcomputer.com/news/security/webroot-antivirus-goes-off-the-rails-and-flags-windows-system-files-as-malicious/

 

 

[Francois_Blais]

You'll probably hear from officials here soon, but Malwarebytes suffered from a similar problem a while ago, and they are supposed to have installed everything needed to prevent this from happening again.

But as I said, I'm not an official, just a follower.

 

[dcollins]

We do follow pretty strict quality guidelines to reduce the chances of  this happening as much as possible. The issue that @Francois_Blais mentions was actually a problem with a Microsoft update where they shipped faulty files, and we did detect those as malicious and removed them. You can read up on the details of that in the following FAQ article: https://support.malwarebytes.com/customer/en/portal/articles/2647220-what-can-i-do-if-i-have-been-affected-by-the-kernel32-dll-false-positive-?b_id=6442

[Francois_Blais]

I stand corrected, Devin, thanks!

[Porthos]

@dcollins There was an issue back in 2013 where a bad MB database was on the update server for just 6-8 minutes that bricked many computers. It was about 5 in the evening my time on April 15  (tax day) that year. I remember it well because over the next few days I had about a hundred computers stacked up in my shop. I always deal with MB issues for free (because I force it on them) but all but 3 of my clients gave me $30-$50 to help them out. I have great and understanding clients. It was also my best month $$$.

https://blog.malwarebytes.com/malwarebytes-news/2013/04/yesterdays-database-update-issue/

Edited April 28, 2017 by Porthos

[exile360]

9 hours ago, Porthos said:

@dcollins There was an issue back in 2013 where a bad MB database was on the update server for just 6-8 minutes that bricked many computers. It was about 5 in the evening my time on April 15  (tax day) that year. I remember it well because over the next few days I had about a hundred computers stacked up in my shop. I always deal with MB issues for free (because I force it on them) but all but 3 of my clients gave me $30-$50 to help them out. I have great and understanding clients. It was also my best month $$$.

https://blog.malwarebytes.com/malwarebytes-news/2013/04/yesterdays-database-update-issue/

Yes, and it was after that very event that we implemented several redundant systems for checking each and every database update before it ships in order to prevent such major FPs, including testing across multiple operating systems and tons of known good/safe files (especially, though not exclusively, critical system files and OS components).

[dcollins]

On 4/27/2017 at 6:29 PM, Porthos said:

@dcollins There was an issue back in 2013 where a bad MB database was on the update server for just 6-8 minutes that bricked many computers. It was about 5 in the evening my time on April 15  (tax day) that year. I remember it well because over the next few days I had about a hundred computers stacked up in my shop. I always deal with MB issues for free (because I force it on them) but all but 3 of my clients gave me $30-$50 to help them out. I have great and understanding clients. It was also my best month $$$.

https://blog.malwarebytes.com/malwarebytes-news/2013/04/yesterdays-database-update-issue/

Thanks! I sometimes forget that the company was around before I joined and things may have happened before then

As @exile360 mentioned, it looks like this was one of the pushes that helped us get better at making sure this doesn't happen again!

Edited April 30, 2017 by dcollins