CustodyStress
Archive › Browse by dependency and custody › Passphrase Dependency — Hardware wallet with passphrase
Part of the CustodyStress archive of observed Bitcoin custody incidents
Passphrase DependencyHardware wallet with passphrase

Passphrase Dependency — Hardware wallet with passphrase

Cases where the defining feature of the custody setup — the hardware wallet passphrase — became the point of failure. The passphrase was set but not recorded in a way that survived the holder's unavailability.

100% of all Hardware wallet with passphrase cases in the archive involve this structural dependency. The blocked rate among them is 58% — 11 points below the archive-wide blocked rate of 69%. The most common recovery path is password bruteforce.

Archive analysis — 18 cases
Outcomes
58% of determinate cases resulted in blocked access — 11 percentage points below the archive-wide average of 69%. 42% resulted in recovered access — above the archive average.
Documentation coverage
33% of cases have indeterminate outcomes — higher than the archive average of 43%.
Primary stress condition
78% of cases involve passphrase unavailable. Vendor lockout accounts for a further 6%.
Recovery path
Password Bruteforce is the most documented recovery path (6 cases, 33% of subset).
Documentation
78% of cases had partial documentation — insufficient to complete recovery without the holder's direct involvement.
Time distribution
Cases span 2017–2025. 33% occurred in 2022 or later.
7
Blocked
0
Constrained
5
Survived
6
Indeterminate

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

18 observed cases
Blocked
7 (39%)
Survived
5 (28%)
Indeterminate
6 (33%)
Trezor Model T Passphrase Loss: 0.7175 BTC On-Chain, Inaccessible
Hardware wallet with passphrase
Blocked 2025
In late December 2025, jwsutherland transferred approximately 0.7175 BTC from the Canadian exchange Newton to a native SegWit (bech32) address generated by a Tr
Trezor Passphrase Forgotten After Factory Reset — Successful Recovery via Community Support
Hardware wallet with passphrase
Survived 2024
BTCRSMD, a moderately experienced Bitcoin user, executed a deliberate custody strategy in July 2024. The user purchased Bitcoin via Swan and routed the coins th
Coldlar Pro3 Hardware Wallet: Valid Seed Phrase Insufficient Without Payment Password
Hardware wallet with passphrase
Blocked 2023
On December 4, 2023, a Bitcoin user identified as zzzccc posted to BitcoinTalk describing a critical custody access failure involving a Coldlar Pro3 hardware wa
Ledger Hardware Wallet: 1.7 BTC Inaccessible After Device Transition and Address Type Mismatch
Hardware wallet with passphrase
Indeterminate 2023
In December 2023, a BitcoinTalk user reported approximately 1.7 BTC held on a Ledger hardware wallet became inaccessible following a device upgrade. The Bitcoin
Forgotten Ledger Nano S Passphrase: Seed Phrase Retained but Inaccessible
Hardware wallet with passphrase
Indeterminate 2023
In March 2023, a forum user identified as despo4helpo posted to a Bitcoin technical support community seeking recovery advice for Bitcoin held on a Ledger Nano
Splashboard Trezor Passphrase Recovery: Third-Party Assisted Access Restoration
Hardware wallet with passphrase
Survived 2022
Splashboard, a Bitcoin holder with minimal public forum presence, purchased a Trezor hardware wallet in late 2021 and performed initial setup. During the setup
Forgotten Hardware Wallet Passphrase: Recovery via Address Database Search
Hardware wallet with passphrase
Indeterminate 2021
In March 2021, a BitcoinTalk user identified as 'wojakboy' initiated a forum thread reporting loss of access to Bitcoin held in a hardware wallet's passphrase-p
Ledger Nano S: 23 of 24 Mnemonic Words with Passphrase, Missing Final Word
Hardware wallet with passphrase
Indeterminate 2018
In May 2018, a Ledger Nano S user accidentally wiped their device during testing and discovered they had retained 23 of 24 seed words, written down in order, pl
Armed Kidnapping for Hardware Wallet Access: $1.8M Ether Theft — New York 2017
Hardware wallet with passphrase
Survived 2017
On November 4, 2017, Louis Meza, 35, of Jersey City, New Jersey, orchestrated a sophisticated attack against a personal acquaintance in New York City. Meza arra
7500 BTC Permanently Locked on IronKey Device After Passphrase Loss
Hardware wallet with passphrase
Blocked
A British engineer encrypted approximately 7500 BTC on an IronKey device, a third-party encrypted storage solution designed with progressive lockout mechanisms
Stefan Thomas: 7,200 Bitcoin Inaccessible Behind IronKey Passphrase
Hardware wallet with passphrase
Blocked
Stefan Thomas, former Chief Technology Officer of Ripple, stored 7,200 BTC on an IronKey encrypted hard drive. The drive implemented a deliberate security const
Lost Passphrase to Ledger BIP39 Hidden Wallet—Seed Phrase Insufficient
Hardware wallet with passphrase
Indeterminate
A Bitcoin holder with existing experience in cryptocurrency set up an advanced feature on their Ledger hardware wallet known as BIP39 passphrase protection. Thi
4 BTC Lost Behind Forgotten Passphrase After Ledger PIN Lockout
Hardware wallet with passphrase
Survived
The user maintained a Ledger Nano S hardware wallet configured with two separate accounts: a primary account secured by a 24-word BIP39 seed phrase stored in co
Stefan Thomas: 7,002 Bitcoin on IronKey S200, Passphrase Lost, 2 Attempts Remaining
Hardware wallet with passphrase
Blocked
Stefan Thomas possessed an IronKey S200 USB drive containing the private keys to 7,002 Bitcoin, worth approximately $235 million at the time of public reporting
Developer Locked Out of $240 Million Bitcoin After Forgetting Hardware Wallet Passphrase
Hardware wallet with passphrase
Blocked
A cryptocurrency developer became unable to access approximately $240 million in Bitcoin stored on a hardware wallet after forgetting the device's passphrase. T
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.
Stefan Thomas: 7,002 Bitcoin Inaccessible on IronKey With 2 Password Attempts Remaining
Hardware wallet with passphrase
Blocked
Stefan Thomas, a German-born software developer based in San Francisco, accumulated 7,002 Bitcoin over years of work in the technology sector. In the early-to-m
Trezor Hardware Wallet: Passphrase Forgotten, Recovery Seed Insufficient
Hardware wallet with passphrase
Indeterminate
A Bitcoin holder configured a Trezor hardware wallet using both a 24-word recovery seed and an optional passphrase feature for additional security. When returni
Browse by dependency and custody
Related pages
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