South Korea widens exchange scrutiny after Bithumb’s bitcoin credit error

On February 8, 2026, South Korea’s Financial Services Commission convened a review of Bithumb’s erroneous bitcoin credits and directed a broader examination of internal controls at virtual-asset exchanges. The regulator’s move turned an operational failure at one trading venue into a market-structure and user-protection issue for the country’s exchange sector.

Bithumb also said on February 8 that it had restored full matching between customer entitlements and exchange-held assets and had begun compensation. That was the company’s contemporaneous account, not an independent audit finding. The Financial Supervisory Service’s inspection was still part of the response described by the regulator.

From a reward error to a regulatory test

Bithumb’s February 7 notice placed the original error at 19:00 Korea Standard Time on February 6. The exchange said a mistake in the quantity field during a promotional reward distribution caused 620,000 BTC to be credited across 695 customer accounts. It said it detected the problem at 19:20, began blocking trading and withdrawals at 19:35, and completed those restrictions at 19:40.

The distinction between a ledger credit and a blockchain transfer is essential. Bithumb said none of the mistakenly credited bitcoin was transferred outside the platform. Its notice reported that 618,212 BTC, or about 99.7% of the erroneous amount, was recovered directly. It said recipients had already sold the remaining 1,788 BTC credited on the platform, requiring additional recovery steps and use of company-owned assets.

On February 8, Bithumb said customer-asset matching had been completed as of 22:45 Korea Standard Time on February 7. It described the result as 100% reconciliation between customer deposits and assets held by the exchange. The company also announced 20,000 won payments for customers logged into its app or website during the incident, plus reimbursement of the sale-price difference and an additional 10% for customers who sold at depressed prices between 19:30 and 19:45 on February 6.

What the regulator ordered

The FSC said its February 8 meeting included the Korea Financial Intelligence Unit and Financial Supervisory Service. Chairman Lee Eog-weon instructed officials to check for further user harm, monitor the FSS on-site inspection and watch significant virtual-asset market movements.

The response extended beyond Bithumb. The FSC said the Digital Asset Exchange Alliance would first review exchange internal controls, with the FSS conducting on-site work based on those results. Officials specifically identified ledger-based cross-checks, multiple-verification procedures and controls designed to prevent human error in asset distributions.

The commission also connected the incident to pending virtual-asset legislation. Its February 8 statement said policymakers would seek financial-company-level internal-control standards, periodic reviews of exchange asset holdings by external experts, and a basis for strict liability when users suffer losses from errors in data-processing systems. Those were policy intentions on February 8, not enacted requirements established by the meeting itself.

What the market evidence does and does not show

Bithumb said sales by some recipients caused a rapid, temporary bitcoin price move on its platform and that the price returned to a normal level within five minutes. The FSC separately referred to a sharp drop. Neither primary record supplied a complete tick series, exact low, comparison venue or consolidated global price window.

Accordingly, the verified record supports a venue-specific dislocation, not a measured claim about bitcoin’s worldwide market price. Crypto trades continuously across exchanges, and Bithumb’s internal ledger event cannot by itself establish a market-wide move or quantify spillovers elsewhere.

Why February 8 mattered

The consequential development was the regulatory escalation. The incident demonstrated how an internal accounting or reward-control failure could create tradable balances, distort a local order book and expose customers even without an on-chain transfer or external hack. By February 8, the immediate reconciliation claim had become secondary to a wider question: whether exchange controls, asset verification and compensation rules were strong enough to prevent a single operational error from becoming a user-protection event.