DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed12 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 12 filings

SAG-AFTRA Health Plan — September 2024 breach

Clustered 12 filings across 9 jurisdictions · filing window Dec 1, 2024 → Mar 14, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

9

Affected · reported

98,474

First → last filing

Dec 1, 2024 → Mar 14, 2025

Merge confidence

100%

incident inc_b557dda52c3b43f8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. Intrusion Sep 17, 2024–Sep 18, 2024, discovered Sep 17, 2024 — the first regulatory filing landed 75 days later (flagged late). 98,474 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 103-day schedule across 12 filings beginning Dec 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
75days

Discovered → first regulatory filing

Discovery variance
143days

Range of discovered_at dates across filings

Filing span
103days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayWashington✗ WA AG >90dMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 17, 2024breach begins
Sep 17, 2024discovered · members disagree
notification delay · 75 days
Dec 1, 2024first filing
Mar 14, 2025most 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. DEC 1IL AGIL AG noticefirst filing · no count statedday 0
  2. DEC 2MA AGMA AG notice991 MA residents+1d
  3. DEC 2NE AGNE AG noticeno count stated+1d
  4. DEC 2HHS OCRHHS OCR noticestates nationwide total 98,474+1d
  5. DEC 2NH AGNH AG notice38 NH residents+1d
  6. DEC 2MT AGMT AG notice60 MT residents+1d
  7. DEC 2CA AGCA AG noticeno count stated+1d
  8. MAR 14CA AGCA AG noticeno count stated+103d
  9. MAR 14NH AGNH AG notice112 NH residents+103d
  10. MAR 14OR AGOR AG noticestates nationwide total 95,104+103d
  11. MAR 14VT AGVT AG noticeno count stated+103d
  12. MAR 14WA AGWA AG noticemost recent · 937 WA residents+103d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 17, 2024 – Sep 18, 2024
NE AG
Discovered
Sep 17, 2024IL AGSep 18, 2024NH AG + MT AG + CA AG +2Oct 3, 2024NE AGFeb 7, 2025OR AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
MA AG + HHS OCR + MT AG +4
Attack vector
Unauthorized Access
HHS OCR

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)

98,474

Sum of filed state slices

2,100· 2.1% of stated

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

US98,474
MA991
WA937
NH112
MT60

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing12 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
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

103 days

Cadence

~1 / 9.4d

vs. multi-state median

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