CustodyStress
Archive › Browse by trigger and outcome › Forgotten Passphrase — Survived
Part of the CustodyStress archive of observed Bitcoin custody incidents
Forgotten_passphraseSurvives

Forgotten Passphrase — Survived

Cases where a forgotten passphrase was overcome and access was recovered. These cases document the conditions that made recovery possible — partial passphrase recall, documented backup, or successful bruteforce.

17 cases in this intersection. 0% of determinate cases resulted in a blocked outcome and 100% in access survived. The most common recovery path is password bruteforce.

Archive analysis — 17 cases
Outcomes
0% of determinate cases resulted in blocked access — 69 percentage points below the archive-wide average of 69%. 100% resulted in recovered access — above the archive average.
Custody type
82% of cases involved software wallet, followed by hardware wallet with passphrase at 6%.
Primary stress condition
94% of cases involve passphrase unavailable. Documentation absent accounts for a further 6%.
Recovery path
Password Bruteforce is the most documented recovery path (12 cases, 71% of subset). Of those with a determinate outcome, 100% resulted in recovered or constrained access.
Documentation
47% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Time distribution
Cases span 2009–2019. Only 0% occurred in 2022 or later — concentrated in earlier periods.
0
Blocked
0
Constrained
17
Survived
0
Indeterminate

0% of determinate cases resulted in blocked or constrained access.

17 observed cases
Survived
17 (100%)
Forgotten 115-Character Wallet Password Recovered via GPU Typo-Bruteforce
Software wallet
Survived 2019
In August 2017, a Bitcoin enthusiast created a Bitcoin Core wallet secured by a 115-character sentence-based password and wrote it down. In June 2019, when they
Electrum Seed Version 18 Password Recovery: btcrecover Incompatibility Resolved
Software wallet
Survived 2019
In December 2019, a BitcoinTalk user (red14159) discovered a wallet.dat file from an Electrum wallet they had lost access to approximately three years earlier.
MultiBit Classic Password Lock: Recovery Through Backup Key File Import
Software wallet
Survived 2018
A BitcoinTalk user (cluuze130) deposited Bitcoin into MultiBit Classic approximately one year before attempting withdrawal in February 2018. At the time of depo
Forgotten Bata Wallet Passphrase Recovered by Professional Service
Software wallet
Survived 2017
On August 1, 2017, a BitcoinTalk user operating under the handle InvestMeDaddy posted a recovery request after losing access to a Bata desktop cryptocurrency wa
Trezor PIN and Seed Words Forgotten: $30,000 Bitcoin Recovery
Hardware wallet (single key)
Survived 2017
In October 2017, a Trezor hardware wallet user discovered they had forgotten both their PIN and recovery seed words, creating a dual-layer access barrier to app
22.1 BTC Bitcoin-Qt Wallet Password Recovery via Community Brute Force (2014)
Software wallet
Survived 2014
In November 2014, a Bitcoin-Qt wallet containing 22.1 BTC became inaccessible when its owner forgot the passphrase. The owner had documented the password creati
Kristoffer Koch Recovers Forgotten 5,000 BTC Wallet After Four Years
Software wallet
Survived 2013
In 2009, Kristoffer Koch, a Norwegian engineering student, purchased 5,000 Bitcoin for approximately 150 Norwegian kroner (roughly $27 USD at the time) as resea
Bomben Recovers 2013 Bitcoin Wallet Locked by Nonstandard Private Key Encoding
Software wallet
Survived 2013
Bomben created a Bitcoin wallet in 2013 using software that implemented a nonstandard encoding for private keys, diverging from the Wallet Import Format (WIF) s
Forgotten Passphrase Locks Desktop Wallet for 8 Years; btcrecover Enables Recovery
Software wallet
Survived 2013
In 2013, this individual created a Bitcoin wallet using desktop software, securing it with a passphrase. The holder subsequently lost memory of that passphrase
Blockchain.info Hosted Wallet Recovery: Password Reset via Seed Phrase (2013)
Exchange custody
Survived 2013
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 i
BitcoinTalk User kentt Recovers Encrypted Wallet via Community Brute-Force Script (June 2013)
Software wallet
Survived 2013
In June 2013, BitcoinTalk user kentt posted confirmation of a successful wallet recovery using community-developed brute-force scripts circulated in topic 85495
Kristoffer Koch Recovers 5000 BTC After Forgotten Wallet Password — 2013
Software wallet
Survived 2009
Kristoffer Koch, a Norwegian engineering student, encountered Bitcoin in late 2009 while researching encryption for his university thesis. Intrigued by the emer
Forgotten Bitcoin Wallet Passphrases: Forum Cases of Successful Third-Party Recovery (2014–2021)
Software wallet
Survived
Between 2014 and 2021, seven Bitcoin holders posted testimonials on a forum documenting their recovery of wallets encrypted with forgotten passphrases. Cases ra
Passphrase Recovery Success and OPSEC Failure: 2014 WalletRecoveryServices Case
Software wallet
Survived
A Bitcoin holder in 2014 created private keys but lost the passphrase required to access them. The funds remained locked for an unknown duration until the owner
BIP38 Paper Wallet: Seven-Year Inaccessibility Resolved via Single-Character Error
Software wallet
Survived
In 2017, an individual encrypted a paper wallet using BIP38 encryption, protecting it with a passphrase derived from their favorite band—a mnemonic they believe
IronKey Password Recovery: Developer Regains Access to $240M Bitcoin
Hardware wallet with passphrase
Survived
In the early 2010s, a software developer stored Bitcoin on an IronKey encrypted USB drive, securing it with a passphrase generated by RoboForm password manager.
170 BTC Passphrase Lockout: Year-Long Inaccessibility Resolved by Memory Recovery
Software wallet
Survived
In early 2011, an investor acquired approximately 170 BTC at roughly $10 per coin, storing the funds in Bitcoin-Qt, the primary self-custody software wallet ava
Browse by trigger and outcome
Terms guide
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.
Survivability
The degree to which a custody system maintains the possibility of authorized recovery under stress.
Archive inclusion criteria

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?

A case must satisfy all three of the following to be included:

  1. 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.
  2. 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.
  3. 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.
  • 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
  • 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

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.

Original text
Rate this translation
Your feedback will be used to help improve Google Translate