Skip to content
coinchoose
Menu

Exchanges guide

The Coinbase Data Breach Explained: What Leaked and How to Protect Yourself

In May 2025 attackers bribed Coinbase support contractors to steal customer data. Here is what leaked, what stayed safe, and how to protect yourself.

On this page
  1. What happened in the Coinbase data breach?
  2. What data leaked, and what stayed safe?
  3. How did the attackers get the data?
  4. How many users were affected?
  5. How did Coinbase respond to the extortion?
  6. Coinbase data breach timeline
  7. What scams should you watch for after the leak?
  8. What should users do now?
  9. Was the October 2026 vendor exposure the same breach?
  10. Will Coinbase refund affected users?
  11. Is Coinbase safe to use now?
  12. FAQ
  13. Source register

In May 2025, criminals bribed Coinbase customer-support contractors working outside the United States to pull personal data from the company’s internal support tools, then demanded US$20 million to keep it private. Coinbase refused, disclosed the incident in a US Securities and Exchange Commission filing on 15 May 2025, and said less than 1% of monthly transacting users were affected. No passwords, private keys, or customer funds were taken, so the main risk for users now is follow-up phishing and impersonation that uses the leaked contact details.

What happened in the Coinbase data breach?

On 11 May 2025 Coinbase received an email from an unknown threat actor claiming to hold data on certain customer accounts plus internal documents covering customer-service and account-management systems, and demanding money to keep the material private. The attacker had obtained the data by paying support contractors and employees outside the US to pull it from systems they used in their jobs. Coinbase had already spotted the improper access through its own security monitoring in the preceding months, fired the people involved, and referred the matter to law enforcement.

Coinbase set out the sequence in a Form 8-K filed under Item 1.05, the SEC item for material cybersecurity incidents. The company said the earlier instances of improper access were part of a single campaign, that it had not paid the threat actor’s demand, and that it was cooperating with law enforcement. The extortion email arrived on 11 May 2025, and the filing was signed by chief financial officer Alesia J. Haas on 15 May 2025.

This was an insider breach involving unauthorized access to Coinbase’s internal support systems, including customer-service and account-management tools, a framing echoed by TechCrunch‘s 15 May 2025 report that the company said its systems had been breached. Coinbase’s trading and custody systems were not reported as compromised, and its customer-facing platforms, including Coinbase Advanced (formerly Coinbase Pro), were not the source of the stolen data. Our guide to choosing an exchange explains the checks to run on any platform.

What data leaked, and what stayed safe?

Coinbase’s SEC filing lists the exposed fields: names, addresses, phone numbers and email addresses; Social Security numbers masked to the last four digits; masked bank-account numbers and some bank identifiers; government-ID images such as driving licences and passports; and account data including balance snapshots and transaction history. What did not leak matters more: passwords, private keys, and customer funds were never accessed, and no targeted contractor could move customer money.

What was exposed What was not exposed
Names, addresses, phone numbers, emails Passwords and login credentials
Social Security numbers (last four digits only) Private keys and seed phrases
Masked bank-account numbers and bank identifiers Two-factor authentication codes
Government-ID images (driving licence, passport) Customer funds (no contractor could access them)
Account balance snapshots and transaction history Coinbase Prime accounts
Limited corporate data available to support agents Coinbase’s trading and custody systems

Because login details and keys were never taken, this was not an account-takeover breach. The value of the stolen data is that it makes scams look authentic: a caller who knows your name, the last four digits of your Social Security number, and a recent balance can be very convincing. CoinDesk confirmed two-factor codes were not compromised, and The Block reported that Coinbase Prime accounts were unaffected.

How did the attackers get the data?

The breach was an insider job, not a software vulnerability. Coinbase’s 8-K states the data was obtained by paying multiple contractors or employees working in support roles outside the United States to pull information from internal tools they legitimately used for their jobs. Coinbase’s own monitoring detected the improper accesses in the previous months, and the company concluded the separate accesses were one coordinated campaign.

This is why Coinbase framed it as a failure of human trust and internal controls rather than a technical exploit, a characterisation echoed by Exterro‘s breakdown of the incident. A small number of people with legitimate support access were bribed to misuse it.

How many users were affected?

