DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed9 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 9 filings

CareSource — May 2023 breach

Clustered 9 filings across 8 jurisdictions · filing window Jan 1, 2023 → Aug 30, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

3,180,537

First → last filing

Jan 1, 2023 → Aug 30, 2023

Merge confidence

100%

incident inc_5cd6afdd15924178 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. Intrusion May 30, 2023–May 31, 2023, discovered May 31, 2023. 3,180,537 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 1 more. Notifications rolled out on a 241-day schedule across 8 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
27days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 179d

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
241days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont⏱ VT AG >14 bdayLeak gap⏱ Leak >30dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 30, 2023breach begins
May 31, 2023discovered · members disagree
Jan 1, 2023first filing
Aug 30, 2023most 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. JUN 29Leak sitecl0p postattacker claim · unverified+179d
  3. JUL 18NH AGNH AG notice6 NH residents+198d
  4. JUL 27HHS OCRHHS OCR noticestates nationwide total 3,180,537+207d
  5. AUG 25VT AGVT AG noticeno count stated+236d
  6. AUG 28CA AGCA AG noticeno count stated+239d
  7. AUG 28MA AGMA AG notice389 MA residents+239d
  8. AUG 30WA AGWA AG notice581 WA residents+241d
  9. AUG 30NH AGNH AG noticemost recent · 70 NH residents+241d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2023
NH AG
Discovered
May 31, 2023IL AGJun 1, 2023NH AGJun 27, 2023VT AG + CA AG + WA AG +1filings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI
NH AG + HHS OCR + VT AG +3
Attack vector
Third-Party / Supply Chain
NH 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)

3,180,537

Sum of filed state slices

1,040· 0.0% of stated

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

US3,180,537
WA581
MA389
NH70

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 filing8 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

241 days

Cadence

~1 / 30.1d

vs. multi-state median

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