Skip to content

Coinone Data Breach: Call Center Servers Hit, Phishing Risk for Customers

Coinone's external call center vendor MetaM was breached on November 12, exposing support chat data including wallet addresses and bank details. Trading…

3 min read How we work

Coinone disclosed on November 15 that an attacker gained access to servers belonging to MetaM, the third-party vendor managing part of the South Korean exchange's customer support operations. The intrusion occurred on November 12 and involved data stored within support conversation logs. Coinone has not disclosed how many customers are affected.

개인정보 유출 사실 관련 안내
고객님, 코인원입니다.당사는 고객님의 개인정보 보호를 위해 최우선으로 노력해 왔으나, 당사가 고객 상담 업무를 맡긴 수탁업체의 서버에 외부 공격자가 무단으로 침입하여 고객님의 소중한 개인정보가 유출되었음을 알려 드립니다. 위탁사로서 이번 사고에 대해 깊은 책임감을 느끼며 진심으로 사과드립니다. 참고로, 고객센터 상담이력이 없는 고객님의 경우 이번 정보유출과…

The data potentially exposed varies by customer, depending on what each individual had shared with support. According to Coinone's official notice published on November 15, the list of compromised fields includes phone numbers, names, email addresses, dates of birth, bank account details, passwords, identification numbers, document issue dates, home addresses, wallet addresses, and transaction identifiers (TXIDs). Coinone clarified that not every field applies to every affected customer. Customers who had never contacted support, the exchange stated, are not involved in the breach.

Trading Accounts and Wallets Kept Separate from the Compromised Servers

Coinone stated that its account, trading, and wallet systems are hosted on infrastructure entirely separate from MetaM's servers, and that those systems show no signs of direct compromise at this time. The exchange said it has launched an investigation alongside the vendor and external specialists, though it has not yet provided a total count of affected users or full details about the incident's scope.

After receiving the breach notification from MetaM, Coinone blocked the access points and IP addresses used in the attack, reinforced monitoring of anomalous logins and transactions, and temporarily redirected external customer support to email only. The company also confirmed it has notified the relevant South Korean authorities.

The Real Risk: Phishing Built on Your Own Support History

The potential exposure of personal data combined with the contents of past support conversations creates conditions for highly convincing fraud. An attacker who knows a real conversation detail, a wallet address, or a previously reported issue can craft messages that are far harder for victims to dismiss. The goal is typically to extract OTP codes or authorize a transfer.

Coinone is urging anyone who shared a password during a support conversation to change it immediately, especially if that password is reused on other platforms. The exchange also reminded customers that it never requests passwords, OTP codes, or verification codes via phone, SMS, or email, and never asks users to withdraw cryptocurrency or change a wallet address. As Coinone noted in its official disclosure at coinone.co.kr, even a message that accurately cites real support history could be an impersonation attempt.

This incident exposes a structural vulnerability that extends well beyond Coinone. Customer data doesn't stay inside an exchange's core trading infrastructure: it flows to vendors, support platforms, and third-party tools. Coinone says its trading and custody systems were not directly breached, but the full scale of the exposure will only become clear as the investigation concludes and individual notifications go out. Customers who used Coinone support before November 12 should treat any unsolicited contact, however detailed it appears, with significant caution.

Promotional content