Bithumb confirms 6,444 customers affected in internal groupware intrusion
Bithumb confirmed on 29 October 2026 that an intrusion into its internal mobile groupware had exposed customer personal information, after saying on 28 October that it was still checking whether customer data had leaked. Digital Today reported that the exchange’s notice listed 6,444 affected customers and 715 employees. The disclosure put the customer impact on record.
Bithumb said 5,600 customers’ information was leaked in encrypted files, while 844 had direct exposure including names, mobile numbers, e-mail addresses, resident registration numbers, driver’s licence numbers, bank account numbers and copies of identification, Digital Today reported. Employee data for 715 also leaked. Yonhap Infomax put the combined total at 7,159, which adds customers and employees; it is not the customer count.
The 5,600 figure describes the form in which the data was held, not a finding that those records were safe. Bithumb’s account, relayed by Yonhap Infomax, was that files protected by digital rights management encryption were inaccessible from outside. The reporting does not say whether they were decrypted or opened. The 844 group is the one described as directly exposed, including identity documents that matter even if exchange accounts and assets were not directly compromised.
What Bithumb disclosed
Digital Today reported that the intrusion happened between 11:28 and 12:27 on 27 October. Bithumb detected abnormal access at 12:14 and blocked the attacker’s route and use of the system. It reported to the Korea Internet & Security Agency that day and told the Personal Information Protection Commission the next day about employee data. It had not then confirmed customer data had leaked; further analysis found the customer exposure, disclosed on 29 October.
Containment and the customer notice
Bithumb said the leaked information was believed to come from material employees saved or processed in the groupware. It said the breached system was separate from those managing exchange accounts and asset holdings, and that it had not confirmed direct compromise of exchange services or the customer database. CoinDesk reported that no crypto funds had been reported lost as of Asian afternoon hours on 28 October, a point-in-time observation rather than a guarantee.
Bithumb said it would notify affected customers individually from the afternoon of 29 October and warned against contacts impersonating employees that request authentication codes or induce app installations. Chief executive Jae-won Lee apologised. He said the company would seek relief and compensation if secondary damage was confirmed, and would re-examine security across internal work infrastructure. The reporting does not show compensation paid or the review complete.
Daishin and the Mirae Asset question
Daishin Securities said personal information of 38,490 customers had been hacked. Names, e-mail addresses and mobile phone numbers were found to have leaked after it detected signs of unauthorised access by hackers the previous week, Yonhap reported. Daishin said it was investigating with authorities, had notified customers and would compensate them in accordance with law if the breach caused damage. Those details are the brokerage’s own account, not an independent audit.
Mirae Asset Global Investments presents a less settled picture. Yonhap reported that financial authorities had begun an inspection into a data breach at the asset manager. CoinDesk reported that Mirae Asset said it blocked abnormal access to some web systems and that investor information was not affected. The accounts are not necessarily incompatible, but the available reporting does not resolve whether any Mirae Asset customer data was exposed. The inspection is not proof of a confirmed customer data leak, and the company statement is not an independent finding.
Regulators move on several fronts
The Financial Supervisory Service began an on-site inspection on the morning of 28 October after receiving the incident report. Yonhap Infomax reported that the FSS was still at the stage of understanding the details and had not confirmed whether to convert the inspection into a formal examination. No findings from that process are in the available reporting.
The Financial Services Commission held an emergency meeting on cybersecurity incidents in the virtual asset industry on 28 October, with the FSS, Financial Security Institute, Digital Asset Exchange Alliance and Bithumb attending. The FSC said security rules for the sector, which is not currently subject to the Electronic Financial Transactions Act, would be significantly strengthened to the level of major financial institutions. Inspections would also expand to Mirae Asset Life Insurance, Mirae Asset Asset Management and Daishin Securities. These are announced plans, not completed measures or findings.
What is not established
Bithumb said the incident was an intrusion exploiting vulnerabilities in a system provided by an external vendor, according to Yonhap Infomax. No specific vulnerability, CVE identifier, vendor advisory or patch detail has been supplied, and no official forensic root cause is available. The attacker’s identity, affiliation and motivation are unknown. The reporting contains no confirmed case of secondary fraud, identity theft or account takeover arising from the Bithumb leak.
Nor do the three firms belong automatically in one campaign. Yonhap reported on 28 October that all three had reported data breaches involving customers, and regulators opened inspections or assessments. But the available reporting establishes no common attacker or common technical cause. FSS Governor Lee Chan-jin said earlier in October that cyberattacks had hit 16 South Korean financial firms as of 14 October, CoinDesk reported. That figure is sector context, not evidence that Bithumb, Daishin and Mirae Asset were struck by one operation.
Why the distinction matters
The separation Bithumb describes, if correct, limits one route to customer assets. It does not erase the exposure of identity data. Copies of identification, resident registration numbers and bank account details can support impersonation attempts, and Bithumb’s warning points to contacts that seek authentication codes or persuade customers to install apps. The reporting does not show that such attempts have succeeded, only that the company considered them a sufficient concern to warn customers.
As of 29 October, the public record established the affected groups and the regulatory steps. It did not establish whether the 5,600 encrypted-file records remained protected in substance as well as form. Nor did it include findings from the FSS inspection into the incident. Those questions sit behind the confirmed numbers. Bithumb’s customer count is now on record; the scope and cause of the exposure are not.
When one notice says 6,444 customers, another figure adds employees to reach 7,159, and a second firm reports 38,490, the practical skill is working out which number answers which question. That kind of reading rests on cybersecurity fundamentals: how data categories and affected populations are defined, what encryption of a stored file does and does not settle, and why a suspected intrusion, a confirmed leak and an unresolved inspection are separate findings. With that grounding, a disclosure becomes something you can assess line by line rather than a total you either trust or dismiss. The Hack Academy’s online cybersecurity training programme lists cybersecurity fundamentals among its subject areas, with self-paced learning and practical exercises alongside the theory, if you would like to build that habit deliberately.
