Botched Security Update Cripples Thousands of Computers
girlmad writes "Thousands of PCs have been crippled by a faulty update from security vendor Malwarebytes that marked legitimate system files as malware code. The update definition meant Malwarebytes' software treated essential Windows.dll and .exe files as malware, stopping them running and thus knocking IT systems and PCs offline, leaving lots of unhappy users and one firm with 80% of its servers offline."
...is all I use these days.
Of course since Windows is "out of favor" here, one does not necessarily mention that Microsoft's "Security Essentials" is easily as good as most commercial Windows anti-malware packages, and much more "light weight". And free. And yes, everyone knows that Microsoft purchased the original technology (so what?) ...
If you want news from today, you have to come back tomorrow.
For once I'm happy that I'm too lazy to regularly update programs like that.
for using microsoft servers
I've yet to see an AV that actually can deal with browser add-on attacks.
The only thing that might help is Malwarebytes because it blocks by IP address.
If you want protection, use an ad blocker. Ad servers seem to be one of the chief causes, if not the top infection vector these days.
Maybe I'm doing something wrong, but I haven't seen a virus in a decade.
Sure there is. Kaspersky Anti-Virus Security Center has a Update Verification module built in, that allows a sysadmin to install the update to a known-clean test group and then run a virus scan BEFORE the update is applied to the rest of the machines. If the scan fails(ie, finds anything), the update is aborted and an email is sent to the admin. If Malwarebytes had that kind of thing(or if it did and the sysadmins actually used it), this wouldn't even be an issue.
I don't need to test my programs.. I have an error correcting modem.
Basically "stop doing stupid things with your computer".
Why a firm needed Malware Bytes on it's servers in the first place is the real question here.
If their results can be bought, Microsoft would have bought them.
The clue is in the name.
Yeah, stupid idiots, why didn't they write their own OS from scratch at the start, then they wouldn't have any of these problems.
systemd is Roko's Basilisk.