LastPass’s Costly Blunder: £1.2M Fine for Data Breach Fiasco in the UK

LastPass is facing a hefty £1.2 million fine from the UK’s Information Commissioner’s Office after a 2022 data breach compromised 1.6 million UK users. The fine comes as a slap on the wrist for a company that left the backdoor open for hackers, serving as a cautionary tale for data protection.

Pro Dashboard

Hot Take:

Ah, LastPass, the keeper of keys and, as it turns out, a Pandora’s box of security mishaps! With a £1.2 million slap on the wrist, or should I say, on the password manager, LastPass is learning the hard way that even the digital gatekeepers need a little more than a master password to keep intruders at bay. It’s a classic case of mixing business with pleasure — who knew sharing could be so hazardous? Looks like LastPass is now ‘LastPass’t the point of no return!

Key Points:

  • The UK’s ICO fined LastPass £1.2 million for a 2022 data breach affecting 1.6 million UK users.
  • The breach occurred in two parts, compromising both corporate source code repositories and customer data.
  • The attack was facilitated by a vulnerability in Plex Media Server and poor password management policies.
  • The second breach was exacerbated by a failure in LastPass’s cloud infrastructure communication.
  • ICO emphasized the need for separate passwords for personal and business accounts to enhance security.

Membership Required

 You must be a member to access this content.

View Membership Levels
Already a member? Log in here
The Nimble Nerd
Confessional Booth of Our Digital Sins

Okay, deep breath, let's get this over with. In the grand act of digital self-sabotage, we've littered this site with cookies. Yep, we did that. Why? So your highness can have a 'premium' experience or whatever. These traitorous cookies hide in your browser, eagerly waiting to welcome you back like a guilty dog that's just chewed your favorite shoe. And, if that's not enough, they also tattle on which parts of our sad little corner of the web you obsess over. Feels dirty, doesn't it?