Published: February 7–12, 2026
On February 6, 2026 at approximately 7:00 PM KST, South Korea’s second-largest cryptocurrency exchange Bithumb suffered one of the most dramatic operational failures in exchange history: during a routine “Random Box” promotional event, an employee entered “BTC” instead of “KRW” in the reward field, resulting in ~620,000 BTC (roughly $40–44 billion at prevailing prices) being credited to 695 user accounts instead of the intended 620,000 KRW (~$1.40 USD each).
The error created phantom balances approximately 13× larger than Bithumb’s actual BTC holdings (~46,000–48,000 BTC). Within minutes the mistake triggered a 17% localized flash crash on Bithumb (BTC fell from ~₩95 million to ₩81.1 million / ~$55,000 USD), before stabilizing. Bithumb detected the issue in ~20 minutes, froze affected accounts in ~35 minutes, and has since recovered 99.7% of the erroneous credits. This article provides the full timeline, technical explanation, recovery mechanics, regulatory fallout, compensation details, and critical lessons for centralized exchanges in 2026.
Timeline of the Bithumb Fat-Finger Incident
| Time (KST, Feb 6 2026) | Event | Impact / Action |
|---|---|---|
| ~19:00 | Random Box promo goes live with erroneous BTC denomination | ~695 users receive ~620,000 BTC total (~2,000 BTC each on average) |
| 19:05–19:20 | Users notice massive balances; some begin trading / withdrawing | BTC price on Bithumb crashes 17% to ₩81.1M (~$55K USD); global BTC stable at ~$68,400 |
| 19:20–19:40 | Bithumb internal detection & emergency freeze | All trading & withdrawals halted on affected accounts; hot wallet protected |
| Feb 6 evening – Feb 7 | 99.7% of erroneous BTC reversed via ledger adjustment | ~125–1,788 BTC (~$9M) remains outstanding (users who transferred out) |
| Feb 7–ongoing | FSC on-site inspection begins | Investigation under Virtual Asset User Protection Act; potential unjust enrichment lawsuits |
What Actually Happened: The Technical Error Explained
The “Random Box” promo was intended to distribute small KRW amounts (average ~2,000 KRW ≈ $1.40) to participants. An employee incorrectly configured the reward denomination field as BTC instead of KRW — a classic “fat finger” input mistake.
Critical failures in the system:
- No unit/type validation on promo reward input
- No real-time cross-check against actual holdings before crediting
- Ledger allowed phantom balances far exceeding hot-wallet reserves (13× overage)
- Insufficient pre-launch simulation or multi-person approval gate
Because the error occurred in the internal ledger (not on-chain), Bithumb was able to reverse most credits quickly once frozen. The 0.3% outstanding (~$9M) represents users who transferred funds out during the ~20–35 minute window before freeze — Bithumb is pursuing recovery via legal channels under Korea’s Virtual Asset User Protection Act.
Market Impact – 17% Localized Flash Crash
The error created extreme localized volatility on Bithumb:
- BTC/KRW pair dropped ~17% from ~₩95 million to ₩81.1 million (~$55,000 USD equivalent)
- Global BTC price remained stable (~$68,400 USD on Binance, Upbit, etc.)
- No cascading liquidations on leveraged positions — Bithumb halted trading fast enough
- Trading volume spiked massively during the crash window
This event highlights a persistent CEX vulnerability: internal ledger errors can create massive price dislocations on a single venue even when global markets remain calm.
Compensation & Regulatory Response
Bithumb announced the following remedial measures:
- Waived trading & withdrawal fees for 7 days post-incident
- Crash victims (users who sold during the 17% drop) receive price difference reimbursement + 10% bonus
- Active users during the event receive 20,000 KRW (~$14 USD) goodwill payment
- Corporate funds covering the ~$9M outstanding balance (no customer losses)
Regulatory fallout:
- South Korea Financial Services Commission (FSC) launched on-site inspection within 24 hours
- Investigation under Virtual Asset User Protection Act (effective 2024)
- Potential fines, suspension orders, or forced compensation enhancements
- Users who refuse to return erroneous funds face civil lawsuits for “unjust enrichment”
Industry Lessons – CEX Internal Controls Exposed
The incident echoes past fat-finger disasters (e.g. Samsung Securities 2018 KRW 100B share error) and reinforces several critical lessons:
- Require multi-layer validation (unit check + balance check) before crediting promotions
- Implement real-time ledger vs actual holdings reconciliation
- Enforce hard circuit-breakers on internal ledger anomalies
- Conduct full end-to-end simulations before any promo launch
- Separate promo ledger from core trading ledger until final reconciliation
It also highlights the continuing advantage of decentralized exchanges: immutable on-chain execution prevents this class of centralized ledger error entirely — though DEXes face their own scalability and UX trade-offs.
Tapbit Trading & Risk Management Considerations
For traders on Tapbit during similar high-profile exchange incidents:
- Monitor localized vs global prices — use Tapbit’s multi-exchange price aggregator to spot Bithumb-style dislocations
- Stablecoin parking → shift to USDT Earn yields during fear spikes
- Dip buying → DCA BTC/USDT spot on global weakness (Tapbit zero-fee)
- Leverage caution → reduce perps exposure during Korea exchange news (125x available but use conservatively)
- Alerts → enable Tapbit app notifications for volume spikes or price divergence
FAQs – Bithumb $40B Bitcoin Error (February 2026)
Did Bithumb lose customer funds in the error?
No — 99.7% of erroneous BTC was reversed via ledger adjustment. The remaining ~$9M is being pursued legally from users who transferred out; no customer balances were permanently lost.
Why did BTC only crash on Bithumb, not globally?
The error was internal ledger-based, not on-chain. Bithumb froze trading quickly, preventing arbitrage outflows. Global exchanges remained stable at ~$68,400.
Will users who kept the BTC face lawsuits?
Yes — Bithumb and FSC can pursue civil recovery under unjust enrichment laws. Korea courts have previously limited such claims in similar cases, but regulatory pressure is higher in 2026.
What compensation is Bithumb offering?
Crash victims get price difference +10% bonus; active users get 20,000 KRW (~$14); 7-day fee waiver. Corporate funds covering outstanding balance.
Conclusion & Regulatory Outlook
Bithumb’s February 6, 2026 fat-finger error — accidentally crediting ~620,000 BTC (~$40–44 billion) to 695 users — ranks among the largest operational failures in exchange history by notional value. Yet the rapid detection (20 minutes), freeze (35 minutes), and 99.7% recovery demonstrate effective crisis response, preventing systemic contagion or customer losses.
The incident will almost certainly accelerate regulatory scrutiny under Korea’s Virtual Asset User Protection Act: expect tighter internal control requirements, mandatory pre-launch simulations, real-time ledger reconciliation rules, and potentially higher capital reserves for major exchanges. For traders on Tapbit, it reinforces the value of diversified custody, stablecoin parking during fear, and zero-fee spot accumulation on global weakness — while highlighting why many are migrating toward DEXes for immutability.
Trade safely & efficiently on Tapbit:
- Sign Up on Tapbit (0% maker fees)
- Login & Secure Your Account
- Go to Security Center – Enable All Protections
Disclaimer: Cryptocurrency trading involves significant risk of loss. Prices are highly volatile and can change rapidly. Exchange incidents, regulatory actions and recovery outcomes are uncertain. This article is for informational purposes only and does not constitute investment, legal or financial advice. Always conduct your own research (DYOR) and never invest more than you can afford to lose completely.
