Coinbase reported a data breach to the California Attorney General and the Washington Attorney General. The 2 notices were filed on May 20, 2025. Coinbase also filed a Form 8-K under Item 1.05 (Material Cybersecurity Incidents) disclosing a cybersecurity incident to the US Securities and Exchange Commission on May 15, 2025. Breach dates in the filings run from December 26, 2024 to May 5, 2025. The Washington filing says the organization became aware of it on May 11, 2025. The Washington filing puts the number of Washington residents affected at 3,337. The Washington filing lists the cause as "Cyberattack: Other". The Washington filing lists the information involved as: names, driver's license or state id numbers, dates of birth, passport numbers.
- Breach dated
- December 26, 2024 to May 5, 2025
- Discovered
- May 11, 2025
- Latest filing
- May 20, 2025
Figures on record
This figure counts only the group named beside it.
Cause on record
Cyberattack, type listed by Washington as “Other”.
Data exposed, as the sources list it
- names
- driver's license or state id numbers
- dates of birth
- passport numbers
The records behind this entry
Form 8-K Item 1.05 filed with the SEC under the name Coinbase Global, Inc.
In the company's own words, from its Form 8-K under Item 1.05 (Material Cybersecurity Incidents) On May 11, 2025, Coinbase, Inc., a subsidiary of Coinbase Global, Inc. (“Coinbase” or the “Company”), received an email communication from an unknown threat actor claiming to have obtained information about certain Coinbase customer accounts, as well as internal Coinbase documentation, including materials relating to customer-service and account-management systems. The communication demanded money in exchange for not publicly disclosing the information.
Show the rest of this text (467 more words)Hide the rest of this text
The threat actor appears to have obtained this information by paying multiple contractors or employees working in support roles outside the United States to collect information from internal Coinbase systems to which they had access in order to perform their job responsibilities. These instances of such personnel accessing data without business need were independently detected by the Company’s security monitoring in the previous months. Upon discovery, the Company had immediately terminated the personnel involved and also implemented heightened fraud-monitoring protections and warned customers whose information was potentially accessed in order to prevent misuse of any compromised information. Since receipt of the email, the Company has assessed the email to be credible, and has concluded that these prior instances of improper data access were part of a single campaign (the “Incident”) that succeeded in taking data from internal systems. The Company has not paid the threat actor’s demand and is cooperating with law enforcement in the investigation of this Incident.
The Incident did not involve the compromise of passwords or private keys, and at no time were any of the targeted contractors or employees able to access customer funds. While the Company is still investigating the affected data, it included:
•Name, address, phone, and email;
•Masked Social Security (last 4 digits only);
•Masked bank-account numbers and some bank account identifiers;
•Government‑ID images (e.g., driver’s license, passport);
•Account data (balance snapshots and transaction history); and
•Limited corporate data (including documents, training material, and communications available to support agents).
The Company is continuing to review and bolster its anti-fraud protections to mitigate the risk that the compromised information could be used in social-engineering attempts. To the extent any eligible retail customers previously sent funds to the threat actor as a direct result of this Incident, the Company intends to voluntarily reimburse them after it completes its review to confirm the facts. The Company is also in the process of opening a new support hub in the United States and taking other measures to harden its defenses to prevent this type of incident.
While Coinbase has not experienced material operational impacts from these events as of the date hereof, the full financial impact of the Incident on the Company is still in the process of being assessed. Based on the information available to the Company on the date hereof and based on facts that continue to evolve, the Company has preliminarily estimated expenses to be within the range of approximately $180 million to $400 million relating to remediation costs and voluntary customer reimbursements relating to this Incident, prior to further review of potential losses, indemnification claims, and potential recoveries, which could meaningfully increase or decrease this estimate. The Company plans to aggressively pursue all remedies. As the Company’s investigation is ongoing, the full impact of these events are not yet known.
Breach notice filed with the California Attorney General under the name Coinbase, Inc.
On this record: breach dated Dec 26, 2024.
Breach notice filed with the Washington Attorney General under the name Coinbase, Inc.
On this record: 3,337 Washington residents; cause given as “Cyberattack: Other”; breach dated Dec 26, 2024 to May 5, 2025; discovered May 11, 2025.
This record lists these kinds of data: names; driver's license or state id numbers; dates of birth; passport numbers.
- Open this record at atg.wa.gov
- Notice letter filed with the Washington Attorney General (PDF) at agportal-s3bucket.s3.amazonaws.com
What to do if this involved you
Consider a credit freeze
A freeze stops new credit being opened in your name. It is free, and you place it yourself with each of the three US credit bureaus: Equifax, Experian and TransUnion. You can check your credit reports for free as well.
These steps follow from the kinds of data the sources list. If you have a notice letter, start with the letter.