DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed11 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

Ascension Health Alliance — December 2023 breach

Clustered 11 filings across 9 jurisdictions · filing window Dec 19, 2024 → Feb 7, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

5,599,699

First → last dated filing

Dec 19, 2024 → Feb 7, 2025

Merge confidence

100%

incident inc_7ef1e178692c41ec · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Dec 30, 2023–Jun 11, 2024, discovered Dec 30, 2023. 5,599,699 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 50-day schedule across 10 dated filings beginning Dec 19, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
130days

Range of discovered_at dates across filings

Filing span
50days

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 clocksWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 225dOregon✗ OR AG >45dMaine⏱ ME AG >30d · 225dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 30, 2023breach begins
Dec 30, 2023discovered · members disagree
Dec 19, 2024first dated filing
Feb 7, 2025most 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 about this breach

  1. DEC 1IL AGIL AG noticefiling day not on record · no count stated—
  2. DEC 19OR AGOR AG noticefirst filing · states nationwide total 5,599,699day 0
  3. DEC 19ME AGME AG noticestates nationwide total 5,599,699day 0
  4. DEC 19DE AGDE AG noticestates nationwide total 5,599,699day 0
  5. DEC 19WA AGWA AG notice5,787 WA residentsday 0
  6. DEC 19MT AGMT AG notice4,568 MT residentsday 0
  7. DEC 19CA AGCA AG noticeno count statedday 0
  8. DEC 19MA AGMA AG notice2,632 MA residentsday 0
  9. FEB 3OR AGOR AG noticestates nationwide total 5,466,931+46d
  10. FEB 3CA AGCA AG noticeno count stated+46d
  11. FEB 7NH AGNH AG noticemost recent · states nationwide total 5,466,931+50d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 7, 2024 – May 8, 2024
ME AG
Discovered
Dec 30, 2023DE AGMay 7, 2024IL AGMay 8, 2024ME AG + WA AG + CA AG +1filings disagree on discovery
Data types
Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI
ME AG + DE AG + WA AG +2
Attack vector
Ransomware
ME 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)

5,599,699

Sum of filed state slices

14,896· 0.3% of stated

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

US5,599,699
WA5,787
MT4,568
MA2,632
ME658
NH645
DE606

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 filing11 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
Reviewed
operator-reviewed Jun 12, 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

50 days

Cadence

~1 / 5.6d

vs. multi-state median

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