CustodyStress
Archive › Browse by trigger and era › Forgotten Passphrase — Exchange Era (2014–2019)
Part of the CustodyStress archive of observed Bitcoin custody incidents
Forgotten_passphraseExchange Era

Forgotten Passphrase — Exchange Era (2014–2019)

Forgotten passphrase cases from the Exchange Era (2014–2019). Hardware wallet adoption during this period created a new cohort of BIP39 passphrase failures.

39 cases in this intersection. 38% of determinate cases resulted in a blocked outcome and 46% in access survived. The most common recovery path is password bruteforce.

Archive analysis — 39 cases
Outcomes
38% of determinate cases resulted in blocked access — 31 percentage points below the archive-wide average of 69%. 46% resulted in recovered access — above the archive average.
Documentation coverage
67% of cases have indeterminate outcomes — higher than the archive average of 43%.
Custody type
62% of cases involved software wallet, followed by exchange custody at 36%.
Primary stress condition
90% of cases involve passphrase unavailable. Vendor lockout accounts for a further 8%.
Recovery path
Password Bruteforce is the most documented recovery path (16 cases, 41% of subset). Of those with a determinate outcome, 100% resulted in recovered or constrained access.
Documentation
74% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
5
Blocked
2
Constrained
6
Survived
26
Indeterminate

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

39 observed cases
Blocked
5 (13%)
Constrained
2 (5%)
Survived
6 (15%)
Indeterminate
26 (67%)
Forgotten Password to 18.2 BTC Bitcoin Core Wallet (May 2014)
Software wallet
Indeterminate 2019
On December 13, 2019, a BitcoinTalk forum user (na4e41.02) posted in the Bitcoin Technical Support section requesting assistance recovering a wallet.dat file en
Forgotten Wallet.dat Password: 13.8 BTC Inaccessible Since 2013
Software wallet
Indeterminate 2019
In September 2019, a BitcoinTalk forum user identified as lankymanx disclosed loss of access to a wallet.dat file created in 2013, containing 13.8 BTC. The wall
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
Mycelium Mobile Wallet PIN Lost — Bitcoin Inaccessible Despite Seed Phrase
Software wallet
Indeterminate 2019
A Mycelium mobile wallet user created a new wallet on an old Android device in 2019, securing it with a 6-digit PIN and recording the 12-word seed phrase on pap
Lost Electrum Wallet Password: wallet.dat File Encrypted, No Backup Credential
Software wallet
Indeterminate 2019
In February 2019, a forum user identified as bitbemining posted a custody failure case involving an Electrum wallet. The user possessed the encrypted wallet.dat
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.
Forgotten wallet.dat Password: 13.8 BTC Locked Since 2013
Software wallet
Indeterminate 2018
On 2 March 2018, a Bitcoin holder identified as fabriciofenenga posted to the Bitcoin Technical Support forum seeking password recovery assistance for a wallet.
131 BTC Inaccessible: Forgotten Wallet Password, No Recovery Mechanism
Software wallet
Indeterminate 2018
In December 2018, a BitcoinTalk user known as 'jackang' posted a public plea for help recovering access to a wallet containing 131 BTC. The wallet had been crea
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
BitcoinTalk User: Encrypted Wallet.dat Passphrase Lost, Recovery Deemed Infeasible
Software wallet
Indeterminate 2018
In January 2018, a BitcoinTalk forum user identified as moztec reported an access failure involving a wallet.dat file encrypted with Bitcoin Core. The user had
Encrypted Wallet, Forgotten Passphrase: Self-Custody Encryption Without Backup
Software wallet
Indeterminate 2018
On January 14, 2018, BitcoinTalk user AsJoshScreams posted a recovery plea for an encrypted cryptocurrency wallet. The user had encrypted their private key with
MultiBit 0.5.15 Forgotten Passphrase: Desktop Wallet Access Lost
Software wallet
Indeterminate 2017
On November 3, 2017, a pseudonymous BitcoinTalk forum user identified as 'dny18' posted a help request in the MultiBit archival section, stating they had forgot
Inherited Encrypted Bitcoin Wallet from 2012: Passphrase Lost After Parent's Death
Software wallet
Indeterminate 2017
Following his mother's death in late 2017, a BitcoinTalk user (umadbro) recovered hard drives from his parent's defunct desktop computer and discovered wallet.d
Dash Core Wallet Passphrase Forgotten: Permanent Access Loss
Software wallet
Blocked 2017
In April 2017, a BitcoinTalk forum user identified as 'Ramchandra' posted describing a custody failure involving a Dash Core software wallet. The user had encry
Blockchain.info Second Password Loss: Vendor Lockout Without Recovery Mechanism
Exchange custody
Indeterminate 2017
In January 2017, forum user ericblogs reported inability to execute transactions on a Blockchain.info hosted wallet after forgetting the account's second passwo
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
David Vu's Blockchain.info Wallet: Trapped With 2 BTC, Secondary Password Forgotten
Exchange custody
Indeterminate 2017
David Vu discovered a critical access failure in June 2017 when he attempted to withdraw Bitcoin from his Blockchain.info wallet. He retained access to his prim
Blockchain.info Hosted Wallet Recovery Attempt: Partial Password, No Seed Backup
Exchange custody
Indeterminate 2017
In October 2017, a BitcoinTalk user identified as Parodium reported being locked out of a blockchain.info wallet created years earlier. The user retained email
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
Lost Electrum Wallet Password (2 BTC) – No Recovery Path Identified
Software wallet
Indeterminate 2016
In September 2016, a BitcoinTalk forum user with username Ashkaan posted a public bounty request seeking professional assistance to recover access to an Electru
Encrypted Wallet Recovery Without Passphrase: pywallet's Hard Limit
Software wallet
Indeterminate 2016
In April 2016, BitcoinTalk user sparkybtc posted about recovering cryptocurrency from a formatted hard drive containing Bitcoin CPU-mined around 2011 and Dogeco
Blockchain.info Wallet Password Loss: No Recovery Options — February 2016
Exchange custody
Indeterminate 2016
In February 2016, a BitcoinTalk user posted on behalf of a friend who had lost the password to a Blockchain.info hosted wallet. The friend retained only an iden
Blockchain.com Wallet (2016): Partial Password Recovery Attempt, Seed Phrase Absent
Exchange custody
Blocked 2016
The subject created a Blockchain.com account in 2016 and deposited approximately 0.03 BTC (valued at roughly $20 at 2016 exchange rates of $600/BTC). Immediatel
Online Wallet Password Lost Without Seed Phrase Backup
Exchange custody
Indeterminate 2016
In November 2017, a BitcoinTalk user (mattmaxx) discovered they had lost access to an online Bitcoin wallet created approximately one year earlier on a laptop t
Blockchain.info Double Encryption Password Lost: Unrecoverable Without Key
Exchange custody
Indeterminate 2015
In February 2015, a BitcoinTalk user identified as ltcgearscammed posted seeking help after losing access to Bitcoin stored in a Blockchain.info wallet secured
← PreviousNext →
Browse by trigger and era
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