MultiBit Classic Wallet Password Lost, No Seed Phrase Documented (2014)
IndeterminateWallet passphrase was unavailable — whether access was ultimately recovered is not known.
In January 2021, a user identified as mr_fish2021 recovered an old Windows computer containing a MultiBit Classic wallet created in 2014. The wallet held an undisclosed amount of Bitcoin. The user possessed all wallet files—including the standard wallet file, rolling backups, and variants labeled as unencrypted backups (wallet-unenc-backup)—but could not recall the password protecting them. No seed phrase or recovery words had ever been recorded when the wallet was originally created, a common omission in the pre-hierarchical deterministic wallet era when such practices were not yet standard.
MultiBit Classic, released during Bitcoin's early years, applied password-based encryption comprehensively across all backup formats. The multibit_recovery utility also requested passwords for all file variants, confirming that encryption was universal rather than selective. The user attempted recovery using btcrecover with password lists and character-set tokens on macOS Big Sur, reporting low confidence in success within reasonable timeframes. Forum users BitMaxz and HCP provided technical guidance on extracting password hashes via multibit2john.py for use with hashcat, and suggested experimenting with character-set masks based on likely password patterns. The user reviewed old notebooks and backup locations searching for password clues but found none. The visible thread documents exploration of GPU acceleration and Cython compilation for faster hash cracking but does not record a resolution. The incident illustrates a critical vulnerability of older wallet software: universal encryption applied to all backup formats, combined with the absence of seed phrase backup practices typical before HD wallets became standard.
| Stress condition | Passphrase unavailable |
| Custody system | Software wallet |
| Outcome | Indeterminate |
| Documentation | Partial |
| Year observed | 2021 |
| Country | unknown |
Why passphrases fail years after they are set
The failure mode documented consistently across observed cases is temporal: the passphrase is set with confidence, not used for an extended period, and then cannot be reproduced exactly when needed. A single character difference — different capitalization, an added space, a slightly different special character — produces a different wallet with a zero balance. The holder may be certain they remember the passphrase while being unable to produce the exact string that was originally set.
What makes this particularly difficult is that there is no signal at the moment of failure. A wrong passphrase does not produce an error message. It opens an empty wallet. The holder sees a zero balance and typically concludes the passphrase was wrong — but without knowing which part was wrong, or by how much.
Professional passphrase recovery services can attempt permutations when the holder has partial information: they remember the general structure, typical patterns they use for passwords, the approximate length, or that it included a specific word. Recovery from total non-recollection is not feasible.
The preventive action is to store a passphrase record — not with the seed phrase, which would defeat its security purpose, but in a separate secure location accessible to the holder and potentially a designated recovery person. A passphrase that exists only in memory has a time horizon: it will eventually be forgotten, and the timing is unpredictable.
Translate