DisclosureLens
Leak SiteState AGConfirmed14 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0pcritical sensitivity
Merged incident · 14 filings

cgm — December 2022 breach

Clustered 14 filings across 12 jurisdictions · filing window Jan 1, 2023 Feb 15, 2024. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

14 filings

States

11

Affected · reported

279,063

First → last filing

Jan 1, 2023 Feb 15, 2024

Merge confidence

100%

incident inc_6814574317134bb3 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings and 1 unverified claim. Intrusion Dec 15, 2022–Dec 28, 2022, discovered Dec 15, 2022 — the first regulatory filing landed 17 days later (flagged late). 279,063 individuals reported across the linked filings. Data reported: Government ID, Biometric, Identity (basic), and 3 more. Notifications rolled out on a 410-day schedule across 13 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
17days

Discovered → first regulatory filing

Discovery variance
154days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 4d

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
410days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksLeak 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
notification delay · 17 days
Jan 1, 2023first filing
Feb 15, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JAN 5Leak sitecl0p postattacker claim · unverified+4d
  3. JUN 7WA AGWA AG notice4,174 WA residents+157d
  4. JUN 7IN AGIN AG noticestates nationwide total 279,063+157d
  5. JUN 7OR AGOR AG noticestates nationwide total 279,063+157d
  6. JUN 7VT AGVT AG noticeno count stated+157d
  7. JUN 7CA AGCA AG noticeno count stated+157d
  8. JUN 7ME AGME AG noticestates nationwide total 279,063+157d
  9. JUN 7MA AGMA AG notice774 MA residents+157d
  10. JUN 12NH AGNH AG notice2 NH residents+162d
  11. FEB 14CA AGCA AG noticeno count stated+409d
  12. FEB 14NH AGNH AG notice4 NH residents+409d
  13. FEB 14MT AGMT AG notice4 MT residents+409d
  14. FEB 15SC AGSC AG noticemost recent · 1,412 SC residents+410d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 15, 2022Dec 28, 2022
WA AG
Discovered
Dec 15, 2022IL AGDec 28, 2022WA AG + VT AG + CA AG +3May 18, 2023OR AG + ME 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)

279,063

Sum of filed state slices

15,135· 5.4% of stated

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

US279,063
IN8,766
WA4,174
SC1,412
MA774
NH4
MT4
ME1

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 filing13 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 Aug 25, 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

410 days

Cadence

~1 / 31.5d

vs. multi-state median

45.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.