CustodyStress
Archive › More United States cases › United States — Hardware wallet (single key)
Part of the CustodyStress archive of observed Bitcoin custody incidents
United StatesHardware wallet (single key)

United States — Hardware wallet (single key)

Cases from the United States involving single-key hardware wallet failures. US hardware wallet cases are concentrated around coercion and passphrase-related failures.

50% of determinate cases in this country with this custody type resulted in a blocked outcome — 14 points below the global rate of 64% for this custody type. This country accounts for 14% of all archive cases with this custody type. The most common recovery path is coerced transfer.

Archive analysis — 10 cases
Outcomes
50% of determinate cases resulted in blocked access — 19 percentage points below the archive-wide average of 69%. 38% resulted in recovered access — above the archive average.
Primary stress condition
40% of cases involve coercion. Seed phrase unavailable accounts for a further 30%.
Recovery path
Coerced Transfer is the most documented recovery path (3 cases, 30% of subset).
Documentation
60% of cases had present and interpretable documentation — yet still produced a blocked or constrained outcome.
Scale
30% of cases involved large or very large holdings (10+ BTC).
Time distribution
Cases span 2017–2025. 40% occurred in 2022 or later.
10 observed cases
Blocked
4 (40%)
Constrained
1 (10%)
Survived
3 (30%)
Indeterminate
2 (20%)
San Francisco Home Invasion: $11M Cryptocurrency Stolen at Gunpoint
Hardware wallet (single key)
Blocked 2025
In November 2025, an armed robber entered a residential home in San Francisco by posing as a delivery worker. The attacker subdued the homeowner by tying them u
Kidnapping and Torture for Seed Phrase Extraction: Portland, Oregon 2023
Hardware wallet (single key)
Blocked 2023
In November 2023, a 21-year-old cryptocurrency holder in Portland, Oregon became the target of a coordinated abduction by four men who traveled from Florida wit
Florida Couple Kidnapped by Crypto-Targeting Gang — Hardware Wallet Retrieved Under Duress
Hardware wallet (single key)
Blocked 2022
In September 2022, Glenn and Julia Goodwin, a retired couple in Delray Beach, Florida, were awakened shortly before midnight by intruders breaking through their
Little Elm, Texas Home Invasion: $1.4M Hardware Wallet Sought but Not Found
Hardware wallet (single key)
Survived 2022
In December 2022, armed home invaders broke into a residential property in Little Elm, Texas, and subjected the occupants to approximately three hours of tortur
Missing 2 of 12 Mnemonic Words: Brute Force Recovery Feasibility
Hardware wallet (single key)
Indeterminate 2020
In March 2020, a Bitcoin holder wrote their 12-word BIP39 mnemonic on paper. During storage or handling, the last two words were torn away and lost, leaving onl
Matthew Mellon's $193M XRP Estate: Cold Wallets, No Keys, No Plan
Hardware wallet (single key)
Constrained 2018
Matthew Mellon, a member of the prominent Mellon banking family, became a significant cryptocurrency investor in the mid-2010s. His $2 million investment in XRP
Mark Frauenfelder's 7.4 BTC: Seed Phrase Discarded by Housecleaner, Recovered via Hardware Vulnerability
Hardware wallet (single key)
Survived 2017
Mark Frauenfelder, editor-in-chief of Boing Boing and Wired contributor, purchased 7.4 Bitcoin in January 2016 for approximately $3,000 and transferred it to a
Ledger Nano S Lockout: Seed Phrase Transcription Error and Checksum Validation Failure
Hardware wallet (single key)
Indeterminate 2017
In December 2017, a Ledger Nano S user reported being locked out of their device after completing initial setup. During device initialization, the user received
Tax Conviction Forces $124M Bitcoin Disclosure Order, But Keys Remain Inaccessible
Hardware wallet (single key)
Blocked
Richard Ahlgren III, an early Bitcoin investor, was convicted of tax evasion for underreporting capital gains from cryptocurrency sales. A Texas federal court i
Mark Frauenfelder's 7 Bitcoin: Household Cleaner Discards Written Seed Phrase
Hardware wallet (single key)
Survived
Mark Frauenfelder, a US journalist, purchased approximately 7 Bitcoin in early 2016 at roughly $3,000 total investment. As the asset price appreciated significa
More United States cases
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