Over $35 million stolen from an unknown number of victims
The catastrophic 2022 data breach of the LastPass password manager continues to haunt its former users, with new research from blockchain intelligence firm TRM Labs revealing a direct link to over $35 million in stolen cryptocurrency. The report, published in late December 2025, details how threat actors are methodically brute-forcing the encrypted customer vaults exfiltrated during the 2022 incident. By cracking weak or reused master passwords, attackers gain access to the sensitive data stored within, including cryptocurrency private keys and seed phrases. The thefts have been ongoing, with the most recent activity tracked to October 2025. The stolen funds are being laundered through a network associated with Russian cybercriminals, involving privacy mixers and high-risk exchanges. This long-tail attack campaign demonstrates the severe, multi-year consequences of a single, large-scale credential breach.
The threat stems from the 2022 LastPass breach, where attackers stole backups of approximately 30 million customer vaults. While these vaults were encrypted, their security relied entirely on the strength of each user's master password. The current attack campaign involves a large-scale, offline brute-force operation (T1110.004) against these stolen vaults. Once a vault with a weak master password is cracked, the attackers have access to all the credentials stored inside.
The primary targets of this campaign are the cryptocurrency assets of LastPass users. The attackers systematically search the decrypted vaults for:
Upon finding these secrets, the attackers immediately drain the associated wallets. The persistence of these thefts, occurring years after the initial breach, indicates that the attackers are continuously working through the massive trove of stolen vaults.
bitcoin, ethereum, private key, seed phrase, etc. (T1552.001).TRM Labs' on-chain analysis revealed a sophisticated money laundering operation pointing towards Russian cybercriminals:
T1496).The direct financial impact is over $35 million in confirmed stolen cryptocurrency, though the true figure is likely higher. The impact on victims is devastating, as cryptocurrency transactions are irreversible, leaving little to no recourse for recovery. This incident severely undermines the trust model of password managers, which are designed to be secure repositories for users' most sensitive data. The long-tail nature of the attack means that former LastPass users who have not changed all their critical passwords, especially crypto-related keys stored in their vaults, remain at risk years after the breach. It serves as a critical lesson on the importance of strong, unique master passwords and the risks of storing ultimate secrets like crypto seed phrases in any online service.
For victims, detection is unfortunately simple: the sudden disappearance of funds from their cryptocurrency wallets. At that point, response is limited.
Proactive Measures for Users:
For Users:
D3-SPP) The security of an encrypted vault is only as strong as the master password. Use a long passphrase (e.g., 5-7 random words) to make brute-force attacks computationally infeasible.D3-MFA) While MFA on the LastPass account itself did not prevent the vault theft, enabling MFA on all underlying services (like crypto exchanges) provides a critical layer of protection.For Service Providers (like Password Managers):
Enforcing the use of strong, long, and unique master passwords for password manager vaults to make offline brute-force attacks infeasible.
Mapped D3FEND Techniques:
Using dedicated offline hardware wallets for storing ultimate secrets like cryptocurrency seed phrases, rather than storing them in any software-based vault.
Enabling MFA on all underlying accounts (e.g., crypto exchanges) protected by the password manager to provide an additional layer of security if the vault is compromised.
Mapped D3FEND Techniques:
The primary lesson from the ongoing LastPass crypto thefts is the critical importance of the master password. For users, this means creating and memorizing a long, complex, and globally unique passphrase for their password manager. A passphrase composed of 5-7 random, unrelated words (e.g., 'correct-horse-battery-staple-ocean') is far more resistant to brute-force attacks than a complex but short password. For enterprises, this means enforcing strong master password policies for corporate password manager deployments and educating users on the risks of password reuse. Password manager providers should, in turn, implement checks for weak or breached passwords during master password creation and enforce minimum length and complexity requirements that make brute-forcing computationally prohibitive.
This incident proves that certain 'ultimate secrets' should never be stored in a cloud-based password manager, regardless of encryption. Cryptocurrency private keys and seed phrases fall into this category. The definitive mitigation is to use a dedicated hardware wallet (a form of hardware-based security). These devices store private keys in a secure, offline chip and require physical interaction to approve any transaction. The keys never leave the device, making them immune to remote theft even if the computer they are connected to is compromised. Users who stored keys in LastPass must migrate their assets to new wallets generated on a hardware wallet to be truly secure from this threat.
Password manager providers can further harden their applications to protect users. A key defense against offline brute-forcing is to significantly increase the number of key derivation iterations (e.g., PBKDF2 or Argon2 rounds) used to turn the master password into the encryption key. While LastPass did increase their defaults, this incident shows that for vaults created before the change, the protection was insufficient. Providers should proactively re-encrypt vaults with stronger settings when users log in. They should also implement client-side checks to warn users if their master password is weak, short, or has appeared in previous data breaches, compelling them to create a more secure one. This shifts some of the security burden from the user to the application's design.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats