Looking back at 12 exchange incidents from 2014 to 2026 that have official statements or mainstream press coverage, outcomes fall into three groups. The platform absorbed the loss and users were untouched (Binance 2019, KuCoin 2020, Bybit 2025, Bitget 2026 and others). Users took a haircut first and were made up later (Bitfinex 2016 cut every account by about 36%; WazirX 2024 repaid about 85.5% up front). Or the exchange went into bankruptcy, claims were fixed in dollars, and people waited years (Mt. Gox, FTX). The size of the theft mattered less than whether the platform had enough of its own capital or a protection fund, and whether only hot wallets were hit.
"User funds are unaffected" after a hack only holds if the platform has the money to cover it and chooses to. Below, each incident in order: the loss, the cause, what users finally got back and how long it took, followed by a 10,000 USDT example under each kind of outcome (sources checked 2026-10-17).
Quick answer
- Platform covered it in full: Binance used its SAFU fund for 7,000 BTC in 2019; Bybit lost about 1.5 billion US dollars of ETH in 2025 and closed the gap within 72 hours; Bitget lost about 388 million US dollars in 2026, covered by its Protection Fund with user balances unaffected.
- Haircut, then made whole or partly whole: Bitfinex cut all accounts by about 36% in 2016 and issued BFX tokens, all redeemed by April 2017. WazirX's plan, sanctioned by a Singapore court, repaid about 85.5% first and the rest in recovery tokens.
- Bankruptcy and long waits: Mt. Gox lost about 850,000 BTC in 2014 and its final repayment deadline was pushed to 2026-10-31. FTX claims were valued in dollars as of the November 2022 petition date.
- The common thread: withdrawals almost always stop first, for days in the best case and years in the worst.
12 incidents at a glance
| When | Exchange | Loss | Cause | What users got |
|---|---|---|---|---|
| 2014 | Mt. Gox | About 850,000 BTC | Security breach; halted withdrawals and filed for bankruptcy | Rehabilitation; repayments in BTC, BCH and yen since 2024; final deadline moved to 2026-10-31 |
| 2016-08 | Bitfinex | About 119,756 BTC | Hot wallet theft | Every account cut by about 36%, made up with BFX tokens ($1 of loss each), all redeemed by April 2017 |
| 2018-01 | Coincheck | About 523 million NEM (about 58 billion yen) | Malware on an employee's computer | Repaid from own funds at 88.549 yen per XEM to about 260,000 users, about 46.3 billion yen |
| 2019-05 | Binance | 7,000 BTC | Phishing, viruses and other methods used to obtain user API keys and 2FA codes; only the BTC hot wallet, about 2% of BTC holdings, was hit | SAFU fund covered it in full, no user funds affected; deposits and withdrawals paused for about a week |
| 2020-09 | KuCoin | About 280 million US dollars | Private keys of several hot wallets leaked | About 84% recovered through partner freezes and law enforcement; KuCoin and its insurance fund covered the rest |
| 2022-11 | FTX | Bankruptcy (not simply a hack) | Customer funds misused; filed for bankruptcy | Claims valued in dollars at the petition date; small (convenience class) creditors at a cumulative 120% by 2025 |
| 2023-11 | HTX (and the Heco bridge) | Over 86.6 million US dollars from the bridge, plus hot wallets | Hot wallets and bridge drained | Justin Sun said HTX would fully compensate user losses; deposits and withdrawals paused for the investigation |
| 2024-05 | DMM Bitcoin (Japan) | About 4,502.9 BTC (about 300 million US dollars) | Private key leak | Group raised about 55 billion yen to buy back the same amount of BTC; announced closure in December and moved accounts to SBI VC Trade |
| 2024-07 | WazirX (India) | About 230 million US dollars | Multisig wallet drained; a US, Japan and South Korea joint statement linked it to North Korea's Lazarus | Singapore High Court sanctioned the scheme on 2025-10-13; about 85.5% repaid first, the rest in recovery tokens |
| 2024-09 | BingX | About 43 million US dollars (estimates vary) | Hot wallet theft | BingX said it would cover losses in full from its own capital; withdrawals reopened in stages |
| 2025-02 | Bybit | About 1.5 billion US dollars of ETH | Signing interface for an ETH multisig cold wallet transfer was manipulated; the FBI attributed it to North Korea's TraderTraitor | ETH gap closed within 72 hours; Hacken proof-of-reserves report confirmed 1:1 |
| 2026-09 | Bitget | About 387.5 million US dollars (later put at about 388 million) | Attacker bypassed existing security controls and moved funds from hot and warm wallets | Protection Fund covered it, user balances unaffected; withdrawals resumed in phases from 9-28, complete on 10-02; Protection Fund back above 300 million on 9-30 |
Sources: Mt. Gox Decrypt, The Block; Bitfinex The Block; Coincheck Bloomberg; Binance announcement; KuCoin Decrypt; FTX Cointelegraph; HTX Cointelegraph; DMM Bitcoin The Block; WazirX Cointelegraph, MediaNama; BingX The Block; Bybit press release, The Register (FBI attribution); Bitget official incident update, phased withdrawal resumption, Protection Fund replenished. Checked 2026-10-17. Dollar figures are mostly at prices at the time and vary slightly between outlets. The table only includes incidents we could tie to an official statement or mainstream report; an exchange missing from it does not mean nothing happened there.
Patterns across the 12
- Hot wallets are where it usually happens: Binance, Bitfinex, KuCoin, BingX and Bitget all lost hot or warm wallet funds. Binance's 2019 notice says the hot wallet held about 2% of its BTC. Cold wallet breaches are rarer; Bybit 2025 is the exception, and the attack went through the signing interface.
- Who pays decides your outcome: platforms with large reserves or protection funds (Binance SAFU, Bitget's Protection Fund) usually leave users untouched. Bybit filled its gap with loans and support from large holders. When the platform can't pay, you get a haircut (Bitfinex, WazirX) or bankruptcy (Mt. Gox, FTX).
- Withdrawals always stop: even when users are made whole, withdrawals pause first. Bitget's USDT withdrawals were down from 9-24 to 9-30 this time, about six days; Binance estimated a week in 2019.
- Bankruptcy is priced in fiat: FTX claims were valued in dollars as of the November 2022 petition date, so later price moves did nothing for creditors.
You can't control whether an exchange gets hacked, only how much you have sitting on it that day.
A worked example: 10,000 USDT on an exchange that gets hit
| Type of outcome (case) | What you get back | How long |
|---|---|---|
| Platform covers in full (Bitget 2026) | 10,000 USDT | USDT withdrawals back after about 6 days |
| Site-wide haircut, then made up (Bitfinex 2016) | About 6,400 left at first, about 3,600 made up via tokens | About 8 months until fully redeemed |
| Court-approved scheme (WazirX 2024) | About 8,550 first, about 1,450 in recovery tokens | About 15 months after the hack |
| Bankruptcy (FTX 2022, small claim) | About 120% of the petition-date dollar value | Two and a half years or more |
The same 10,000 USDT comes back untouched within a week in the best case, and takes years in the worst, with no access to it in the meantime. That's why many long-term holders keep trading money on exchanges and move the rest to a wallet they control.
What this has to do with rebates
An exchange's automatic rebate goes back into your exchange account, sitting next to your trading funds, and gets frozen with them if something goes wrong. Fee Otter's extra rebate is settled daily and, on request, paid as on-chain USDT on BEP20 to an address you bound yourself, minimum 1 USDT, with the 0.015 USDT network fee paid by you, and every payout is visible on BscScan. Withdrawing your rebate regularly means it doesn't have to share the platform risk your trading funds carry. For whether a rebate platform itself is safe, see is a crypto fee rebate safe.