Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Happened in the LastPass Breach?

Two linked intrusions in 2022 ended with attackers holding encrypted customer vault backups, taken after a senior engineer’s home computer was compromised through unpatched media software.

Illustration for the cybersecurity term LastPass Breach
Home / Blog / Cybersecurity Terms / What Happened in the LastPass Breach?
17 November 2026

What Happened in the LastPass Breach?

What Happened in the LastPass Breach?

LastPass disclosed two connected incidents in 2022. The first, in August, involved an attacker compromising a developer account and taking source code and technical documentation from the development environment. The company said at the time that no customer data was affected, and on the available evidence that was true. The second incident, disclosed in December, was the serious one, and it used information obtained in the first.

The Second Intrusion

Between August and October 2022 the attacker targeted four senior DevOps engineers who held the decryption keys for the company’s cloud backup storage. They compromised one engineer’s home computer by exploiting a vulnerable third-party media server application running on it, installed a keylogger, and captured the engineer’s master password as it was typed into their own password manager after multi-factor authentication had been satisfied.

With those credentials the attacker reached a shared cloud storage environment and took backups containing customer vault data, together with unencrypted customer metadata including company names, billing addresses, email addresses, telephone numbers, and the IP addresses from which customers had accessed the service.

What Was and Was Not Encrypted

Vault entries were partially encrypted. Usernames, passwords, secure notes, and form-filled data were protected with 256-bit AES using a key derived from each user’s master password, which LastPass does not hold. Website URLs were not encrypted. That distinction mattered more than it first appeared: even without cracking a vault, an attacker could see which services each customer used, which is a precise targeting list for phishing and for attacks on cryptocurrency exchanges.

Key derivation strength varied dramatically. LastPass used PBKDF2, and had increased the default iteration count over the years, but accounts created under older defaults retained them. Some legacy accounts were found to have iteration counts in the low thousands, and a small number had effectively one iteration, making offline attacks against those vaults far cheaper than the published default suggested. Security researchers subsequently connected a series of large cryptocurrency thefts from 2023 onwards to vaults believed to have come from this breach.

The Lessons Are Not “Do Not Use a Password Manager”

A password manager remains the right answer for almost every organisation and individual. The alternative — reused passwords across dozens of services — fails faster and more often. What the incident actually teaches is more specific:

The structural point is the one worth taking to a board. Concentrating secrets in one service creates enormous convenience and a single high-value target, which is why privileged access management for administrative credentials, hardware-backed keys for the accounts that matter most, and multi-factor authentication that resists phishing belong alongside the password manager rather than behind it.

At Privia Security, we review secret storage and privileged workflow design as part of our infrastructure and architecture review services.

FAQ – Frequently Asked Questions

Were LastPass Vaults Decrypted by the Attackers?

Not directly. Vault credential fields were encrypted with a key derived from each user’s master password, which the company does not hold, so the attacker took ciphertext. The risk is offline attack at leisure: vaults protected by weak master passwords or low iteration counts are realistically crackable, and researchers have linked later cryptocurrency thefts to vaults believed to originate from this breach.

Why Did Unencrypted URLs Matter?

Because they reveal which services each customer uses without any decryption at all. An attacker can see that a given person holds accounts at a particular bank, exchange, or corporate portal, which turns a generic stolen dataset into a targeted phishing and account takeover list. It also tells them which vaults are worth the cost of an offline attack.

Should I Stop Using a Password Manager?

No. The realistic alternative is password reuse, which fails far more often and far more cheaply. Use a long unique master passphrase, confirm your key derivation iteration count meets the current default rather than the one in force when the account was created, enable phishing-resistant multi-factor authentication, and prefer providers that encrypt the entire record including URLs.

What Should an Organisation Do After a Provider Breach Like This?

Assume the encrypted copies are permanent and act accordingly. Change the master password, rotate the credentials stored in the vault starting with administrative, financial, and remote access accounts, and review authentication logs for the services involved. Afterwards, check whether any privileged key material was reachable from personal or unmanaged devices.

Related Terms

You May Be Interested In These

What Is Terrascan?

Cybersecurity Terms

17 November 2026

What Is Terrascan?

Read More
What Is Threat Modelling?

Cybersecurity Terms

17 November 2026

What Is Threat Modelling?

Read More
What Is Confidential Computing?

Cybersecurity Terms

17 November 2026

What Is Confidential Computing?

Read More