{"id":432,"date":"2025-05-19T15:06:53","date_gmt":"2025-05-19T15:06:53","guid":{"rendered":""},"modified":"2025-06-03T13:38:11","modified_gmt":"2025-06-03T13:38:11","slug":"400m-coinbase-hack-the-case-for-zktls-decentralized-id","status":"publish","type":"post","link":"https:\/\/ont.io\/news\/400m-coinbase-hack-the-case-for-zktls-decentralized-id\/","title":{"rendered":"$400M Coinbase Hack: The Case for zkTLS & Decentralized ID"},"content":{"rendered":"

Could Coinbase\u2019s $400 Million Data Breach Have Been Prevented With zkTLS and Decentralized Identity?<\/span><\/h2>\n

On 15 May 2025, Coinbase disclosed a breach that exposed personal data from nearly 1 percent of its 100 million users. Attackers bribed support agents and accessed identity documents, contact information, and account metadata. Estimated losses could reach 400 million dollars. The hackers demanded 20 million dollars in Bitcoin. Coinbase refused and offered the same amount as a bounty for leads.<\/span><\/p>\n

The damage goes far beyond this single event. Even without private key theft, stolen personal data enables phishing, KYC bypass, and SIM-swap attacks that can compromise users for years to come.<\/span><\/p>\n

What Happened? A Quick Timeline<\/span><\/h2>\n

<\/p>\n\n\n\n\n\n\n\n
Date<\/td>\nEvent<\/td>\n<\/tr>\n
Early May<\/td>\nSupport agents bribed, ID data extracted<\/td>\n<\/tr>\n
11 May<\/td>\nRansom note sent<\/td>\n<\/tr>\n
15 May<\/td>\nDisclosure filed with SEC and published in blog post<\/td>\n<\/tr>\n
16 May<\/td>\nCoinbase pledges to reimburse victims and posts 20 million dollar bounty<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Even though private keys were untouched, the leak included data that makes phishing almost impossible to detect. The real threat is not immediate wallet drain but long-term identity compromise.<\/span><\/p>\n

Why Traditional Defenses Failed<\/span><\/h2>\n