ToolScore

The LastPass Breach Is Still Costing People Money

Over $35M stolen, still counting the number that matters here

By Stan K.

Four years after August 2022, the LastPass invoices keep arriving: a £1,228,283 UK fine in November 2025, a $24.5M US settlement, and crypto theft that never stopped — over $35M by 2023 and a ~$150M 2025 heist linked to the same stolen vaults. The verified chain, and the three lessons that transfer to any manager.

Most data breaches end. The LastPass breach did not: four years after the August 2022 intrusion, it was still generating invoices — a £1,228,283 UK regulator fine in November 2025, a $24.5M US class-action settlement, and a drip of cryptocurrency thefts that continued into 2025. This is the verified chain of events, what was actually inside the stolen backups, and why we treat breach history as a price column rather than a footnote.

The chain: from a media server to every vault backup

The intrusion that mattered did not start at LastPass’s front door. An attacker compromised a DevOps engineer’s personal Plex media server through an unpatched critical vulnerability and planted a keystroke logger. The logger harvested the engineer’s master password. That password opened the corporate vault — which held the keys to the backup infrastructure, including customer-data backups stored in Amazon S3. In August 2022 the attacker had already exfiltrated source code and technical documentation, including an encrypted copy of the key protecting those backups; with the engineer’s credentials, the customer vault backups themselves left the building.

The uncomfortable part is the genre: no cryptography was broken. A strong master password fell to a keylogger on a personal machine, and the blast radius was decided by what one engineer’s vault could reach.

What was actually inside the backups

The vault data was encrypted with each customer’s master password — but not all of it. Stored unencrypted: names, email addresses, billing addresses, partial card numbers, and website URLs. LastPass said usernames were partially unencrypted; the exact split stayed unclear, and claims about IP addresses never checked out against the sources, so we don’t repeat them here.

Two consequences. First, even users with uncrackable master passwords handed attackers a map — every site they had an account on, tied to their email. Second, the vaults that did fall were not equally protected: LastPass had raised its minimum PBKDF2 iteration count over time, so vaults created in the early years carried outdated, low iteration counts — crackable on commodity hardware. (The specific counts you may have seen quoted elsewhere never checked out against a live source; we won’t print them.)

Three lessons that transfer to any manager

One: the master password is only as strong as the machine you type it on — a keylogger beats entropy. Two: if your manager exposes its KDF/iteration settings, raise them; the LastPass victims who were hurt worst were hurt by a default. Three: ask what stays unencrypted — URLs, emails and notes are a map of your life even when passwords hold.

The bill, itemized so far

  • The regulator. On 20 November 2025 the UK’s ICO fined LastPass UK Ltd £1,228,283 — reduced by 30% for remediation, covering more than 1 million affected UK users.
  • The class action. A $24.5M US settlement, agreed in principle in November 2025 and reported in February 2026, with $16M earmarked for crypto losses.
  • The victims who never got a claims form. By September 2023, Krebs counted more than 150 victims and more than $35M in stolen cryptocurrency. In 2025 an additional ~$150M heist was linked to the same stolen vaults — with seed phrases stored in LastPass the common factor across victims. Storing a seed phrase in a vault whose backups just left S3 converted a password incident into a life-savings incident.
The LastPass breach — the bill so far
UK ICO fine (Nov 2025) £1.23M
US class-action settlement $24.5M
Crypto stolen by 2023 $35M+
2025 heist (linked) ~$150M

That last line is why LastPass has no row in our pricing tables: after the vault backups fell, its effective price stopped being measurable in subscription dollars. For contrast, the October 2023 Okta support-system breach that touched 1Password’s admin accounts compromised zero vaults — the difference between an incident and a catastrophe is architecture, not luck.

What a year of password security costs per person, at vendors whose record held, is in Password Managers: Cost per Person — from $7.98 per head (Bitwarden Families) to $0 (Bitwarden Free, KeePassXC). The full free-tier, family-math and breach-history tables live in the Password Managers hub.

Numbers change — the math doesn't
Token prices and plan limits shift monthly; the structural arguments in this guide age slowly. For current per-tool numbers see the live rankings.