CustodyStress
Archive › Browse by trigger and custody type › Forgotten Passphrase — Software wallet
Part of the CustodyStress archive of observed Bitcoin custody incidents
Forgotten_passphraseSoftware wallet

Forgotten Passphrase — Software wallet

Cases where a mobile wallet passphrase was forgotten. This is the highest-count trigger×custody combination involving self-custody — forgotten passphrases on mobile wallets are the most documented single failure in the archive.

77 cases in this intersection. 32% of determinate cases resulted in a blocked outcome and 56% in access survived. The most common recovery path is password bruteforce.

8
Blocked
3
Constrained
14
Survived
52
Indeterminate

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

77 observed cases
Blocked
8 (10%)
Constrained
3 (4%)
Survived
14 (18%)
Indeterminate
52 (68%)
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
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
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
Encrypted Bitcoin Core Wallet Loss: Forgotten Passphrase, Selective Key Export Failure
Software wallet
Blocked 2015
In October 2015, forum user phantitox reported recovering a wallet.dat file from a damaged hard drive, only to discover the passphrase protecting the encrypted
Forgotten Bitcoin Core Passphrase: Third-Party Recovery Service Success — Community Skepticism
Software wallet
Constrained 2015
In July 2015, a BitcoinTalk user (bassride2) discovered that while they had meticulously backed up their Bitcoin Core wallet.dat file multiple times, they had f
Electrum Wallet Password Loss Without Seed Phrase Backup
Software wallet
Indeterminate 2015
In November 2015, a BitcoinTalk user created a password-protected Electrum software wallet for testing purposes and set a password they believed followed the pa
Forgotten Passphrase and Overwritten Wallet.dat: 0.50 BTC Permanently Lost
Software wallet
Blocked 2015
In May 2015, BitcoinTalk user grovearmada discovered they had lost access to an encrypted Bitcoin wallet containing 0.50 BTC (approximately $115–120 USD at 2015
Forgotten Passphrase: 3.3 BTC Recovered by Third-Party Service for 20% Fee
Software wallet
Constrained 2014
In June 2014, a BitcoinTalk user identified as marsje007 discovered they could no longer access a wallet containing 3.3 BTC after changing the passphrase and fa
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
Forgotten Encryption Passphrase Blocks Access to 10+ BTC in Bitcoin Core Wallet
Software wallet
Indeterminate 2014
In December 2014, a BitcoinTalk user identifying as casperround publicly sought help recovering access to an encrypted Bitcoin Core wallet containing over 10 BT
Passphrase unavailable — Bitcoin-Qt (2013)
Software wallet
Indeterminate 2013
In November 2013, BitcoinTalk user eric89 reported a custody failure involving a Litecoin wallet mined in April 2013. The user had encrypted the wallet using Li
Passphrase unavailable — software wallet (2013)
Software wallet
Indeterminate 2013
On February 5, 2014, BitcoinTalk user repukken posted in the encrypted wallet recovery thread seeking help to brute-force access to a Dogecoin wallet after forg
Dogecoin Wallet Passphrase Mismatch: 50,000 DOGE Inaccessible Despite Documentation
Software wallet
Indeterminate 2013
On December 27, 2013, a BitcoinTalk user named Alohaboy posted seeking help recovering access to a Dogecoin wallet. The user had documented their passphrase ('d
13.8 BTC Lost to Forgotten Wallet.dat Password: DIY and Professional Recovery Attempts
Software wallet
Indeterminate 2013
A Bitcoin user created an encrypted Bitcoin Core wallet in 2013 containing 13.8 BTC. The passphrase was forgotten, rendering the wallet inaccessible. In Septemb
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
Noitev's Lost Electrum Password: 1.8–1.9 BTC Recovered via Brute-Force Attack
Software wallet
Constrained 2013
On April 8, 2013, BitcoinTalk user Noitev reported losing access to an Electrum wallet holding approximately 1.8–1.9 BTC due to a forgotten password. The wallet
BitcoinTalk User RTQ1154 Locks 78 BTC Behind Mistyped Wallet Password
Software wallet
Indeterminate 2013
In June 2013, a BitcoinTalk forum user identifying as RTQ1154 posted in a community thread titled 'Let's add up the KNOWN lost bitcoins' describing a custody lo
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
Passphrase unavailable — Bitcoin-Qt (2013)
Software wallet
Indeterminate 2013
In April 2013, a BitcoinTalk user identified as 'veryveryinteresting' posted in topic 85495, the community's primary encrypted wallet recovery thread, describin
BitcoinTalk User 'Liquid': 30 BTC Inaccessible Due to Forgotten Bitcoin-Qt Encryption Password
Software wallet
Indeterminate 2013
In June 2013, a BitcoinTalk forum user operating under the handle 'Liquid' posted in the encrypted wallet recovery thread (topic 85495) describing an inaccessib
Hidden wallet discovered — Bitcoin-Qt (2013)
Software wallet
Indeterminate 2013
In November 2013, BitcoinTalk user nobbie discovered that Bitcoin-Qt's wallet encryption feature had been activated, locking access to the wallet with a passwor
Passphrase unavailable — Bitcoin-Qt (2013)
Software wallet
Indeterminate 2013
In April 2013, a BitcoinTalk user identified as 'legitnick' posted in topic 85495, the primary community support thread for locked wallet recovery during the 20
← PreviousNext →
Browse by trigger and custody type
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