Post cover image
A vault can look secure and still fail — the LastPass breach showed how stolen encrypted vaults can enable offline password cracking.

October 15, 2026

Your Password Manager Can Be Hacked Without Stealing Your Password.

LastPass told 25 million users their encrypted vaults were safe. Three years later, $35 million in cryptocurrency had been drained from…

By Raj Kanjariya

9 min read

THE ONE TOOL YOU TRUSTED COMPLETELY

LastPass told 25 million users their encrypted vaults were safe. Three years later, $35 million in cryptocurrency had been drained from those same vaults. The passwords were never stolen. The encrypted containers were — and that turned out to be enough.

He had done everything the security guides told him to do.

Unique password for every website. Randomly generated. Stored safely in LastPass — one of the world's most trusted password managers, used by 25 million people and 85,000 businesses.

When LastPass announced a breach in December 2022, he read the statement carefully.

"Customer vault data was stolen. However, vault contents remain encrypted with your master password. As long as you have a strong master password, your data is safe."

He exhaled. His master password was "Football2019!" — not perfect, but surely strong enough.

Fourteen months later, his cryptocurrency wallet was empty.

The breach led to further incidents because stolen vault backups can be subjected to offline cracking attempts. In 2025, LastPass settled a class action lawsuit for $24.5 million for losses incurred by customers whose vaults had been accessed.

He was one of more than 150 confirmed victims. His vault had been cracked.

The attackers never needed his master password.

They just needed time.

What Actually Happened — Step by Step

The LastPass breach wasn't a single dramatic hack. It was a methodical two-stage operation that unfolded over four months — and its consequences are still active in 2026.

Stage 1 — August 2022: The Developer's Laptop

The breach began with a compromised developer account in August and escalated when attackers used stolen data to target a senior engineer's home computer. The attacker exploited a vulnerability in Plex media software on the engineer's home computer to install a keylogger, capturing the master password needed to access LastPass's corporate vault.

A keylogger on a home computer. Through a vulnerability in Plex — a media streaming application that has nothing to do with password management. The senior engineer's personal laptop, used to access corporate systems, compromised through an unrelated application.

Stage 2 — Late 2022: The Vault Backups

With the corporate master password captured, the attackers accessed LastPass's cloud storage — Amazon S3 buckets containing encrypted backup copies of every customer's vault.

The breach exposed encrypted customer vaults and unencrypted metadata for millions of users — including URLs, usernames, billing addresses, and IP addresses.

Read that carefully. The vault contents were encrypted. The metadata — the list of every website you had a password for, your billing address, your IP address — was stored in plaintext.

Attackers now knew exactly which sites each user had accounts on. Which banks. Which crypto exchanges. Which email providers. They didn't have the passwords yet. They had a map of where the passwords led.

Stage 3–2023 Through 2026: The Quiet Cracking

Encrypted vault backups stolen from the 2022 LastPass data breach have enabled bad actors to take advantage of weak master passwords to crack them open and drain cryptocurrency assets as recently as late 2025.

The thefts didn't happen in a rush. They happened slowly, methodically, over three years. Each cracked vault opened a new set of accounts to drain.

None

The Encryption Promise — And What It Actually Meant

LastPass's statement after the breach included a specific claim:

"It would take millions of years to crack your master password."

That sentence is technically accurate. And almost entirely misleading.

"Millions of years" assumes a specific type of attack — trying passwords one at a time against a live system, with rate limiting, with lockouts after failed attempts.

Offline attacks are different.

ONLINE ATTACK (against a live server):
→ Rate limited: 5 attempts before lockout
→ Timeout delays between attempts
→ IP blocking after suspicious activity
→ Millions of years is accurate here

OFFLINE ATTACK (against stolen encrypted data):
→ No server. No rate limit. No lockout.
→ No timeouts. No IP blocking.
→ Attackers have the encrypted data locally
→ Can try millions of passwords per second
→ Using powerful GPU clusters running 24/7
→ Indefinitely. Without alerting anyone.

These so-called offline attacks allow the bad guys to conduct unlimited and unfettered brute force password cracking attempts against the encrypted data using powerful computers that can each try millions of password guesses per second.

"Football2019!" seems random. Against an online system with rate limiting, it would hold. Against an offline attack with a GPU cluster trying millions of variations per second — names, years, common substitutions — it falls in hours.

The encryption is real. AES-256 is genuinely unbreakable. The weakness is not the encryption algorithm. The weakness is the key — the master password that protects the encryption.

If your master password is a word, a name, a phrase, a date, or any combination that follows human patterns — an offline attack has unlimited time to find it.

