Forgotten Password on Blockchain.info: 0.22 BTC Access Lost, Brute-Force Recovery Attempted
IndeterminateWallet passphrase was unavailable — whether access was ultimately recovered is not known.
In October 2014, a BitcoinTalk forum user reported that their friend had become locked out of a blockchain.info wallet containing 0.22 BTC after forgetting the password and failing to maintain any backup. The friend possessed only the wallet identifier. Blockchain.info's architecture encrypted wallets client-side using the user's password; the platform itself could not decrypt or reset access, making password loss equivalent to permanent lockout without alternative recovery paths.
The original poster sought technical feasibility guidance on password recovery. Community members, including btchris (developer of the btcrecover tool), provided detailed instructions for extracting the encrypted wallet file (wallet.aes.json) from blockchain.info's servers and applying cryptographic attack tools. The approach involved exporting the wallet file, extracting the AES encryption hash using blockchain2john, and then applying brute-force techniques via John the Ripper or btcrecover with GPU acceleration (CUDA/OpenCL) to attempt password reconstruction.
The original poster successfully validated the toolchain on practice wallets with known simple passwords, reporting successful recovery within 30 seconds when password components were known. By October 9, 2014, findftp reported launching brute-force attacks on the friend's actual wallet.aes.json file using John the Ripper on a laptop. However, the thread provided no documentation of whether the recovery succeeded, was abandoned, or remained ongoing. The case illustrates the custody paradox of early web wallets: funds were held on a company's servers (creating institutional dependency) yet encrypted with a user-controlled password that no institution could recover, leaving only computational attack as a remedy for forgotten credentials.
| Stress condition | Passphrase unavailable |
| Custody system | Exchange custody |
| Outcome | Indeterminate |
| Documentation | Partial |
| Year observed | 2014 |
| 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