COINBASE, INC. — December 2024 breach
Clustered 10 filings across 10 jurisdictions · filing window May 1, 2025 → May 30, 2025. View entity profile → Other incidents for this victim →
incident inc_bbcd0d43a0374cd6 · merged by deterministic · confidence 100%
Litigation Timing
SupplementalRange of discovered_at dates across filings
Materiality determination to SEC 8-K filing
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta — no leak-site claim in this cluster.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- MAY 1IL AGIL AG noticefirst filing · no count statedday 0
- MAY 15SEC 8-KSEC 8-K noticeno count stated+14d
- MAY 20WA AGWA AG notice3,337 WA residentsauto-linked+19d
- MAY 20CA AGCA AG noticeno count statedauto-linked+19d
- MAY 20MT AGMT AG notice160 MT residentsauto-linked+19d
- MAY 20ME AGME AG noticestates nationwide total 69,461auto-linked+19d
- MAY 20MA AGMA AG notice2,050 MA residentsauto-linked+19d
- MAY 27NH AGNH AG notice454 NH residentsauto-linked+26d
- MAY 30IN AGIN AG noticestates nationwide total 69,461auto-linked+29d
- MAY 30NE AGNE AG noticemost recent · no count statedauto-linked+29d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Dec 26, 2024 – May 5, 2025 WA AG
- Discovered
- May 11, 2025· 136d undetected IL AG + WA AG + ME AG +1
- Data types
- Financial · Financial account · Identity (basic) · Government ID · PII IL AG + SEC 8-K + WA AG +6
- Attack vector
- Insider SEC 8-K
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Count reconciliation
per-state reported counts
Nationwide (stated in a filing)
69,461
Sum of filed state slices
6,506· 9.4% of stated
91% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
29 days
Cadence
~1 / 3.2d
vs. multi-state median
3.6× slower
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.
The weekly clock on records like this one
The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.
Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.