Yapizon Exchange Hack (April 2017): 3,831 BTC Stolen, Socialised Loss Model Applied to All Users
BlockedCustodial platform became inaccessible — the holder had no independent key control.
On April 22, 2017, Yapizon, a South Korean cryptocurrency exchange, suffered a security breach resulting in the theft of 3,831 BTC—approximately 37% of the exchange's total holdings, valued at approximately $4.85 million at the time. Rather than absorbing the loss or seeking bankruptcy protection, Yapizon adopted a controversial loss-socialisation model previously employed by Bitfinex following its 2016 hack. Under this approach, the exchange reduced every user account balance proportionally, distributing the loss uniformly across all account holders regardless of whether their specific coins had been compromised.
This meant that users who had taken no role in the security failure nonetheless bore a material financial loss. In an effort to restore customer confidence and distance itself from the breach, Yapizon rebranded as YouBit. The rebranding strategy failed to prevent or mitigate systemic custody weaknesses. In December 2017, less than nine months later, YouBit suffered a second major hack resulting in the loss of approximately 17% of its remaining assets.
This second breach prompted the company to file for bankruptcy. The cumulative effect of both hacks and the socialised loss model left users of the Yapizon and YouBit platforms with significant, largely unrecoverable losses. The case demonstrates that even when an exchange avoids immediate closure, a socialised loss model still constitutes a material custody failure for users, as the platform's security controls proved inadequate and repeatedly failed to protect customer assets.
| Stress condition | Vendor lockout |
| Custody system | Exchange custody |
| Outcome | Blocked |
| Documentation | Present and interpretable |
| Year observed | 2017 |
| Country | South Korea |
Why custodial Bitcoin fails differently than self-custody
Exchange custody transfers the custody problem from the holder to the institution. The holder no longer needs to manage seed phrases, maintain hardware, or understand cryptographic concepts. They need only to maintain their account. This simplicity has a cost: the holder no longer controls the private keys. Access depends entirely on the continued operational, financial, and regulatory health of the exchange.
Cases in this archive show that exchange failures cluster around specific event types: bankruptcy and insolvency, regulatory seizure, geographic sanctions, and account-level access failures (lost 2FA, forgotten email credentials). Each event type has a different recovery path and a different timeline. Bankruptcy proceedings typically take 6-24 months and produce partial recovery. Regulatory seizure timelines depend on legal process. Account access failures may be resolvable through platform support or may not.
The distinguishing feature of vendor lockout cases is that recovery — when it occurs — happens through processes the holder did not design and cannot control. They become claimants in a process rather than holders of an asset.
The primary protection against vendor lockout is not using a vendor for custody beyond what is needed operationally. Holdings intended to be stored long-term are most exposed to institutional risk. Exchange custody is well-suited for active trading and conversion; it is poorly suited for long-term storage of significant value. Moving Bitcoin off exchange into self-custody eliminates platform dependency at the cost of taking on personal custody responsibility.