The Metadata Problem Nobody Talked About

The stolen vault contents were encrypted. But something else was stored alongside them — and it wasn't encrypted at all.

Website URLs are unencrypted in stored vault data.

The list of every website you had a password for was stored in plaintext. Binance. Coinbase. Kraken. Your bank. Your email.

Attackers sitting with 30 million vault backups could sort users by which crypto exchanges they had accounts on — before cracking a single password.

They prioritized.

Users with crypto exchange credentials stored in LastPass became the primary targets. The unencrypted URL list was a map to the highest-value vaults. Crackers focused computing resources on those users first.

The encryption protected what was inside the vault. The metadata pointed to exactly whose vault was worth cracking.

Three Years of Quiet Theft

The scale of what followed is still being measured.

Backups of around 30 million customer password vaults were exposed in the incident, creating what TRM Labs described as a 'long-tail risk' for more than 25 million users. Any vault protected by a weak master password could eventually be decrypted offline, turning a single 2022 intrusion into a multi-year window for attackers to quietly crack passwords and drain assets over time.

More than $35 million in siphoned digital assets have been traced, out of which $28 million was converted to Bitcoin and laundered via Wasabi Wallet between late 2024 and early 2025.

$28 million. Laundered. Between late 2024 and early 2025 — two to three years after the original breach.

Court filings confirm that victims' wallets were compromised through stolen password vault data, not phishing, not malware. The US Secret Service seized $23 million connected to the breach.

The victims weren't phished. They weren't infected with malware. They did nothing wrong in 2024 or 2025. Their data was stolen in 2022. Their vaults were cracked at the attackers' leisure. Their accounts were drained when the attackers were ready.

TRM Labs traced $35M in crypto stolen via weak vault passwords from the 2022 LastPass breach, with laundering patterns pointing to Russian exchanges.

And the campaign isn't over.

Attackers still have those 30 million encrypted vault backups. Vaults that haven't been cracked yet will be tried until they are — or until the computing cost exceeds the expected value inside.

Every vault that hasn't been cracked is still in someone's possession, on a server somewhere, being tried against a wordlist. Users who had LastPass accounts in 2022 and have never changed their master password are still at risk — today, in 2026, four years later.

Why This Isn't Just a LastPass Problem

LastPass is the case study because the breach was large and the consequences are documented. But the architectural issue — encrypted vault plus human-chosen master password plus offline cracking potential — is not specific to LastPass.

Any password manager that stores your encrypted vault where it can be stolen faces the same risk surface. The vault is only as secure as the master password protecting it.

The differences between password managers are in the security model around the vault:

WHAT MATTERS IN A PASSWORD MANAGER:

1. WHERE IS THE VAULT STORED?
   → Cloud sync (convenient, breach risk)
   → Local only (safer, no sync)
   → Zero-knowledge architecture (server never
     sees your key — only encrypted data)

2. WHAT IS THE PBKDF2 ITERATION COUNT?
   → How many times is your master password
     hashed before it becomes the encryption key?
   → More iterations = slower cracking
   → LastPass (2022): some users had 1 iteration
     (old accounts from years prior)
   → Bitwarden default: 600,000 iterations
   → 1Password: uses PBKDF2 with 650,000 iterations
     + additional key material

3. IS METADATA ENCRYPTED?
   → LastPass: URLs stored unencrypted
   → Bitwarden: All vault data encrypted
   → 1Password: All vault data encrypted

4. WHAT IS THE ZERO-KNOWLEDGE MODEL?
   → The server should never have your
     decryption key
   → Decryption should happen on your device
     with your master password
   → Verify this in the security documentation

The Iteration Count — The Detail Almost Nobody Checks

Users who did not update password iteration settings are at the highest risk of vault decryption.

This is the technical detail that determined who got cracked and who didn't.

PBKDF2 iterations are the number of times your master password is mathematically transformed before it becomes the encryption key. More iterations = more computing time required per guess.

LASTPASS IN 2022:
Old accounts (created before ~2018):
→ 1 iteration PBKDF2
→ Attackers can try 10 MILLION
  guesses per second per GPU

LastPass current default:
→ 600,000 iterations
→ Dramatically slower to crack

BITWARDEN:
→ 600,000 iterations (default)
→ Configurable up to much higher

1PASSWORD:
→ Uses PBKDF2 + additional secret key
→ The "secret key" is stored separately
→ Even if vault is stolen + master password
  cracked, the secret key is also required

If you had LastPass before 2018:
Your vault may have had 1 iteration.
Not 600,000. One.

