Three crypto exchanges in three countries disclosed security incidents on 28 October. Coinbase said a breach at one of its vendors exposed some customer contact details. South Korea's Bithumb confirmed that an intruder got into internal staff software and leaked personal data. India's CoinDCX confirmed a $15.99 million loss, days after its chief executive had suggested the breach reports might be a false alarm. Only one of these cases involves missing money. The other two still matter, because leaked personal data is what scammers use to set up their next attack.

Coinbase: a vendor leak, not a platform hack

Coinbase said the incident started at Amplitude, an analytics vendor whose breach exposed some customer contact information, as BeInCrypto reported. Analytics vendors are outside companies that track how people use an app or website. To do that job they often hold some identifying data.

Coinbase said its own systems and customer funds were not affected. The available reporting does not say how many customers were involved or exactly which contact fields leaked. Users should not assume that only email addresses were exposed until Coinbase says so.

Bithumb: intruders inside the groupware

According to Bitcoin.com News, citing Yonhap, Bithumb confirmed that an unauthorised outside party got into its internal mobile groupware and leaked personal data. Bithumb is South Korea's second-largest exchange. Groupware is the software staff use for messaging, email, scheduling and approving documents. That means it can hold employee details, internal conversations and sometimes customer records.

Bithumb found the intrusion on 27 October and is still checking whether any customer information was taken. No theft of funds has been reported.

Two other Korean financial firms reported intrusions on the same day. Daishin Securities said personal and credit information on 38,490 customers had leaked, the largest confirmed exposure of the three. Mirae Asset Global Investments reported a hacking incident but did not say how many clients were affected. Investigators have not linked the Bithumb breach to the other two. The Financial Supervisory Service, South Korea's main financial regulator, is investigating all three.

It has already been a difficult year for Bithumb. In February the exchange mistakenly credited 620,000 BTC to 249 users during a promotion. It recovered about 99.7% of that and promised full compensation plus an extra 10%. Korean exchanges have been targeted before: rival Upbit lost about $36 million in a Solana hot wallet hack in November 2025, which local authorities suspected was carried out by North Korea's Lazarus Group.

CoinDCX: the one incident where money was lost

CoinDCX is the only one of the three that has confirmed lost funds. Bitcoinist reported that the exchange confirmed a $15.99 million loss tied to retired wallet infrastructure, meaning wallets the exchange had stopped using. It said the cause was a failed automated transfer. Bitcoin.com News rounded the figure to $16 million.

The way the news came out is a problem in itself. A few days before the confirmation, CoinDCX's CEO had played down the reports. Bitcoinist says he called them a possible false alarm, and Bitcoin.com News says he dismissed the suspicious transfers. The available reports do not explain how a failed automated transfer turned into a $15.99 million loss. They also do not say whether any customer balances were affected or who will cover the shortfall.

Why leaked contact details are a real risk

A breach of back-office systems is not the same as a hot wallet hack. In a hot wallet hack, attackers take crypto directly from an exchange's internet-connected wallets. Back-office breaches hand attackers something slower but still useful: names, email addresses, phone numbers and sometimes proof that a person holds an account on a particular platform.

With that information, scammers can send messages that look real. They might send a "security alert" from what appears to be the exchange, a fake support call, or a text with a link to a lookalike login page. Because the target really does hold an account, the message is more convincing.

The recent pattern in the industry shows the risk. Bitcoin.com News pointed to a Keystone hardware wallet data breach that exposed buyers' addresses to scammers, a customer data breach at hardware wallet maker Foundation, and an intrusion into GMO's trading cloud. Separately, Cybernews reported that Dutch bitcoin broker Bitonic has fixed a flaw that led to a breach of bitcoin accounts.

Practical steps for affected users

These are general security habits, not responses tailored to any one exchange's investigation.

  • Treat unexpected contact as suspicious. Do not click links in emails or texts that claim to be from your exchange. Open the app or type the web address yourself.
  • Never share recovery phrases or one-time codes. No real exchange support agent will ask for your seed phrase, the list of words that controls your wallet, or for two-factor codes.
  • Upgrade two-factor authentication. Use an authenticator app or a hardware security key instead of SMS where you can, because phone numbers can be hijacked.
  • Turn on withdrawal address allowlists if your exchange offers them. These limit withdrawals to addresses you have approved in advance.
  • Watch for SIM-swap warning signs. If your phone suddenly loses service, contact your carrier straight away.
  • Check official channels only for breach notices, and be wary of "compensation" offers that ask you to connect a wallet or pay a fee.

What to watch

  • Bithumb's customer data finding: whether its investigation shows that customer records, and not just internal data, left the groupware system.
  • The FSS investigation: any findings on whether the Bithumb, Daishin and Mirae Asset intrusions are linked, and any action the regulator takes.
  • Coinbase and Amplitude: how many customers were affected, which contact fields were exposed, and whether affected users are notified directly.
  • CoinDCX's explanation: how the retired wallet infrastructure was still holding funds, whether customers bear any of the loss, and why the first public response downplayed the reports.
  • Follow-on phishing: reports of targeted scams aimed at Coinbase or Bithumb users in the coming weeks would show the leaked data is being used.