South Korean crypto exchange Coinone has confirmed the Coinone data breach: attackers broke into MetaM, the outsourced firm that runs its customer support, and customer data was leaked. The support desk was. And that support desk held the kind of data an exchange’s own systems are built to protect: passwords, bank account numbers and South Korean resident registration numbers, shared by customers in chat and phone calls.
Coinone disclosed the breach in a public notice on Sunday 15 November 2026, SBS reported. The attacker had accessed MetaM’s servers at around 4 a.m. on Thursday 12 November and viewed or extracted customer consultation records. Coinone says its own account, trading and wallet systems run on separate infrastructure and show no sign of direct intrusion.
The scope is limited to customers who contacted Coinone’s support. People who never contacted support are not affected, Cointelegraph reported. Coinone has not disclosed how many customers are affected.
The breach hit the support desk, not the exchange
MetaM is a commissioned service provider that handles Coinone’s customer support. An external attacker made an unauthorised intrusion into MetaM’s servers, Coinone said in its notice. The records taken were the consultation data customers left during chat or phone support sessions, not trading data.
Coinone learned of the incident at around 9:20 a.m. on 12 November, when MetaM reported it, Herald Corp reported. Immediately after learning of it, Coinone blocked the attack IPs and access to the customer centre, and switched support to email-only consultations. It also stepped up monitoring of abnormal logins and transactions, and began reviewing the vendor’s security management.
The exchange reported the leak to three regulators, the Korea Internet and Security Agency (KISA), the Personal Information Protection Commission (PIPC) and the Financial Supervisory Service (FSS), and is cooperating with their investigations. Coinone apologised, promising a comprehensive review of security “not only of our own systems but also of the partner companies to which we entrust operations”.
Coinone ranked third among South Korea’s crypto exchanges by estimated app monthly active users in July 2025, at about 600,000, according to WiseApp Retail data, BitRss reported. It offers won trading through real-name accounts at KakaoBank.
Eleven fields in the Coinone data breach, and six of them are dangerous
Eleven categories of data were potentially exposed, varying by customer with what each person shared in their support interaction. The list is what makes this breach different from an ordinary contact-data leak: six of the eleven fields go beyond ordinary contact data. Four are sensitive identity or financial information, with the password and resident registration number carrying the most serious risk. That grouping is ours, not Coinone’s.
| Group | Fields | Why it matters |
|---|---|---|
| Most sensitive (4) | Passwords, resident registration numbers, bank account numbers, ID issue dates | Raise the risk of impersonation and targeted social engineering |
| Crypto-specific identifiers (2) | Wallet addresses, transaction IDs (TXIDs) | Tie a victim to on-chain activity |
| Identity profile (5) | Names, phone numbers, email addresses, dates of birth, home addresses | Complete the phishing profile |
The resident registration number sets this breach apart. It is South Korea’s national identity number, and its presence in the exposed support data is what makes this leak serious. A password shared in a support chat is the other one: Coinone urged customers who shared passwords during support to change them immediately, and to update the same password on any other site where it was used.
Coinone says the exposed information alone cannot log anyone in or withdraw assets. The risk is impersonation: a caller who could quote your name, date of birth, bank account number and details of your last support call sounds like your exchange.
Seventy-six hours from intrusion to disclosure
The vendor told Coinone the same morning; the public did not hear about it for three days. Both halves of that timeline are confirmed, and the contrast is the story of this breach as much as the data itself.
| Event | Time (KST) | Gap |
|---|---|---|
| Attacker accesses MetaM’s servers | Thu 12 Nov, around 4 a.m. | None |
| MetaM notifies Coinone | Thu 12 Nov, around 9:20 a.m. | 5 hours 20 minutes |
| Coinone blocks attack IPs, switches support to email-only | Thu 12 Nov, after learning of it | Same day |
| Coinone confirms the leak publicly | Sun 15 Nov, around 8 a.m. | 76 hours after intrusion |
The 76-hour gap is our own calculation: intrusion around 4 a.m. on 12 November, public confirmation around 8 a.m. on 15 November. Coinone says it was investigating the exact timing and details with the vendor and specialist agencies in that period. The gap is a timeline fact, not evidence of a cover-up.
The disclosure comes as South Korea tightens financial-sector cybersecurity. In October 2026, 130 of 555 financial firms reported areas needing improvement in the Financial Services Commission’s 12-point cybersecurity checklist, Cointelegraph reported. On Thursday 12 November the regulator said it would issue a conditional no-action opinion allowing virtual-asset service providers to proactively block deposits and withdrawals when hacking is suspected.
What should I do if I contacted Coinone support?
If you ever contacted Coinone support, assume the details you shared in that chat or call may be in an attacker’s hands. Change any password you shared there, and anywhere else you used it too. Then treat every call or message that quotes your support history as unproven until you check it another way.
- Change the password you shared with Coinone support, starting with your Coinone account and email.
- Change the same password on every other site where you reused it, starting with banking and email.
- Check that the two-factor authentication on your Coinone account uses a phone number you still control.
- Ignore calls or messages that quote your support history and ask for money, codes or remote access.
- Watch for Coinone’s lookup tool, and use it once available to check which details were exposed.
- Report any suspicious call or message to Coinone through the official channels listed in its notice.
Coinone says it will never ask for a password, a one-time code, a withdrawal or a wallet-address change by phone, text or email.
What is confirmed, and what is not
Confirmed: the Coinone data breach began when an attacker accessed MetaM’s servers at around 4 a.m. on 12 November and viewed or extracted customer support records. Coinone learned of it at 9:20 a.m. the same day and confirmed it publicly on 15 November. Eleven categories of data were potentially exposed, varying by customer. Coinone’s own account, trading and wallet systems show no sign of direct breach. The leak was reported to KISA, the PIPC and the FSS. Coinone plans a personal data exposure lookup service so customers can check which of their details were affected.
Not confirmed: whether the attacker actually copied the support data out or only viewed it, since Coinone’s wording is “viewed or extracted” and no source confirms a volume of stolen records. Coinone has not attributed the attack to a named threat actor, and its notice does not mention ransomware or extortion. No customer funds have been reported stolen. The exact number of affected customers has not been disclosed, and the exact timing and details of the leak are still under investigation.
What to watch next
The lookup tool is the first thing to watch. Coinone says it will prepare a lookup tool and a separate notification service so customers can check which of their details were affected. The public notice does not say which fields were exposed for each individual; Coinone plans to provide that through a separate notice or the lookup service.
The second is the affected count, which Coinone has not disclosed. The PIPC and KISA have been notified and are involved in the response; whether a count will be released remains unknown. The third is whether the FSC’s conditional no-action opinion on blocking deposits and withdrawals, announced on 12 November, three calendar days before this disclosure, gets used at Coinone or any other exchange. None of these has a date yet. None of them changes what a customer who contacted support should do today: change the password and treat the next call as unproven.


