A home media server and a password manager: the LastPass breach
Two linked incidents in 2022 ended with backups of LastPass customer vaults in attackers' hands. The route ran through one engineer's unpatched home software.

The chain that ended with backups of LastPass customer vaults in criminal hands started on a home computer, with a media server program that had needed an update since May 2020.
That is not a cheap shot at one engineer. It is the whole point of the case. LastPass had multi-factor authentication, a mature development environment, and the kind of security posture you would expect from a company whose product is secrets. The attack went around all of it by finding the one machine in the path that nobody managed.
Two incidents, linked
LastPass has always described this as two incidents, and the distinction matters for understanding both the attack and the criticism the company received.
Incident one: August 2022
An attacker gained access to LastPass's development environment using a compromised developer account, and took portions of source code and technical documentation. LastPass's position was that no customer data or vault data was taken in this incident, because the development environment did not contain any.
That statement was accurate and incomplete in an important way: what was taken was knowledge. Source code and technical documentation tell you how a system is built, where the valuable data lives, and who would have the keys to it.
Incident two: August to October 2022
Using information from the first intrusion, the attacker targeted one of four DevOps engineers who held the decryption keys for the cloud storage service where backups lived. The route in was not a corporate system at all.
- Exploit the home computer. The attacker exploited a remote code execution vulnerability in a third-party media software package on the engineer's personal computer. Reporting identified the software as Plex Media Server, and Plex confirmed the flaw as CVE-2020-5741, fixed in a release from May 2020 that the employee had never installed.
- Install a keylogger. Ordinary malware, doing the oldest job in the business.
- Capture the master password. The engineer authenticated with multi-factor authentication and then typed their LastPass master password. The keylogger recorded it.
- Open the corporate vault. With the master password, the attacker exported entries and shared folders from that engineer's LastPass corporate vault.
- Use the keys. Those entries included the decryption keys for cloud storage buckets containing configuration data, API and third-party integration secrets, customer metadata and backups of customer vault data.
The intrusion ran from around 12 August to 26 October 2022. LastPass has stated that no threat actor activity has been observed since 26 October 2022.
What was actually taken, and what that means
This is where precision matters most, because both panic and complacency were widespread at the time.
Unencrypted customer information. Company names, end-user names, billing addresses, email addresses, telephone numbers and IP addresses from which the service was accessed. This is directly usable for targeted phishing.
Vault backups with mixed protection. The backups contained both unencrypted and encrypted fields. Website URLs were among the unencrypted data. Usernames, passwords, secure notes and form-filled data were encrypted and, by design, decryptable only with the individual user's master password, which LastPass does not hold.
Two consequences follow. First, even without decryption, an attacker learns which services each person uses, which is a precise targeting list. Second, the encrypted fields are subject to offline attack: with the file in hand, an attacker can guess master passwords at their own pace with no rate limiting and no account lockout. For a long, unique master password that is impractical. For a short or reused one it is a matter of time. The security of each individual's vault came down to a choice that individual had made, possibly years earlier.
Confirmed, reported and unknown
Confirmed by LastPass
- The two incidents, the development environment compromise in August 2022 and the targeting of a DevOps engineer afterwards.
- Exploitation of a third-party media software package on the engineer's home computer, a keylogger, and capture of the master password after MFA.
- Access to cloud storage containing configuration data, integration secrets, customer metadata and vault backups.
- The categories of unencrypted and encrypted data listed above.
- That activity ceased after 26 October 2022, and the published guidance for consumer and business customers.
Reported and corroborated outside LastPass
- The identification of the software as Plex Media Server and the specific CVE, confirmed by Plex rather than by LastPass.
- That four engineers held the decryption keys.
- Subsequent research linking stolen vault data to cryptocurrency thefts from individuals whose seed phrases had been stored in password managers. The link is based on investigative analysis rather than official confirmation.
Unknown
- How the original developer account in incident one was compromised.
- How many vaults, if any, have actually been decrypted.
- The attacker's identity.
Why it matters technically
MFA does not protect a compromised endpoint. This is the single most useful correction the incident offers. Multi-factor authentication stops someone else logging in as you. It does nothing about malware watching the session you legitimately opened. Endpoint integrity is a separate control and it is the one that failed here. Our articles on MFA phishing and password-stealing malware cover the two different threat models.
Personal devices in privileged paths are the gap. The engineer was presumably working from home on their own machine, as many people do. An unmanaged device has no patch enforcement, no endpoint detection and no separation between work and a media server. If a role holds keys to production data, the device it uses has to be managed, and ideally it should be a dedicated administrative workstation that does nothing else.
Key custody was too concentrated. Four people could decrypt the backups, and compromising one of them was sufficient. Splitting key material, requiring two people to act, or keeping backup decryption keys in a hardware security module would each have broken the chain after the vault was opened.
Storing secrets in the same system you administer is circular. The decryption keys for the backups were in a corporate password vault that one password opened. Keys that protect everything should not live behind a single reusable secret.
Information is loot. The first incident took no customer data and enabled the second. When a breach takes "only" source code or documentation, the right assumption is that the attacker now knows where to go next, and the response has to include reviewing who holds privileged access and tightening it.
What an ordinary business should take from it
- List who can access your backups, and whether a single credential on a single device gets them there.
- Give privileged staff managed devices, with enforced patching and endpoint detection, and keep administrative work off personal machines.
- Separate the credentials that protect infrastructure from the general-purpose password manager your team uses day to day.
- Treat a long, unique master password as non-negotiable for anyone using a password manager, and prefer passkeys where services support them. Our business password manager article covers rollout.
- Never store recovery phrases or seed phrases in a password manager, or anywhere that is backed up to someone else's cloud.
- Assume a vendor breach will produce targeted phishing aimed at your staff, using the exact services they are known to use. See phishing that follows a breach.
Email claiming your password manager was breached? These are heavily imitated. Check the message with CyberWatch AI Scan and sign in only via your own bookmark, never a link.
Should you still use a password manager?
Yes, and the reasoning survives this incident. The alternative in practice is not a perfect system; it is reused passwords across dozens of sites, which is the single most reliable cause of account takeover. What LastPass changed is the standard of care: a very strong unique master password, multi-factor authentication, up-to-date clients, no seed phrases or recovery codes stored inside, and a vendor whose breach disclosures you can read. Our guides to password reuse and account security set out the trade-off in full.
The short version
An attacker took source code and documentation from a development environment, worked out who held the keys, exploited an unpatched media server on that person's home computer, logged their master password with a keylogger after they had passed multi-factor authentication, opened their corporate vault, and used the keys inside it to download backups of customer vaults over roughly eight weeks.
Nothing in that chain required breaking cryptography. It required one unmanaged device in a privileged path and a small group of people holding keys to everything. Both are findable in your own organization in an afternoon.
Frequently asked questions
What happened to LastPass in 2022?
Two linked incidents. In August 2022 an attacker used a compromised developer account to reach LastPass's development environment and take source code and technical documentation. Information from that first intrusion was then used to target a senior DevOps engineer and reach cloud storage holding backups of customer vault data.
How did the attackers reach the second environment?
They compromised the engineer's personal home computer by exploiting a vulnerability in a third-party media software package, installed a keylogger, captured the employee's LastPass master password as it was typed after multi-factor authentication, and opened that engineer's corporate vault. The vault held decryption keys for the cloud storage buckets.
Which software was exploited?
LastPass described it as a third-party media software package. Reporting identified it as Plex Media Server, and Plex confirmed a nearly three-year-old patched flaw, CVE-2020-5741, as the route to code execution. Plex said the fix had been available since version 1.19.3.2764 in May 2020 and the employee had never upgraded.
What customer data was taken?
Backups of customer vault data, plus account information such as company names, end-user names, billing addresses, email addresses, telephone numbers and IP addresses. The vault backups contained unencrypted fields including website URLs, and encrypted fields including usernames, passwords, secure notes and form-filled data.
Were the passwords in the vaults readable?
Not directly. The sensitive fields were encrypted and can only be decrypted with each user's master password, which LastPass does not store. The practical risk is offline brute-force attack against those backups, which is why weak or reused master passwords were the deciding factor for individual users.
How long were the attackers active?
The second intrusion ran from around 12 August to 26 October 2022, roughly eight weeks. LastPass has stated it saw no threat actor activity after 26 October 2022.
Why did multi-factor authentication not stop it?
It was not bypassed. The keylogger captured the master password after the employee had completed multi-factor authentication, which gave the attacker the vault contents from an already-authenticated session context. MFA protects the login, not a compromised endpoint.
What should LastPass users have done?
LastPass published guidance for consumer and business users, including reviewing account settings and iteration counts and rotating stored credentials. Anyone with a short or reused master password should have treated every stored credential as potentially recoverable and changed the important ones.
What is the main organizational lesson?
A small number of engineers held keys to everything, and one of them had an unmanaged personal device in the path. Privileged access needs to come with managed devices, segregated administrative workstations and no single credential that unlocks every backup.
Sources
- Notice of Recent Security Incident, LastPass
- Security Incident Update and Recommended Actions, LastPass
- Incident 2 details, LastPass Support
- CVE-2020-5741 Detail, NIST National Vulnerability Database
- CVE Record: CVE-2020-5741, CVE Program
- LastPass Says DevOps Engineer Home Computer Hacked, SecurityWeek
- LastPass Hack: Engineer's Failure to Update Plex Software Led to Massive Data Breach, The Hacker News
- Hacked home computer of engineer led to second LastPass data breach, CSO Online
- Input Capture: Keylogging, Technique T1056.001, MITRE ATT&CK


