Coinbase — overseas-contractor breach
Attackers bribed overseas Coinbase customer-support contractors to extract internal data on a subset of customers; Coinbase refused a $20M ransom and offered a counter-bounty.
- Target
- Coinbase — overseas-contractor breach
- Date public
- 15 May 2025
- Sector
- Financial Services
- Attack type
- Insider
- Threat actor
- Bribed overseas customer-support contractors
- Severity
- High
- Region
- Global
In May 2025 Coinbase disclosed that attackers had recruited and bribed customer-support contractors employed by Coinbase’s overseas business-process-outsourcing partners to extract internal customer data on a subset of high-net-worth users. The data taken included names, addresses, dates of birth, masked Social Security numbers, masked bank-account numbers, government-ID images and account balances, but did not include passwords, two-factor authentication codes, or wallet seed phrases. Coinbase confirmed in its 8-K filing that no customer funds had been stolen.
The attackers attempted to extort Coinbase for $20 million, threatening public disclosure. Coinbase publicly refused to pay, fired the implicated contractors, terminated relationships with the affected outsourcers, and offered a parallel $20 million bounty for information leading to the attackers’ arrest. The company disclosed estimated remediation and reimbursement costs of $180-400 million in the same filing. The incident is studied as a textbook example of the insider-recruitment threat against the customer-support tier of large financial-services platforms — the same channel exploited at Robinhood (2021), Twilio (2022), and many others.
Controls that would have helped
Defender controls catalogued in the Controls Desk that would have changed the outcome of this incident, or limited its blast radius. Sourced from regulator and framework guidance — never vendors.
- Phishing-resistant MFA on every privileged account Hardware keys or platform authenticators on admin, cloud-root, HR-system, CRM and customer-data accounts. SMS one-time codes do not count as MFA against a serious adversary.
- Disable legacy authentication on cloud tenants Basic auth and other legacy authentication protocols bypass MFA. The configuration is a tenant-level switch and the standards bodies have wanted it flipped for years.
Sources
- Coinbase 8-K filing — May 2025 // primary
- Coinbase blog — protecting our customers // primary