Password recovery · KeePass · Bitwarden · LastPass · 1Password
Your wallet password is probably in a password manager. Forgot the master password? Here’s the recovery path.
Most wallet passwords are not written down anywhere except a password manager. When the master password is forgotten, the wallet password is locked inside — but the manager itself is crackable offline. This page explains how, and when it is worth trying.
By Robbert Bink · ~5 min read · Published 8 August 2026 · Last reviewed: 14 August 2026
KeePass, LastPass and 1Password vaults are encrypted with a key derived from your master password — deliberately slow, but crackable. With a copy of the vault and a good candidate list, hashcat can test millions of guesses per hour. The same rule applies: human-chosen passwords with clues are recoverable; long random ones are not.
Why this page exists
The search checklist tells you to check your password manager first — because that is where most wallet passwords are stored. But “checking” only works if you can open the manager. If the master password itself is gone, the wallet password is not lost: it is locked behind a second password, and that second password is exactly the kind of problem this site covers. (If the password is locked inside a protected document instead of a manager, the encrypted-file guide is the matching path.)
Which managers are crackable — and how fast
These are the official hashcat modes, straight from the hashcat example-hashes list:
| Manager | Mode | What it means |
|---|---|---|
KeePass 1 (.kdb) / KeePass 2 (.kdbx) | 13400 (AES-KDF, KDBX ≤ 3); KDBX 4: 34300 Argon2 / 34301 AESKDF | KeePass 1 saves as .kdb, KeePass 2 as .kdbx — the classic desktop manager. Mode 13400 covers KeePass 1 (AES/Twofish) and KeePass 2 with AES-KDF (KDBX ≤ 3). KDBX 4 does not force a single KDF: KeePass lets you choose AES-KDF or Argon2, so identify the database version and KDF first (keepass2john reports which one your file uses) — current hashcat versions support both KDBX 4 variants via 34300 (Argon2) and 34301 (AESKDF). |
| LastPass (local vault cache) | 6800 | You need your own locally cached vault (never anyone else’s); the hash line uses your email, the iteration count and the vault blob. |
Bitwarden (local data.json) | 23400 | Works from your own local vault file (data.json) — extract the hash line with bitwarden2hashcat or bitwarden2john. Before extracting, determine which KDF the account uses: mode 23400 and the standard extractor cover the supported Bitwarden format they were designed for — do not assume an Argon2id-configured vault follows the same route. The app’s encrypted export is a different file and is not used for cracking. |
| 1Password (agilekeychain) | 6600 | Legacy format — keychain files on your own device. Convert with 1password2john.py first; hashcat needs the extracted hash line, not the raw keychain. |
| 1Password (cloudkeychain) | 8200 | Legacy/later keychain format — still an offline file on your device. Convert with 1password2john.py before running hashcat. |
| 1Password (mobilekeychain) | 31800 | The local mobilekeychain format in 1Password 8 — a separate route, not the 6600/8200 1password2john conversion; verify the exact local format and required extraction route first. Modern 1Password accounts also use a Secret Key alongside the account password — that key is part of what has to be recovered. |
Password Safe v3 (.psafe3) | 5200 | Another legacy desktop manager with a crackable format. |
The speed reality: modern managers use hundreds of thousands of key-derivation iterations (KeePass 2 with Argon2 or high AES-KDF rounds, LastPass with high rounds). That makes a random 16-character master password effectively unreachable — but a human-chosen master password, which is most people’s reality, is exactly where a good candidate list wins.
The walkthrough — five steps
-
1
Protect the database
Work on a read-only copy of the vault or keychain file, offline, on your own machine. Never upload the vault to a public checker or unknown website — a website asking for your
.kdb/.kdbxor keychain is harvesting it. The protection rules apply to manager files too. -
2
Get the vault into a hash line
KeePass: identify whether you have a KeePass 1
.kdbor KeePass 2.kdbxdatabase first, then thekeepass2johnscript (from the John the Ripper project) extracts the hash line from your database. For KDBX 4, also check which KDF the file actually uses: KeePass lets you choose AES-KDF or Argon2, and current hashcat versions support both via 34300 (Argon2) and 34301 (AESKDF). LastPass: locate the locally cached vault in your browser extension’s storage (thelastpass2johnscript reads it) — the account’s CSV export does not contain the hash. Bitwarden: find the localdata.json(desktop app or browser extension), determine which KDF the account uses, and extract the hash line withbitwarden2hashcatorbitwarden2john(hashcat mode23400— the standard extractor does not read Argon2id parameters, so do not assume that route applies to every vault). 1Password: identify the exact format first, then convert before running hashcat — for agilekeychain (6600) and cloudkeychain (8200), hashcat’s own guidance points to1password2john.py;31800is a separate local mobilekeychain format (1Password 8) — verify the exact local format and required extraction route first. Modern accounts also use a Secret Key alongside the account password — that key is part of what has to be recovered. The hashcat walkthrough covers the general extraction flow. -
3
Pick the mode
From the table above:
13400KeePass with AES-KDF (KDBX ≤ 3); KDBX 4 may be Argon2 (34300) or AES-KDF (34301) — identify the KDF first.6800LastPass,23400Bitwarden,6600/8200/318001Password,5200Password Safe. -
4
Build the attack
A wordlist from your password hint list with rules, or a mask when you remember the shape:
hashcat -m 13400 vault.hash words.txt -r rules/best66.ruleThis command is for AES-KDF databases (mode 13400). If the database is KDBX 4, mode 13400 will not load it — check the KDF that
keepass2johnreports: Argon2 databases use hashcat mode 34300, AES-KDF KDBX 4 databases use mode 34301. Master passwords follow the same habits as every other password you ever made — years, names, patterns. That is the memory work, and it decides the outcome. -
5
Read the result — and unlock the chain
A cracked master password may open the vault, and inside it is the wallet password (and often the seed phrase backup too) — for some password managers. For modern 1Password accounts, the account password alone is not enough: the Secret Key, an already signed-in device, Emergency Kit, recovery code, or another supported recovery route may also be required. If the status screen shows an unworkable pace, the verdict is that the master password was random — and no tool changes that. Check the math before investing weeks.
Never upload your vault to a public checker or unknown website
The vault contains every password you own, including the wallet password. Legitimate recovery runs offline on your own machine — never upload your vault file to a public checker or unknown website.
Sources & references
Keep going — it’s all free
Not sure what you lost or what’s possible?
Take the quick diagnosis for a first verdict — it stops early when the answer is already clear — then work the search checklist. Everything here is informative, runs offline, and is free to use.