wasl.tech

Coinone Breach: Passwords and National IDs Exposed in Support Vendor Hack

Picture the scene. A Coinone customer in Seoul calls the exchange’s support line about a stuck withdrawal. The agent on the other end is polite and helpful. They take down the details — a name, a phone number, maybe even a password — and promise to sort it out.

Now imagine that conversation sitting on a server that was never meant to be a target. That is what happened in the early hours of Thursday, November 12, when an attacker slipped into the systems of MetaM, the outside company that handles Coinone’s customer support.

Coinone, South Korea’s third-largest crypto exchange, confirmed the Coinone breach in a public notice on Sunday, November 15. The hackers did not touch trading accounts or wallets, the exchange said. But the support records they reached may contain some of the most sensitive information a person can lose.

What Happened Inside MetaM’s Servers

According to CoinCentral, the break-in happened at about 4 a.m. Korean time on Thursday, November 12. MetaM reported it to Coinone at about 9:20 a.m. the same morning — a little over five hours later.

The public did not hear about it until Sunday. Coinone posted its notice at 8 a.m. Korean time on November 15, roughly 76 hours after the attack began and more than 70 hours after the exchange itself knew.

Coinone has not explained how the attacker got in. The exchange says it is investigating the method with MetaM and outside security specialists, and it promises to publish new findings as they emerge.

What the Coinone Breach Exposed

The server held consultation records — the notes and transcripts from customer chats and phone calls. Coinone lists eleven types of personal data that may appear in them.

The list reads like a fraudster’s wish list. Names, phone numbers, email addresses and dates of birth sit alongside bank account numbers, passwords, home addresses and crypto wallet addresses.

Worse still are the identity documents. The records may include resident registration numbers — South Korea’s national ID — and the issue dates on identity cards. Those cannot simply be changed like a password.

Not every customer had all eleven types exposed. What leaked depends on what each person said during their own support conversation. But Coinone has not said how many customers are affected, or how many consultation records the server held.

One boundary does apply. Only customers who contacted Coinone’s support centre are in scope. Anyone who never opened a ticket falls outside the incident, the exchange says.

What the Hackers Did Not Reach

Coinone was quick to draw a line around the damage. Its account, trading and wallet systems run separately from MetaM’s servers, and the exchange says no direct intrusion into them has been confirmed.

No crypto has been reported stolen. Coinone also argues that a leaked password alone is not enough to break into an account, because logging in needs extra checks such as a registered one-time password or KakaoTalk verification.

That is reassuring as far as it goes. But passwords and national IDs are useful in ways that have nothing to do with logging into Coinone. They are the raw material for identity theft, phishing calls and bank fraud — and they do not expire.

Three Days Before Customers Were Told

The timing has drawn attention. MetaM told Coinone about the breach within hours, yet the public notice arrived three days later. Coinone did not say how many customers were affected.

Coinone says it reported the incident to three regulators: the Korea Internet and Security Agency, the Personal Information Protection Commission and the Financial Supervisory Service. The notice does not say when those reports were filed.

In the meantime, the exchange says it blocked the attacker’s IP address and the access paths to its customer centre. It stepped up real-time monitoring of unusual logins and transactions, and it is reviewing MetaM’s security controls itself.

Customer support has moved to email only for now. Coinone also plans to launch a lookup service so people can check whether their details were involved — though no date has been set.

The Third Korean Exchange Hit in Three Weeks

The Coinone breach is not an isolated incident. It is the third data or security scare at a South Korean exchange in less than three weeks.

Bithumb detected unauthorised access to its groupware on October 27. The exchange later confirmed records tied to 6,444 customers, with personal data directly exposed for 844 of them. Gopax reported its own incident on November 6.

Regulators were already worried. In October, South Korea’s Financial Services Commission found security gaps at 130 of the 555 financial firms it reviewed. This week, the regulator said it would let crypto exchanges suspend withdrawals when hacking is suspected.

The incidents land while Seoul is still reworking its rules after the Binance hack. Coinone is a significant player — the country’s third-largest exchange, with OKX holding a 20% stake, and about 4,540 bitcoin in daily trading volume, worth close to $298 million at a bitcoin price near $65,700.

It has been a rough month for security teams everywhere. A critical OpenSSH flaw let attackers into Linux servers without a password, the Railway breach saw stolen AI keys rack up $740,000 in fraudulent charges, and the Fireworks AI breach exposed customer datasets and model weights.

What Coinone Customers Should Do Now

Coinone’s advice to customers is blunt. Anyone who shared a password with support should change it — and change it everywhere else they used the same one.

Customers should also treat unexpected calls or messages with suspicion, especially any that mention a past support chat. Coinone warned that scammers may use the leaked details to sound convincing.

Under South Korean privacy law, affected customers may seek damages of up to 3 million won — about $2,245 — when proving actual losses is difficult. That is small comfort for a leaked national ID, but it is one route to compensation.

What Happens Next

The investigation is still running. Coinone says it will publish new findings promptly, and the lookup service will eventually tell each customer exactly what was exposed.

The pattern should worry every company that outsources customer support. The most sensitive data an exchange holds is not always in its trading engine. It is in the chat logs, call notes and ticket histories where customers hand over exactly the details an attacker wants.

Regulators are already moving. The Financial Services Commission’s decision to let exchanges suspend withdrawals when hacking is suspected is a start, but it does nothing for data that has already left the building. Tighter rules on how support vendors store customer records may follow — and other exchanges will be checking their own contractors tonight.

The bigger question is whether three breaches in three weeks will force a deeper change. South Korea’s exchanges have spent years building trust with millions of customers. A support vendor’s server should not be the weakest link in that chain — but this week, it was.

For now, the lesson is an old one. The most dangerous data is not always in the vault. Sometimes it is in the notes taken by the person who answered the phone.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top