CustodyStress
Archive › Browse by trigger and stress condition › Physical Coercion — Coercion
Part of the CustodyStress archive of observed Bitcoin custody incidents
Physical_coercionCoercion

Physical Coercion — Coercion

Cases where physical coercion was both the documented trigger and the stress condition category. These cases represent the core coercion pattern — an attacker using force or threat of force against a Bitcoin holder.

109 cases in this intersection. 80% of determinate cases resulted in a blocked outcome and 18% in access survived. The most common recovery path is coerced transfer.

74
Blocked
1
Constrained
17
Survived
17
Indeterminate

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

109 observed cases
Blocked
74 (68%)
Constrained
1 (1%)
Survived
17 (16%)
Indeterminate
17 (16%)
Three Indian Cryptocurrency Traders Tortured for 80 BTC Ransom
Unknown custody system
Blocked 2019
In June 2019, three cryptocurrency traders—Luftan Shaikh, Mohammad Shazad, and Malang Shah—were abducted by a criminal gang in Jaipur, Rajasthan, India. The per
Masked Raiders Rob Bitcoin Exchange in Sparkhill, Birmingham (July 2019)
Exchange custody
Blocked 2019
In July 2019, a group of masked raiders conducted an armed robbery of a Bitcoin exchange located in the Sparkhill area of Birmingham, England. The incident occu
Oslo Bitcoin Millionaire's Escape From Armed Home Invader (2019)
Hardware wallet (single key)
Survived 2019
In May 2019, a Bitcoin millionaire residing in Oslo, Norway became the target of an armed home invasion. The attacker confronted the victim at his apartment, bu
Danny Aston Home Invasion: UK's First Documented Crypto-Targeted Physical Attack — 2018
Unknown custody system
Indeterminate 2018
On an unspecified date in 2018, four armed men invaded the Moulsford, Oxfordshire residence of cryptocurrency trader Danny Aston. The assault was motivated by a
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
Brazilian Bitcoin Miner's Wife Kidnapped for Ransom — 2017 Florianopolis Case
Unknown custody system
Indeterminate 2017
In 2017, a Brazilian Bitcoin miner based in Florianopolis became the subject of local media profiles highlighting his cryptocurrency fortune accumulated through
Ryan Piercy Kidnapped in Costa Rica — First Widely Reported Bitcoin Ransom Demand
Unknown custody system
Indeterminate 2015
On January 20, 2015, Ryan Piercy, a Canadian national residing in San José, Costa Rica, was abducted by kidnappers who made an unprecedented demand: $500,000 in
South African Investor Tortured and Coerced Into Cryptocurrency Transfer
Hardware wallet (single key)
Blocked
A South African investor holding approximately 100,000 in cryptocurrency in self-custody became the target of a violent attack. The attacker employed torture an
British Columbia Home Invasion: $1.6M Bitcoin Forced Transfer Under Duress
Hardware wallet (single key)
Blocked
In British Columbia, a couple fell victim to a targeted home invasion in which three attackers entered their residence and subjected them to a 13-hour ordeal. D
← Previous
1345
Next →
Browse by trigger and stress condition
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