This is why some users were cracked quickly and others weren't. Not based on password strength alone — based on which year they created their LastPass account and whether they ever updated their encryption settings.

None

What To Do Right Now

If you used LastPass before 2022:

STEP 1 — Assume your vault was stolen.
Not might have been. Was.
30 million vaults were taken.
If you had an account, yours was one of them.

STEP 2 — Change your master password immediately.
Make it strong: 20+ characters, random, passphrase.
Example: "correct-horse-battery-staple-2026"
This doesn't un-steal the old vault —
but if crackers haven't cracked it yet,
a stronger current password limits
future damage.

STEP 3 — Move any crypto.
If you stored seed phrases or private keys
in LastPass before December 2022:
Move the crypto to a new wallet NOW.
The seed phrase from the old wallet
should be considered compromised.

STEP 4 — Change passwords for critical accounts.
Banks, email, crypto exchanges, anything
stored in LastPass before December 2022.
Prioritize accounts linked to financial assets.

Choosing a password manager going forward:

BITWARDEN (Recommended)
→ Open source — code is auditable
→ 600,000 PBKDF2 iterations (default)
→ All vault data encrypted including URLs
→ Zero-knowledge model
→ Self-hostable if you want full control
→ Free tier is genuinely complete

1PASSWORD (Also strong)
→ Secret Key model — extra layer beyond master password
→ Even with master password cracked,
  Secret Key also required
→ All vault data encrypted
→ Regular third-party security audits

KEEPASS (Maximum control)
→ Local only — no cloud, no breach risk
→ Vault never leaves your device
→ Manual sync via your own methods
→ Open source, widely audited
→ Requires more technical management

LASTPASS (Proceed with caution)
→ Has implemented improvements since 2022
→ Track record makes trust difficult
→ History of breach remains
→ Now a separate company (post-GoTo split)

The Master Password You Actually Need

WEAK (crackable in hours offline):
Football2019!
Password123
Tr0ub4dor&3
Summer2022!

These feel strong.
Against an offline GPU cluster:
They fall quickly.

 STRONG (genuinely resistant):
Method 1 — Random passphrase:
"correct-staple-battery-horse-lamp-72"
→ Long. Random words. Number added.
→ Memorable. Genuinely strong.

Method 2 — Random characters:
"Xk9#mP2$nQr7@jL4"
→16+ characters, fully random
→ Use a different password manager
  to store this password

Method 3 — Diceware:
Roll physical dice to select words
from the EFF wordlist
→ Mathematically provable entropy
→ No human pattern = nothing to guess

WHAT NEVER TO USE:
→ Any word from any dictionary
→ Names + years
→ Keyboard patterns (qwerty, 123456)
→ Anything you can remember easily
   without effort

The golden rule:
If your master password is memorable
because it follows a pattern,
it can be cracked.

The One-Sentence Insight

Password managers protect your passwords behind a master password — and when a company stores your encrypted vault in the cloud, "your data is encrypted" means exactly as much protection as your master password provides against an attacker with unlimited time, unlimited computing power, and no rate limits.

Conclusion

"Any vault protected by a weak master password could eventually be decrypted offline, turning a single 2022 intrusion into a multi-year window for attackers to quietly crack passwords and drain assets over time."

That sentence came from TRM Labs' official report. It describes what happened. It also describes what is still happening.

The 30 million vault backups stolen in 2022 still exist on attackers' servers. Every vault that hasn't been cracked is still being worked on. The campaign doesn't end until either the computing cost exceeds the expected value — or every vault with anything valuable inside has been opened.

Password managers are still the right tool. Using unique, randomly generated passwords for every site — managed by a password manager — is dramatically more secure than reusing passwords or writing them in a notebook. That hasn't changed.

What changed is the understanding of what "your vault is encrypted" actually guarantees. It guarantees that attackers need your master password to access your data. It doesn't guarantee they can't get your master password, offline, with enough time and computing power.

The defense is a master password that is genuinely random, genuinely long, and genuinely not guessable — not strong-feeling, but strong by the standards of what GPU clusters can try in an afternoon.

Change yours today. If you used LastPass before 2022, rotate the passwords that were inside it. Move any crypto whose seed phrases lived there.

The breach was in 2022. The consequences are still arriving in 2026.

Connect With Me 🙏

Thanks for reading!

If you just opened your password manager to check your master password strength — good. That's exactly why this was written.

👉 Follow on Medium: medium.com/@rajkanjariya2020

Portfolio: rajkanjariya.dev

LinkedIn: Raj Kanjariya

— Raj Kanjariya, Full-Stack Developer & AI Researcher