
Rajneesh Sachdeva
Crypto Analyst
TL;DR
An attacker reached servers run by MetaM, Coinone's outsourced customer support provider, on Thursday. Support records may have exposed names, national ID numbers, contact details, bank accounts, wallet addresses and passwords. Coinone says its trading, wallet and account systems show no direct compromise, but phishing and identity theft risks remain. No customer count has been published.
Key takeaways
- An attacker got into servers run by MetaM, Coinone's customer support vendor, on Thursday, and Coinone says it found out the same day.
- Possibly exposed data includes names, birth dates, national ID numbers, phone numbers, emails, home addresses, bank account numbers, wallet addresses, transaction IDs and passwords.
- Coinone says exposure depends on what each customer shared with support, and its account, trading and wallet systems run separately with no sign of direct compromise.
- Coinone has not published how many customers are affected, and it warned that fraudsters could use details from past conversations to impersonate the exchange.
- Coinone told South Korean regulators, who recently found security deficiencies at 130 of 555 financial firms reviewed.
Coinone wasn't hacked the way most people picture. Its trading engine, wallets and account systems appear untouched. The damage came through a side door: a vendor that answers customer questions.
On Sunday, the South Korean exchange told users that an attacker had gotten into servers run by MetaM, its outsourced customer support provider, on Thursday. The intruder viewed or pulled support records. Coinone says it found out the same day. For now, the Coinone data breach is a story about what people typed into a help ticket.
The Support Records Held More Than Anyone Expected
The list of possibly exposed fields is long. Cointelegraph's report says it spans identity basics such as a customer's name, birth date and national ID number, plus contact details like phone, email and home address. It also reaches financial items: bank account numbers, crypto wallet addresses and transaction IDs. And it includes passwords.
Not every customer lost every item. Coinone says the mix depends on what each person shared with support, and anyone who never contacted the help center is, by the exchange's account, outside the blast radius.
How many people are inside it? Nobody outside Coinone knows, and Coinone hasn't published a count.
The passwords line is the one that jumped out at me. Plenty of exchanges tell users never to share credentials with staff. Yet the records apparently held some, which suggests either agents asked or customers pasted them in while locked out and annoyed. Either way, a support log is a bad place for a password to live. Expect regulators to ask why it was there.
Why a Help Ticket Is Such a Rich Target
Think about what a support conversation actually is. A customer who is locked out, confused about a withdrawal or stuck in identity verification will say almost anything to get unstuck. They attach screenshots, read out account numbers and explain their situation in detail. Over months, a ticket archive becomes a more candid file on a person than the formal onboarding record ever was.
That matters because onboarding data is structured and tightly held, while support data is messy, free‑form and often stored by whoever was cheapest to hire. Nobody designing a help desk tool thinks of it as a vault. Attackers do.
There's also a quality problem. Stolen databases of leaked emails are cheap and stale. A fresh set of tickets tied to a named exchange, with real dates and real problems, is worth far more to a fraud crew because it comes with a script.
Vendors Keep Being the Weak Link
Exchanges spend heavily on cold storage, withdrawal whitelists and key management. Customer service gets a smaller budget and a contractor. That's a sensible cost decision right up until the contractor's servers hold the same identity details as the exchange's compliance team.
Coinone says its account, trading and wallet infrastructure runs separately from MetaM's systems and shows no sign of direct compromise. I'd take that at face value for now, with one caveat: it's a statement about funds, not privacy. Nobody drains a wallet with a birth date. They use it to sound credible on the phone, and that is where the exposure will show up first.
The contractual question is just as interesting. Under South Korean rules, a financial firm generally stays answerable to its customers for data it hands to an outsourced partner. If that holds here, the exchange carries the reputational and possibly legal weight for a breach on servers it did not run. That is a strong argument for auditing vendors as hard as the firm audits itself.
The Scam That Follows a Leak Like This
Coinone itself flagged the likeliest next step. Fraudsters can reference details from earlier conversations to pose as the exchange. A caller who knows your name, the month you asked about a withdrawal and the last four digits of your bank account doesn't sound like a stranger.
That's why support‑channel leaks are nastier than a bare email dump. The context is real, and a phishing text that mentions a ticket you actually opened gets clicked.
The practical advice is boring, and it holds up:
- Change any password you ever gave to support staff, and anywhere you reused it.
- Treat unsolicited calls, texts and emails claiming to be Coinone as hostile, even when they cite accurate details.
- Contact the exchange only through the app or the address you type yourself.
- Watch for new accounts or loans opened with your national ID number.
The last item moves slowly. Identity theft built on a leaked national ID can surface months later, long after the headlines fade, so the vigilance has to outlast the news cycle.
Seoul Was Already Leaning on the Sector
The disclosure landed in the middle of a regulatory push. In October, the Financial Services Commission found security deficiencies at 130 of the 555 financial firms it reviewed, roughly one in four. Then on Thursday, the same day the intruder reached MetaM's servers, the regulator said it would let crypto exchanges suspend withdrawals when they suspect a hack, and called for round‑the‑clock monitoring.
Those two rules target a different threat than this one. A withdrawal freeze helps when an attacker is draining hot wallets. It does nothing when the stolen item is a transcript of a support chat. Monitoring requirements might catch an intrusion sooner, but only if they reach contractors and not just the exchange's own perimeter.
Coinone told South Korean regulators about the incident and did the one clear thing it could: warn people fast. Fine. Speed isn't the same as disclosing scope, and the second is still missing.
What the Rate and Policy Backdrop Means Here
It's tempting to file a vendor leak under operational noise, separate from the market story. I'd resist that. Institutions that have been edging toward crypto, from banks to asset managers, ask the same questions of every platform: who touches customer data, and who is liable when they fail? A breach at a contractor is exactly the scenario their risk committees model.
Regulators are asking the same thing from the other side. With Seoul tightening its security expectations, an incident like this gives supervisors a concrete case for pushing the rules past the exchange's own walls. If that happens, compliance costs rise for every platform that outsources support, and the cheapest vendors become the hardest to justify.
None of this says anything about prices or what anyone should hold. It does say that trust, not just technology, is what exchanges are really selling, and a leaked help desk spends it quickly.
What to Watch Next
Three things will show how serious this is. First, whether Coinone publishes a customer count or a date range for the affected records. Second, whether regulators treat outsourced support vendors as part of an exchange's own security obligations. Third, whether phishing reports tied to Coinone start climbing over the coming weeks.
If they do, the lesson won't be about cold storage. It will be that in 2026, the weakest system an exchange owns may be one it doesn't operate.
