Security & Risk5 minNewsroom

Coinone Confirms Data Breach via Service Provider

The South Korean exchange reports that an intruder accessed servers of the outsourced firm MetaM and exposed 11 types of data, including passwords and national ID. No funds were affected, according to the company.

Telefone de mesa fora do gancho sobre a bancada de atendimento.

Coinone, one of the largest cryptocurrency exchanges in South Korea, reported on Sunday, November 15, that an intruder accessed the servers of MetaM, the third-party company operating its customer service. According to the exchange's statement, reported by Cointelegraph, Bitcoin.com, and Crypto.news, the attacker viewed or extracted stored customer service records from the provider. The breach occurred on November 12 and was reported to Coinone by MetaM the same day.

The list of potentially exposed data includes 11 categories, according to the exchange: name, phone number, email, date of birth, bank account number, password, national resident registration number (the Korean national identifier), document issuance date, residential address, crypto wallet address, and transaction identifiers. Coinone did not disclose how many customers were affected, stating only that the incident impacts those who contacted customer service.

What the Exchange Claims and Actions Taken

The company asserts that member accounts, the trading system, and wallets operate separately from MetaM's servers and that there is no loss of customer funds. It has blocked the attacker's IP addresses, suspended access to the outsourced center, and is now handling inquiries exclusively via email, in addition to enhancing monitoring of logins and unusual activities. The case has been reported to the Korea Internet & Security Agency (KISA), the Personal Information Protection Commission (PIPC), and the Financial Supervisory Service (FSS), according to the statement. As of the end of this report, MetaM had not publicly commented.

The inclusion of passwords among the exposed fields is the most concerning detail. Customer service records should not contain credentials in plain text. If Coinone's list is accurate, some support process was logging passwords provided by customers, and the exchange’s own recommendation to change passwords on Coinone and any service where they were reused indicates that the company considers the risk to be real.

The Pattern: Customer Service as a Side Door

This incident mirrors the anatomy of the Coinbase incident in 2025. At the time, the American exchange revealed that criminals had bribed support agents abroad to obtain customer data, estimating the cost to be as high as $400 million. In June of that year, Coinbase acknowledged that the agents worked for TaskUs in Indore, India, where reported compensation ranged from $500 to $700 per month.

The difference lies in the vector. For Coinbase, the problem was individuals with legitimate access selling data. For Coinone, according to the company, it was a breach of the provider's servers. The outcome for the end customer is the same: the most protected asset of the operation, the wallet, remained intact, while the data necessary for social engineering attacks escaped through the area considered to be of lowest risk.

In August 2025, the PIPC fined SK Telecom 134.8 billion won, approximately $97 million, for a USIM data leak that affected more than 23 million subscribers, a record for a single company in the country. The commission cited weak access controls and authentication keys stored unencrypted. Storing passwords in a customer support system falls into the same category of failures.

Insights for Those Outsourcing Support

For banks and fintechs operating in Korea, this case reinforces that the PIPC scrutinizes the data controller, not just the provider. Coinone notified three regulators, which indicates that the exchange anticipates scrutiny in both privacy and financial governance.

In India and the Philippines, BPO hubs servicing banks, insurers, and exchanges from various countries, the follow-up from Coinbase and Coinone is likely to tighten contractual clauses: environment segregation, data masking in the agent console, and call access auditing. In Brazil, where exchanges and digital banks also outsource part of their support, a regulator’s question would be the same as the one the PIPC will pose in Seoul: who decided that the provider could hold that set of data.

What Coinone has yet to answer is why a service provider needed to store resident registration numbers and bank account details alongside passwords in the same repository. The response to this question, more than the final number of affected individuals, will determine the extent of the sanction.

Sources

  1. tradingview.comhttps://www.tradingview.com/news/cointelegraph:94375fced094b:0-coinone-warns-of-phishing-identity-theft-after-customer-data-breach/
  2. news.bitcoin.comhttps://news.bitcoin.com/security/coinone-data-breach-exposes-passwords-and-sensitive-customer-records/
  3. crypto.newshttps://crypto.news/coinone-data-breach-customer-support-hack/
  4. tokenpost.comhttps://www.tokenpost.com/news/technology/57666
  5. koreatimes.co.krhttps://www.koreatimes.co.kr/business/tech-science/20250828/sk-telecom-fined-97-mil-over-april-data-breach
  6. infosecurity-magazine.comhttps://www.infosecurity-magazine.com/news/taskus-employee-coinbase-breach/

The week's analysis, by email

One weekly edition with what matters to people who decide. No ads, no sponsorship.

One-click cancellation, at any time.

Security & Risk →