Coinbase’s public figure is less than 1% of monthly transacting users, and it did not publish an exact headcount in its SEC filing. A mandatory filing with the Maine Attorney General, reported by SecurityWeek in May 2025, put the number at 69,461 customers nationwide, consistent with that percentage. The exposed data was partly masked, which limits identity-theft risk but does not stop phishing.

The Block reported Coinbase’s own wording of less than 1% of monthly users, and SecurityWeek reported that a Maine Attorney General filing pinned the number at 69,461 customers nationwide. The ClassAction.org investigation page repeats the less than 1% figure and shows that affected users have been solicited for mass arbitration rather than a class action, so you may be contacted by law firms after a notice of this kind.

The identifiers were masked, not full: the Social Security number leaked as the last four digits only, and bank account numbers were masked. That limits the identity-theft exposure compared with a full-record leak, but the contact details and account activity are enough to power convincing social-engineering attempts.

Coinbase’s 8-K says it warned potentially affected customers, and the company notifies users from a coinbase.com address when their information is involved. If you think you were affected, log in at coinbase.com directly and check your account notifications rather than trusting an inbound message.

How did Coinbase respond to the extortion?

Coinbase refused the $20 million demand and converted it into a $20 million reward for information leading to the arrest and conviction of those responsible. It fired the contractors involved, referred them to US and international law enforcement, added fraud-monitoring safeguards, and said it would open a new US-based support hub and reimburse customers tricked into sending funds.

The threat actor demanded $20 million in bitcoin to keep the data private, and Coinbase’s 8-K states it has not paid the threat actor’s demand. The company instead announced a $20 million bounty for information leading to an arrest, with tips directed to [email protected].

The 8-K also lists the operational response: firing the personnel involved, adding fraud-monitoring safeguards, warning potentially affected customers, opening a new US support hub, and hardening its defenses. Coinbase said it would aggressively pursue all remedies against those responsible.

The bounty and the reimbursement commitment together set this incident apart from the quieter handling of many insider breaches. Coinbase made the demand public, put a price on identifying the attackers, and promised to make whole customers who were tricked into sending funds as a direct result of the incident.

Coinbase data breach timeline

Three dates anchor the 2025 incident: the extortion email arrived on 11 May 2025, the earliest event in the SEC filing was 14 May 2025, and Coinbase filed the 8-K and published its public statement on 15 May 2025. A separate, unrelated vendor exposure followed in late October 2026.

Date Event Source
Previous months Coinbase security monitoring independently detects improper access to customer data by support contractors and employees outside the US; personnel are fired SEC 8-K
11 May 2025 Unknown threat actor emails Coinbase demanding payment to keep stolen customer data private SEC 8-K, CoinDesk
14 May 2025 Date of earliest event reported in Coinbase’s Form 8-K (Item 1.05) SEC 8-K
15 May 2025 8-K signed by CFO Alesia J. Haas and filed; Coinbase publishes its blog statement and announces the $20m bounty after refusing the $20m demand SEC 8-K, The Block
27-28 October 2026 Coinbase confirms a separate incident at Amplitude exposed contact information and limited transaction data for a small subset; funds safe and no unauthorized access to Coinbase systems CoinDesk, Unchained

Media reports on 2 June 2025 linked the bribery to customer-support work in India and named outsourcing vendor TaskUs. I could not open the primary source behind those reports, so the location and vendor are described only as outside the United States, the wording used in Coinbase’s own filing.

What scams should you watch for after the leak?

The leaked details power three recurring scams: fake support calls and texts that quote your account data to seem real, a withdrawal-code text that asks you to approve a transfer you never made, and phishing emails that copy Coinbase notices to steal your login. None can move funds unless you act, so pausing and verifying is the defence.

First, impersonation. A caller may know your name, phone number, and even a masked identifier, and claim your account is at risk so you should move funds to a safe wallet or read back a code. Genuine support staff will not do this.

Second, the withdrawal-code text, where you receive a code you did not request followed by a call from a fake agent asking you to read it back. Reading it back can approve the attacker’s withdrawal. Our page on the Coinbase withdrawal-code text scam walks through the exact sequence.

