CustodyStress
Archive › Browse by country › Australia
Part of the CustodyStress archive of observed Bitcoin custody incidents

Australia

Bitcoin custody incidents documented in Australia. Cases reflect a mix of exchange failures and self-custody losses consistent with the broader archive pattern.

9 cases from Australia are included in this archive. 63% of determinate cases resulted in a blocked outcome. The most frequently observed stress condition is vendor-lockout cases.

Archive analysis — 9 cases
Outcomes
63% of determinate cases resulted in blocked access — 6 percentage points below the archive-wide average of 69%. 38% resulted in constrained recovery.
Custody type
67% of cases involved exchange custody, followed by software wallet at 22%.
Primary stress condition
67% of cases involve vendor lockout. Device loss accounts for a further 22%.
Recovery path
Exchange Support is the most documented recovery path (2 cases, 22% of subset).
Structural dependency
67% of cases carry a institutional cooperation required dependency tag — the most common structural factor in this subset.
9 observed cases
Blocked
5 (56%)
Constrained
3 (33%)
Indeterminate
1 (11%)
Peter Vuong Kidnapping: Physical Coercion and Ransom Demand, Sydney 2023
Unknown custody system
Blocked 2023
In March 2023, Peter Vuong was abducted in Sydney by an organised crime group and held for six days while the gang tortured him and demanded $5 million in ranso
Institutional lockout — exchange custody, Australia (2015)
Exchange custody
Blocked 2015
igot, an Australian-branded Bitcoin exchange later traced to operational infrastructure in India, faced a significant customer crisis in May 2015 when users rep
Digital CC v. igot Exchange: $180,000 Bitcoin Claim, Australian Court Action
Exchange custody
Indeterminate 2015
Digital CC, an Australian digital currency company, accumulated approximately $180,000 in Bitcoin holdings or claims held on the igot exchange. Beginning in 201
Institutional lockout — exchange custody, Australia (2015)
Exchange custody
Constrained 2015
igot, an Australian Bitcoin exchange operated by Remi Fabre under the digital.cc domain, entered a state of operational dysfunction beginning in August 2015. Us
Institutional lockout — exchange custody, Australia (2015)
Exchange custody
Constrained 2015
In August 2015, the Australian Bitcoin exchange igot ceased all operations and communications, leaving customers unable to access their holdings or funds. Reddi
Australian Miner Loses Early Bitcoin When Sole USB Backup Drive Fails Irrecoverably
Software wallet
Blocked 2013
Alex, an Australian Bitcoin miner based in Melbourne, mined Bitcoin around 2010 when mining was still a hobbyist activity with negligible monetary value. Unlike
Inputs.io Hack: 4,100 BTC Stolen, Partial Refunds October 2013
Exchange custody
Constrained 2013
Inputs.io was an Australian-hosted Bitcoin wallet service operated by a developer known as TradeFortress. On October 23, 2013, the platform suffered a security
CryptoXChange Exchange Collapse: Users Locked Out of Bitcoin Deposits
Exchange custody
Blocked 2012
CryptoXChange launched on November 10, 2011, as an Australian Bitcoin exchange offering two-factor authentication features including Yubikey support. The platfo
Campbell Simpson Discards 1,400 BTC on Failing Hard Drive Without Backup
Software wallet
Blocked 2012
Campbell Simpson, editor of Gizmodo Australia, purchased approximately 1,400 Bitcoin in early 2010 when a single coin traded for roughly 1.5 cents, investing ar
Browse by country
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