Is It Risky to Store All Your Passwords in One Place?

What actually happened to LastPass in 2022

The breach came in two stages. In August 2022, attackers compromised a LastPass software developer and stole source code. They used what they learned to go after a senior DevOps engineer, exploiting a vulnerable third-party media server on the engineer's home computer and installing a keylogger that captured the corporate vault password after MFA (BleepingComputer). With those credentials the intruder reached decryption keys for an AWS S3 cloud backup and copied customer vault data.

The stolen data split in two. Unencrypted: customer names, email and billing addresses, phone numbers, IP addresses, partial credit card numbers, and the full list of website URLs each person had saved. Encrypted: the usernames and passwords inside every entry, protected by each user's master password through PBKDF2 key derivation (Wikipedia).

LastPass's initial August 2022 notice said customer data was untouched. On 22 December 2022 the company acknowledged that encrypted vault backups had been taken (Cybersecurity Dive). The UK Information Commissioner's Office later recorded more than one million affected UK users and imposed a £1,228,283 fine in November 2025, and LastPass settled a US class action for $24.5 million in February 2026, with $16 million earmarked for cryptocurrency losses (Wikipedia).

By late 2025 the stolen vaults were still producing damage. TRM Labs traced roughly $35 million in cryptocurrency thefts back to decrypted LastPass vaults, overwhelmingly from accounts whose master passwords were short, reused, or guessable (The Hacker News, TRM Labs).

Why most vaults did not get drained

Every serious password manager uses zero-knowledge encryption. The vault is encrypted on your device with a key derived from your master password, and the provider never sees the password or the key. Bitwarden, 1Password, Dashlane, Keeper, NordPass, Proton Pass and Zoho Vault all work this way (Bitwarden Security Whitepaper). You can see this across the field on our Best Password Manager 2026 list: zero-knowledge is table stakes.

That is why a stolen server backup is a bad day, not a catastrophe. The attacker ends up with ciphertext and has to brute-force the master password, one guess at a time. The key derivation function is deliberately slow so each guess is expensive. Bitwarden now defaults to 600,000 PBKDF2 iterations and also offers Argon2id, which is memory-hard and harder to accelerate on GPUs (Bitwarden KDF docs). 1Password uses 650,000 PBKDF2 iterations (1Password support).

The practical meaning: if your master password is long and random and your KDF is modern, an offline attacker trying to crack your vault is looking at timelines measured in centuries on current hardware. If any of those are weak, the number falls fast.

The single point of failure is your master password

This is the part the LastPass breach made unarguable. LastPass raised its default PBKDF2 iteration count from 5,000 to around 100,000 in 2018 but did not retroactively upgrade older accounts, so at the time of the breach a large share of legacy vaults were still being stretched at 5,000 iterations (Palant, Hive Systems).

Hive Systems' GPU benchmarks make the gap concrete. On a 12-GPU RTX 4090 rig at 5,000 iterations, a non-random master password can fall in hours. At 600,000 iterations, the same rig is slowed by two orders of magnitude, and a truly random passphrase of four or more words is effectively untouchable within any human timeframe (Hive Systems).

The practical rule: iteration count protects you, but it only multiplies the strength that is already there. 'Summer2024!' at 650,000 iterations is still bad. A random four- or five-word passphrase from the EFF diceware list is roughly 50 to 65 bits of entropy and does not care how many GPUs you throw at it.

1Password's extra layer: the Secret Key

1Password took a different architectural bet. On top of your master password it generates a 128-bit Secret Key when you create your account, and both are mixed together to derive the vault encryption key (1Password support). The server never has the Secret Key. That means a server-side theft of the encrypted vault, the LastPass scenario, does not let an attacker start guessing master passwords offline: without the Secret Key, there is no key to guess against.

This is why 1Password Individual, 1Password Families, 1Password Teams and 1Password Business get repeatedly cited for defense-in-depth. The cost is that the Secret Key has to live somewhere you can find it: on the Emergency Kit PDF, printed, in a safe, or on a second device.

