Part of the CustodyStress archive of observed Bitcoin custody incidents
CS-00092
Blockchain.info Hosted Wallet Recovery: Password Reset via Seed Phrase (2013)
Survived
Wallet passphrase was unavailable — a recovery path existed and access was restored.
What could have prevented this
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.
Test whether your setup has this gap →
Case description
PandaNL opened a Blockchain.info hosted wallet in 2013 and over several years forgot the account password. The user retained three critical pieces of recovery information: the wallet ID, a valid 12-word mnemonic seed phrase, and an encrypted wallet.aes.
json backup file. The email address associated with the account remained under the user's control. When attempting recovery through Blockchain.info's standard account recovery interface, the system presented a non-functional 'Check/continue' button that remained greyed out, blocking further progress.
Initial troubleshooting attempts within the community forum suggested importing the wallet.aes.json file to a new account, but this approach required the original password—creating a circular dependency. A critical breakthrough occurred when community member krishnapramod noted that wallets created in 2013 typically used 17–19 word recovery phrases rather than 12 words, prompting verification of the phrase length.
PandaNL confirmed possession of a legitimate 12-word phrase. This clarification led to discovery of Blockchain.info's dedicated forgot-password recovery tool at https://blockchain.info/wallet/forgot-password.
Using this specialized tool with the correct seed phrase, PandaNL successfully recovered the account password and regained full wallet access by June 28, 2017—approximately four years after initial password loss. The case illustrates both the vulnerability of password-dependent hosted wallet access and the recovery pathway available when seed phrase backup exists. A secondary user (Superzpay) in the same thread faced identical circumstances but remained unresolved within visible documentation. No specific Bitcoin amount, USD value, or final asset disposition is recorded.
Custody context
| Stress condition | Passphrase unavailable |
| Custody system | Exchange custody |
| Outcome | Survived |
| Documentation | Present and interpretable |
| Year observed | 2013 |
| Country | unknown |
Structural dependencies observed
Human context
Owner-only operational knowledge
Why this matters
Why passphrases fail years after they are set
A passphrase adds a second layer of security to a Bitcoin wallet: the seed phrase opens one wallet; the seed phrase plus the passphrase opens a different one. This structure is effective at protecting against seed phrase theft. It is poorly designed for long-term memory reliability.
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.
How this category of failure is typically preventable
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.
Read more: How Passphrase Delay Failures Occur →
Frequently asked questions
Can a forgotten Bitcoin wallet passphrase be recovered?
In most cases, no. A wallet passphrase is not stored on the device, the network, or any recoverable system. It exists only in the holder's memory. If forgotten, there is no reset mechanism and no institution that can retrieve it. Some professional recovery services attempt passphrase variations for holders who remember partial information — but this is only feasible if the original passphrase had a recognizable pattern.
Is a Bitcoin passphrase the same as the seed phrase?
No. A passphrase is an additional secret layered on top of the seed phrase. The seed phrase alone generates one wallet; the seed phrase plus a specific passphrase generates a different wallet. Both are required for access. Losing the passphrase while retaining the seed phrase still blocks access — the seed alone will open an empty wallet, not the funded one.
Why do Bitcoin passphrases get forgotten even when the owner remembers setting one?
Passphrases are often set once during wallet setup and then not used again for months or years. Memory of infrequently used information degrades over time, and even small deviations — different capitalization, added space, slightly different word order — produce a completely different wallet with a zero balance. The holder may recall setting a passphrase clearly while being unable to reproduce the exact characters required.
Most structurally similar case
2013 Blockchain.info AES-Encrypted Wallet: Password Lost, Recovery Tooling Exhausted
Passphrase unavailable
·
Exchange custody
· 2013
Indeterminate
Related cases
This archive documents observed custody survivability failures. It does not attempt to document all Bitcoin losses or security incidents.
Submit a case
A passphrase introduces a dependency that may not persist over time. The CustodyStress assessment evaluates whether a recovery path exists without it.
Start Bitcoin Custody Stress Test
$149 · 12-month access · Unlimited assessments
A 30-minute assessment that models how your Bitcoin custody setup behaves when assumptions fail, with reference documents others can read without your help.
View example profile documents
Outcome terms
Survived
Access remained possible under the reported conditions.
Constrained
Access remained possible, but only with delay, dependence, or significant difficulty.
Blocked
Access was not possible under the reported conditions.
Indeterminate
There was not enough information to determine the outcome.
Assessment terms
Survivability
The degree to which a custody system maintains the possibility of authorized recovery under stress.
This archive documents cases where a legitimate owner, heir, or authorized party encountered barriers accessing or recovering Bitcoin due to a failure in the custody arrangement. The central question for inclusion is: did the custody structure fail a legitimate access or recovery attempt?
Inclusion requirements
A case must satisfy all three of the following to be included:
- Legitimate access attempt. The person attempting to access or recover the Bitcoin was the owner, a designated heir, an executor, a legal authority, or another party with a legitimate claim — not a thief, attacker, or unauthorized third party.
- Custody structure failure. The failure was caused by a property of the custody arrangement — missing credentials, structural dependencies, documentation gaps, knowledge concentration, legal barriers, or institutional constraints — not market conditions, individual-level fraud or theft, or protocol-level issues. Platform-level failures that block legitimate user access are in scope regardless of their cause.
- Documentable outcome or access constraint. The case must have a stated or inferable outcome: access blocked, access constrained, access delayed, or access eventually achieved through a recovery path. Cases with entirely unknown outcomes are included only where the structural failure is documented and the constraint is unambiguous.
In scope
- Owner death or incapacity — Bitcoin held in self-custody that becomes inaccessible to heirs or designated parties because credentials, documentation, or operational knowledge were not transferred
- Passphrase loss — BIP39 passphrase forgotten or unavailable, blocking access to a funded wallet even where the seed phrase is present
- Seed phrase or wallet backup unavailable — no independent recovery path existed or the backup was destroyed, lost, or never created
- Device loss without independent backup — hardware wallet, phone, or computer lost or destroyed with no recovery path outside the device
- Documentation absent or ambiguous — heirs or executors cannot determine that Bitcoin exists, which wallet holds it, or how to access it
- Knowledge concentration — only one person knew the procedure, passphrase, or access method; that person is dead, incapacitated, or unreachable
- Multisig quorum failure — a threshold signature arrangement cannot be completed because signers are unavailable, uncooperative, incapacitated, or have lost their keys
- Legal authority / access mismatch — a court order, probate ruling, or power of attorney establishes legal entitlement but provides no technical path to access
- Institutional custody barrier — exchange or platform hacks, insolvency, regulatory seizure, or operational failure that caused a access constraint or failure for legitimate users, whether temporary, prolonged, or permanent. The failure of the custodian to remain available or solvent is itself the in-scope event.
- Forced relocation or geographic constraint — physical access to a device or location required for recovery is blocked by displacement, border restrictions, or political circumstances
- Coercion — the holder was compelled under threat to transfer Bitcoin or disclose credentials during an access event
- Hidden asset discovery — heirs or executors locate a wallet or account but cannot access it due to missing credentials or operational knowledge
Out of scope
- Market losses, investment losses, yield scheme losses, or Ponzi scheme losses
- Hacks or theft targeting an individual's personal security (phishing, SIM swap, social engineering, malware) where the custody architecture itself did not fail
- Unauthorized transfers where the holder's custody system was not the cause of the failure
- Ordinary transaction mistakes — wrong-address sends, fee errors, mistaken amounts
- Protocol-level failures — cryptographic vulnerabilities, consensus bugs, firmware integrity failures
- Deliberate burns or tribute burns
- Cases where the stated loss is unverifiable and no structural custody failure is described
Source and verification
Cases are drawn from public sources including forum posts, news reporting, court documents, academic research, and direct submissions. Each case is reviewed against the inclusion criteria above before publication. Source material is retained and available on request for documented cases.
The archive is observational and descriptive. It does not attempt to document all Bitcoin custody failures — only those meeting the criteria above with sufficient documentation to describe the structural failure and its outcome.
Translate