Bithumb discloses data leak after internal system breach: Report

Bithumb is South Korea's second-largest crypto exchange, and the breach disclosed on October 28 hit an internal workplace tool used by staff rather than the trading platform itself. The incident lands alongside a separate breach at Coinbase, where contact details for roughly 70,000 users were potentially exposed, and reports naming two other South Korean financial firms hit by similar intrusions. Employee-facing systems, not custody infrastructure, are emerging as the weak point across multiple exchanges this year.

Bithumb says no cryptocurrency funds were lost, but it is still checking whether customer personal information leaked alongside employee data, leaving account holders unable to confirm their own exposure yet. Until that review closes, users are left watching for phishing attempts built on any leaked details rather than acting on a confirmed breach notice. Employees whose mobile work system was compromised face the immediate fallout, while Bithumb must now demonstrate its internal tools meet the same scrutiny as its trading systems.

Pairing Bithumb's case with Coinbase's shows the same structural weakness recurring regardless of jurisdiction or market position: centralized back-office systems holding user data remain a single point of failure, even when custody of coins stays intact. Crypto exchanges market themselves on securing digital assets, yet the personal information tied to those accounts sits in conventional corporate systems with conventional vulnerabilities. That gap between asset security and data security is where repeated breaches keep landing.

Bithumb's own confirmation of whether customer data, not just employee records, was exposed is the open question that will determine the scale of this incident. South Korean regulators grouping Bithumb with two other financial firms reporting breaches suggests a sector-wide review may follow, which could bring disclosure requirements or penalties. Until Bithumb publishes a completed assessment, the number of affected customers and any required notifications remain unresolved.