bunch of stuff blocked all of a sudden such as all of google

[jamestlarson]

4 minutes ago, davidf said:

V05 seems to be working (touch wood)

Can confirm v05 is working so far.

 

Edit: Retract the above, still blocking things furiously. Strike 2..... 3rd fix attempt is the charm?

Edited January 27, 2018 by jamestlarson

[Bazinga]

2 minutes ago, davidf said:

V05 seems to be working (touch wood)

Not for me.

[mbates14]

not for me. yet...

[tzetter]

V05 still throwing up pop-ups constantly....

[holmebrian]

yep can confirm 05 broken still

[bigalxenos]

Nah, 05 still screwed over here too. I think I'm just leaving realtime off until Monday at this rate.

 

Thanks for the A+ support, MB team!

[davidf]

Just now, Bazinga said:

Not for me.

I spoke too soon I'm afraid. I opened a second tab and it seemed okay (Firefox) but when I closed it down and restarted FF the same problem was back, so V05 isn't working

[mbates14]

Same here. Hasnt fixed a thing. 

[TigerRisk-SI]

 

Any help with this? Seems clients don't have any DNS?

[Trockid]

I'm having the same problems as everyone else. Anti-malware for business. Really need this fixed...

[mbates14]

Because your DNS is blocked too! What a complete and utter disaster. Especially if its google DNS, once you start blocking DNS servers, your stuck with a catch22. Cant update because of the blocks, but you need to update but you cant. 

In a personal or a small company environment its easy just to disable things and get around. But in large corporations where everything is tiered and graded, you just created an economical disaster for that company. Yikes.... 

Luckily its Saturday here in North America so the impact should be minimal. 

Have to disable all protections. 

Edited January 27, 2018 by mbates14

[holmebrian]

really its only the website blocking thats broken should be all you need to disable

[rbryant76]

seing blocks to Ncentreal serves as well. 

[jamestlarson]

v06 is out. Still blocking everything. Strike 3 and still no response from Malwarebytes support. Sweet! Top notch.

Edited January 27, 2018 by jamestlarson

[LBFmedia]

Blocking Facebook, CNN, etc. here as well. 

[Bazinga]

Just redistribute v02.

[mbates14]

If they are continually pushing definitions but cant really "find the problem". There is the slight chance that the system was HACKED. 

Because, I dont see someone creating that big of a mistake in a definition file to block just about everything, However, thats something a hacker could and would want to do... 

Look into that one. 

Edited January 27, 2018 by mbates14

[jamestlarson]

1 minute ago, mbates14 said:

If they are continually pushing definitions but cant really "find the problem". There is the slight chance that the system was HACKED. 

Look into that one. 

Malwarebytes is hacked?????! Uh oh.....

[asilver]

1 minute ago, Bazinga said:

Just redistribute v02.

^ This! 

[Concretesalad]

Why can't you repackage previous WORKING update and redistribute?

 

[mbates14]

2 minutes ago, jamestlarson said:

Malwarebytes is hacked?????! Uh oh.....

Nope, not saying that they were. However judging by how Malwarebytes software is acting and that their definition updates they have pushed 4, 5, and 6 hasnt fixed it, Well one could only assume... 

I dont know the architecture of the software, but Somehow its ignoring the rulesets issued by the newer definitions file for some reason. 

[jwhitespro]

2 minutes ago, asilver said:

^ This! 

When i checked my console machines with v02 had the issue...i don't know for sure if the console was completely up to date but it should have been based on the checkin date.

[BrentB9193]

8 minutes ago, holmebrian said:

really its only the website blocking thats broken should be all you need to disable

This didn't work for us.  We had to kill the entire client.

[mbates14]

I have a gut feeling that they either seriously bodged an update, or the potentional for ths system being hacked is there. How else can you explain it? 

Edited January 27, 2018 by mbates14

[Bazinga]

1 minute ago, jwhitespro said:

When i checked my console machines with v02 had the issue...i don't know for sure if the console was completely up to date but it should have been based on the checkin date.

Okay... what about v01? Maybe go back a full day?