DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed15 records · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0pcritical sensitivity
Merged incident · 15 records

cgm — December 2022 breach

Clustered 15 records across 11 jurisdictions: 14 filings and 1 leak-site claim · filing window Jun 7, 2023 → Feb 15, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 records

States

11

Affected · reported

315,346

First → last dated filing

Jun 7, 2023 → Feb 15, 2024

Merge confidence

100%

incident inc_6814574317134bb3 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings and 1 unverified claim. Intrusion Dec 15, 2022–Dec 28, 2022, discovered Dec 15, 2022. 315,346 individuals reported across the linked filings. Data reported: Government ID, Biometric, Identity (basic), and 3 more. Notifications rolled out on a 253-day schedule across 13 dated filings beginning Jun 7, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
368days

Range of discovered_at dates across filings

Filing span
253days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksWashington✗ WA AG >90dLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 161dFull clock table in Litigation Timeline

Sensitive data

biometricidentity_government

Incident timeline

Dec 15, 2022breach begins
Dec 15, 2022discovered · members disagree
Jun 7, 2023first dated filing
Feb 15, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JAN 5Leak sitecl0p postfirst record · attacker claim · unverifiedday 0
  3. JUN 7WA AGWA AG notice4,174 WA residents+153d
  4. JUN 7IN AGIN AG noticestates nationwide total 279,063+153d
  5. JUN 7OR AGOR AG noticestates nationwide total 279,063+153d
  6. JUN 7VT AGVT AG noticeno count stated+153d
  7. JUN 7CA AGCA AG noticeno count stated+153d
  8. JUN 7ME AGME AG noticestates nationwide total 279,063+153d
  9. JUN 7MA AGMA AG notice774 MA residents+153d
  10. JUN 12NH AGNH AG notice2 NH residents+158d
  11. FEB 14MT AGMT AG notice4 MT residents+405d
  12. FEB 14CA AGCA AG noticeno count stated+405d
  13. FEB 14NH AGNH AG notice4 NH residents+405d
  14. FEB 14ME AGME AG noticestates nationwide total 315,346+405d
  15. FEB 15SC AGSC AG noticemost recent · 1,412 SC residents+406d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 15, 2022 – Dec 28, 2022
WA AG
Discovered
Dec 15, 2022IL AGDec 28, 2022WA AG + VT AG + CA AG +3May 18, 2023OR AG + ME AGDec 18, 2023ME AGfilings disagree on discovery
Data types
Biometric · Financial account · Health (basic) · Identity (basic) · Government ID · PII
WA AG + VT AG + CA AG +5
Attack vector
Ransomware
WA AG

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)

315,346

Sum of filed state slices

15,136· 4.8% of stated

95% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US315,346
IN8,766
WA4,174
SC1,412
MA774
NH4
MT4
ME2

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

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing14 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 2026 · at least one link edge was human-adjudicated
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

253 days

Cadence

~1 / 21.1d

vs. multi-state median

42.2× 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.