Bitwarden Teams Organization, Bitwarden Premium and most other managers rely on master password plus iteration count alone. That is defensible if the password is strong and the KDF is modern, but it has one fewer layer than 1Password's model, and that difference was the whole story for people with weak LastPass master passwords.

What happens if you forget your master password

Zero-knowledge has a flip side: the provider cannot email you a reset link. Every manager handles this with recovery mechanisms you have to set up in advance.

1Password gives you three overlapping options. The Emergency Kit is a PDF with your Secret Key, your sign-in address, and space to record your account password; you print it and store it somewhere physical (1Password marketplace). Recovery Codes, launched more recently, are a one-time code you generate and store separately, which lets you reset the account password via the email on your account (1Password blog). On family and business plans, a family organizer or admin can recover another member's account, and the user gets a fresh Secret Key when they do (1Password support).

Bitwarden is stricter. There is no server-side reset. You have three pre-arranged paths: Emergency Access, where a trusted contact can request takeover of your vault after a delay you set; Organization Master Password Reset, where an admin on a Bitwarden Teams or Enterprise account can reset you; or the master password hint you stored at signup (Bitwarden support). If none of those are configured and you forget, the vault is unreadable and the only option is to delete the account and start over.

Business plans across the category, including Keeper Security Enterprise, Keeper Security Advanced Team, LastPass Business Advanced, Dashlane Business, Zoho Vault Enterprise, NordPass Business and RoboForm Business, all include admin-driven account recovery. That is one reason businesses can tolerate strict policies: there is a safety net that individuals have to build for themselves.

The setup checklist that makes a breach survivable

You cannot prevent your provider from getting hacked. You can make that hack a non-event. Every item below is either free or a one-time tax, and together they are what separated 'nothing happened' from 'cryptocurrency drained' after LastPass.

• Use a random passphrase of four or more words (EFF diceware) as your master password. Do not reuse it anywhere. Do not base it on anything personal.
• Turn on two-factor authentication on the vault itself. A hardware key such as YubiKey or Google Titan is phishing-resistant by design in a way that SMS and app-based codes are not (Panic Vault). If you can afford two keys, register both, so losing one is not a lockout.
• Set up recovery before you need it. On 1Password, print the Emergency Kit and generate a Recovery Code. On Bitwarden, invite an Emergency Access contact. On a business plan, make sure at least two admins can run account recovery.
• Protect the email account tied to your vault with its own strong password and its own second factor. Email is the recovery path for everything else; if it falls, the whole chain falls.
• Keep the 2FA code for the password manager and for your main email outside the password manager, in an authenticator app or on a hardware key. Putting them inside the vault recreates a single point of failure you just worked to remove.
• If you are on an older account on any manager, check your KDF settings. On Bitwarden that is Settings, Security, Keys. On 1Password the modern iteration count is enforced server-side. On any other manager, dig until you find the setting; if it is 5,000 or 10,000, raise it.

So should you still put everything in one app?

Yes, and the LastPass episode is the reason, not the counterexample. The alternatives are worse: a browser's built-in store with weaker recovery and no cross-vendor portability, a notebook you will lose, or reuse, which is the main way accounts actually get compromised today. The 2022 breach set off months of scrutiny across the category and surfaced no equivalent incidents at 1Password, Bitwarden, Dashlane, Keeper, NordPass or Proton Pass. Architecturally the field is in better shape than it was in 2021, with higher default iteration counts, Argon2id options, and in 1Password's case the Secret Key preventing offline guessing entirely.

The honest framing is that a password manager concentrates risk in one place where that risk can actually be defended: strong master password, hardware 2FA, and prepared recovery. Spreading passwords across your head, a notepad, the browser and three reused variants concentrates risk in one place where it cannot be defended, which is memory. Pick the former, do the setup once, and stop thinking about it.