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

Yale New Haven Health Services Corporation — November 2023 breach

Clustered 3 filings across 2 jurisdictions · filing window Aug 9, 2024 → Dec 26, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

2

Affected · reported

5

First → last filing

Aug 9, 2024 → Dec 26, 2024

Merge confidence

100%

incident inc_033c1b7d256e4b36 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe unauthorized access. Intrusion Nov 10, 2023–Nov 30, 2023, discovered Dec 4, 2023 — the first regulatory filing landed 249 days later (flagged late). 5 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 139-day schedule across 3 filings beginning Aug 9, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
249days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
139days

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 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 10, 2023breach begins
Dec 4, 2023discovered
notification delay · 249 days
Aug 9, 2024first filing
Dec 26, 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. AUG 9VT AGVT AG noticefirst filing · no count statedday 0
  2. AUG 19NH AGNH AG notice5 affected+10d
  3. DEC 26NH AGNH AG noticemost recent · no count stated+139d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 10, 2023 – Nov 30, 2023
VT AG
Discovered
Dec 4, 2023· 24d undetected
VT AG + NH AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
VT AG + NH AG
Attack vector
Unauthorized Access
VT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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

139 days

Cadence

~1 / 69.5d

vs. multi-state median

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