Third, phishing emails and texts that imitate account-locked or verify-your-identity notices, linking to fake login pages. The same tactics appear across crypto scams, including free Bitcoin offers that harvest credentials. The standing rule, from Stoltmann Law‘s guidance for victims, is to not provide codes, do not send crypto, and preserve the evidence.

What should users do now?

Because no passwords, keys, or funds were taken, the realistic threat is a scammer who uses your leaked details to sound legitimate over email, text, or phone. Treat unexpected Coinbase contact as suspicious, never share a code or send crypto to a support agent, move from SMS to an authenticator app or hardware key, and lock your account the moment anything feels off.

  1. Assume follow-up contact is hostile. Your name, address, phone, email, the last four of your Social Security number, and account activity may be in the attacker’s hands, so a caller quoting them proves nothing.
  2. Never hand over your password, a two-factor code, or a seed phrase, and never send funds to an address a support agent gives you. No genuine Coinbase representative will ask for these. Learn how to store a seed phrase so it never gets shared by accident.
  3. Switch off SMS two-factor authentication and use an authenticator app or a hardware security key instead, because SMS can be intercepted through a SIM swap.
  4. Verify senders and URLs, and log in only by typing coinbase.com yourself rather than clicking links in unexpected messages.
  5. If anything feels wrong, lock your account immediately in the app or at coinbase.com, then report through Coinbase’s official site or app rather than a number in a suspicious message.
  6. Preserve evidence: keep the emails, texts, call logs, voicemails, and screenshots, and download your Coinbase account activity and support tickets.
  7. If you lost money because of this specific incident, Coinbase’s 8-K says it intends to voluntarily reimburse eligible retail customers who sent funds to the threat actor as a direct result, after confirming the facts.
  8. Watch your accounts and credit. The leaked identifiers were masked, but monitor your bank statements, turn on account alerts, and consider a fraud alert on your credit file if your government ID image was among the exposed data.

Steps 2 through 6 track the guidance Stoltmann Law published for victims of this breach. For holdings you plan to keep long term, moving them into a wallet you control removes them from the exchange-phishing vector, a trade-off covered in our page on whether to keep crypto on an exchange.

Was the October 2026 vendor exposure the same breach?

No. In late October 2026 a separate incident at Amplitude, a third-party analytics provider, exposed contact information and limited transaction data for a small subset of Coinbase customers, a Coinbase spokesperson told Unchained. Coinbase said the exposed data did not include home addresses or anything that would let someone directly access an account, that it found no evidence of unauthorized access to Coinbase systems, and that customer funds were not impacted. The full scope of the exposure was not publicly disclosed. This is distinct from the May 2025 support-contractor breach.

May 2025 support-contractor breach October 2026 Amplitude exposure
What happened Bribed support contractors pulled data from internal tools Third-party analytics provider Amplitude exposed contact data
Data involved Names, addresses, masked IDs, balances, transaction history Contact information and limited transaction data (a small subset)
Funds at risk No, funds and private keys were never accessed No, customer funds are safe
Disclosed SEC 8-K and blog post, 15 May 2025 Coinbase Support statement, late October 2026

The two events are separate. The October 2026 incident occurred on Amplitude’s side, and Coinbase said it found no evidence of unauthorized access to Coinbase systems and that “Coinbase has not had a data breach”, as reported by Unchained. If you received a notice in late 2026 about contact or transaction data, that is the Amplitude event, not the 2025 breach.

Will Coinbase refund affected users?

Coinbase committed in its 8-K to voluntarily reimburse eligible retail customers who sent funds to the threat actor as a direct result of the May 2025 incident, after completing a review to confirm the facts. This is specific to the breach and differs from refunds for an ordinary account takeover, which depend on how the account was compromised.

The filing says Coinbase intends to voluntarily reimburse eligible retail customers who previously sent funds to the threat actor as a direct result of this incident. It also set the preliminary financial impact at approximately $180 million to $400 million for remediation costs and voluntary customer reimbursements, before review of potential losses, indemnification claims, and recoveries, and cautioned the estimate could meaningfully increase or decrease.

If you believe you lost money because of this incident, report it through Coinbase’s official site or app and keep your transaction records and correspondence. See our page on whether Coinbase is safe for the platform’s broader security picture.

Is Coinbase safe to use now?

