Welcome back to ‘This Week in Getting Hacked’—the world’s greatest cybersecurity-related link dump! Each week, we bring you the best news stories from the cybersecurity field, letting you know who’s getting hacked, who’s hacking, what data is leaking, and about what you should take with caution. So strap in, change your password, and let’s find out who’s getting hacked this week!
On to the links….
Popular Gaming Provider Steam has been compromised. So stop buying those sale game you’re never going to play and change your password. We should probably also mention that this vulnerability has been present for at least 10 years.
The vulnerability let attackers take total control of a Steam user’s computer and all 125 million users were vulnerable.
Steam has since patched it in March 2018 before releasing details of the vulnerability in May. Valve, Steam’s parent company, did not respond to comments.
GDPR went into effect on the 25th and already Facebook and Google were hit with $8.8 billion in lawsuits on the very first day. There really isn’t much more to say here other than man people were waiting for this, huh?
Just ready to pounce on the Internet’s largest companies.
Budget Android phones are being sold with Malware pre-installed. 141 low-budget Android phones have been found with Malware infested firmware. The organization behind this has been around for a while and thought to have been eradicated. However, the only real harm they do is overlain ads on top of other apps, but that’s still SUPER ANNOYING.
Someone, please stop these people from just being total idiots.
Amazon’s Alexa has been spying on darn near everything you’ve been saying around it. And its been doing some strange things with those recordings. We won’t get into many of the stories here (you can read them by clicking this), what we’re more interested in what Amazon has to say. They provided Recode with the following explanation:
Echo woke up due to a word in background conversation sounding like “Alexa.” Then, the subsequent conversation was heard as a “send message” request. At which point, Alexa said out loud “To whom?” At which point, the background conversation was interpreted as a name in the customers contact list. Alexa then asked out loud, “[contact name], right?” Alexa then interpreted background conversation as “right”. As unlikely as this string of events is, we are evaluating options to make this case even less likely.”
Hmmm. Hopefully we’ll get some further updates out of this one.