how it happened
- whoattackerfirst breach: source code
- the gaphome computerunpatched Plex, keylogger
- thenbackup keys vaultcloud backups copied
- the resultcustomer vaultslater linked to $35M+ crypto theft
what everyone assumed
You draw a security perimeter around the things you own and manage: the corporate laptop, the office network, the systems in scope for your audit. A personal computer at an employee’s house sits outside that line by definition. It is their device, their network, their software, and reaching into it feels both impractical and intrusive. The boundary is reasonable, because you cannot patch a machine you do not administer, and the audit does not ask you to.
what happened
The 2022 LastPass breach came in two connected acts. In August 2022, an attacker compromised a developer’s corporate environment and took source code and technical documentation, including an encrypted copy of a key used to protect backups. That intrusion was detected and contained, and it looked finished. Working from what they had learned, the attackers then identified a specific target: one of only four DevOps engineers who held the ability to decrypt production backups. They reached that engineer through their home computer, exploiting the unpatched vulnerability in Plex media software running on it, and installed a keylogger. When the engineer entered their master password after passing multi-factor authentication, it was captured.
step by step
- August 2022a developer environment is breachedSource code and an encrypted backup key are taken. It looks contained.
- one of four engineers who can decrypt backups is targetedThrough unpatched Plex software on their home computer.the assumption breaks here
- a keylogger captures the master passwordTyped after MFA was passed.
- late 2022 into 2023customer vault backups stolenPasswords encrypted; URLs, names, emails and some billing data not.
how it surfaced
With the engineer’s captured credentials, the attackers reached an internal vault holding the keys to LastPass’s cloud backups, and exfiltrated backup copies of customer vault data. LastPass disclosed the scope in stages through late 2022 and into 2023. The stolen backups held customer vault data in a format where sensitive fields such as usernames and passwords remained encrypted with keys derived from each user’s master password, while some fields, including website URLs, were not encrypted, alongside customer names, email addresses, phone numbers, and some billing details. The encrypted material was only as safe as each user’s master password. The assumption retired itself at the point of entry: the vault theft traced back through a home computer running consumer media software, a device no corporate audit had ever seen.
Scope is defined by access, not by who owns the hardware.
If a person can reach your most sensitive systems, then every device that person authenticates from is in scope, including the one on their kitchen counter. An attacker follows the access, and the access does not stop at the office door.
picture it at a company like yours
The company here is made up. The other two paths are not: they happened, and each links to the story.
- in this storythe day it mattersAn attacker targets that home computer and records the engineer's master password.what it costs youYour most protected data is stolen through a device your company never saw.
- or it goes like thisit happenedKaseya VSA, 2021howYour IT provider's remote-management tool is broken into.what leavesevery computer it manageswho ends up with ita ransomware crew hitting all its clients at once
- or it goes like thisit happenedUS Treasury and BeyondTrust, 2024howThe master key of a remote-support product is stolen.what leavesstaff computers and the documents on themwho ends up with ita state-sponsored group
sources
your turn
what you can do about it
this week
List the handful of people with that level of access and ask, plainly, whether their authentication is bound to hardware you trust or would survive on any personal machine they happen to use.
BYOD and home devices feel like someone else's problem because you cannot manage what you do not own. The quiet-months question narrows it: which of your people can reach production or decrypt sensitive data, and from what devices do they actually log in. The lesson from LastPass was not about one engineer's home network. It was that the smallest group with the deepest access is exactly where the perimeter has to reach.
go deeper
if you're not sure where to start
Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.
open the checklist →