Yes, with one important distinction: the May 2025 incident involved unauthorized access to Coinbase’s internal support systems, but no customer funds or private keys were taken in either the 2025 or 2026 incidents, and Coinbase added fraud-monitoring safeguards and a new US-based support hub afterwards. The danger that remains is social engineering aimed at you, which is why your own verification habits matter more than any exchange feature.

Coinbase’s 8-K said there had been no material operational impacts and that it would aggressively pursue all remedies. As of November 2026 the platform continues to operate, and its US entity is a publicly traded company that files cybersecurity disclosures with the SEC, which is one reason this incident was documented in unusual detail.

None of this removes the need for basic hygiene: use an authenticator app or hardware key, do not reuse passwords, and never share codes or seed phrases. Our guide to choosing an exchange and our page on keeping crypto on an exchange cover the trade-offs in more detail.

Crypto assets are volatile and this is not financial advice.

FAQ

Did Coinbase get hit with a major breach?

Yes. In May 2025 Coinbase disclosed that criminals bribed customer-support contractors outside the United States to steal customer data from its internal support tools, affecting less than 1% of monthly transacting users. No passwords, private keys, or customer funds were taken, and Coinbase refused the attackers’ $20 million extortion demand.

How do I know if a Coinbase text is real?

Genuine Coinbase messages come from coinbase.com and its verified subdomains, and no Coinbase representative will ask for your password, two-factor code, or seed phrase, or tell you to move funds to a new address. If a text asks for any of these or pressures you to act fast, treat it as a scam and report it through the official Coinbase site or app.

Will Coinbase refund me if my account is hacked?

For the May 2025 incident, Coinbase’s SEC filing commits it to voluntarily reimburse eligible retail customers who sent funds to the threat actor as a direct result of the breach, after confirming the facts. Refunds for an ordinary account takeover depend on how the account was compromised and are not automatic.

Is it safe to use Coinbase right now?

Yes. The May 2025 incident involved unauthorized access to Coinbase’s internal support systems, but no customer funds or private keys were taken in either the 2025 or 2026 incidents, and Coinbase has added fraud-monitoring safeguards and a US-based support hub. The realistic risk is phishing that uses leaked contact details, so use an authenticator app or hardware key and never share codes.

How do I check if my Coinbase data was exposed?

Coinbase said it notified customers potentially affected by the 2025 breach, and it separately confirmed the Amplitude exposure in October 2026. Watch for an official notice from a coinbase.com address, and log in at coinbase.com directly to review recent activity and support messages rather than following links in emails or texts.

Was there another Coinbase data breach in 2026?

In late October 2026 a separate incident at Amplitude, a third-party analytics provider, exposed email addresses and phone numbers for a small subset of Coinbase customers. Coinbase said customer funds were safe and its own systems showed no unauthorized access. This is distinct from the May 2025 support-contractor breach.

Source register

  1. 01SEC: Coinbase Global, Inc. Form 8-K (Item 1.05 cybersecurity incident)sec.gov
  2. 02The Block: Coinbase offers $20 million bounty on data thieves who tried to extort exchangetheblock.co
  3. 03CoinDesk: Coinbase Says Criminals Stole Customer Data, Offers $20M Bug Bountycoindesk.com
  4. 04CoinDesk: Coinbase says user funds are safe after vendor exposes customer datacoindesk.com
  5. 05Unchained: Coinbase ties customer contact data exposure to vendor Amplitudeunchainedcrypto.com
  6. 06SecurityWeek: Coinbase Says Rogue Contractor Data Breach Affects 69,461 Userssecurityweek.com
  7. 07TechCrunch: Coinbase says customers' personal information stolen in data breachtechcrunch.com
  8. 08Exterro: Insider Bribery Leads to Major Coinbase Data Breachexterro.com
  9. 09ClassAction.org: Coinbase Data Breach Legal Investigationclassaction.org
  10. 10Stoltmann Law: Coinbase Data Breach. What Victims Need to Knowstoltmannlaw.com
  11. 11SEC EDGAR: Coinbase Global, Inc. 8-K filing indexsec.gov

Last updated Spotted an error? Send a correction

About the author

CoinChoose Editorial Team

How CoinChoose researches and checks pages