All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed5 filings · 4 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 5 filings

VITAS Hospice Services, LLC — September 2025 breach

Clustered 5 filings across 4 jurisdictions · filing window Nov 1, 2025 → Nov 24, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

319,177

First → last filing

Nov 1, 2025 → Nov 24, 2025

Merge confidence

100%

incident inc_2b5db5a100dd4c0a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe hacking. Intrusion Sep 21, 2025–Oct 27, 2025, discovered Oct 24, 2025 — the first regulatory filing landed 8 days later. 319,177 individuals reported across the linked filings. Data reported: Government ID, Health (basic), PII, and 2 more. Notifications rolled out on a 23-day schedule across 5 filings beginning Nov 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

8days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

23days

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 clocksTexas✓ TX AG ≤30dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 21, 2025breach begins

Oct 24, 2025discovered

notification delay · 8 days

Nov 1, 2025first filing

Nov 24, 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

NOV 1IL AGIL AG noticefirst filing · no count statedauto-linkedday 0
NOV 1IL AGIL AG noticeno count statedauto-linkedday 0
NOV 19CA AGCA AG noticeno count statedauto-linked+18d
NOV 21TX AGTX AG noticestates nationwide total 319,177auto-linked+20d
NOV 24HHS OCRHHS OCR noticemost recent · states nationwide total 319,177auto-linked+23d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Sep 21, 2025 – Oct 27, 2025
Discovered: Oct 24, 2025· 33d undetected
Data types: Health (basic) · Identity (basic) · Government ID · PHI · PII
Attack vector: Third-Party / Supply Chain

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)

319,177

Sum of filed state slices

5,633· 1.8% of stated

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

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

23 days

Cadence

~1 / 5.8d

vs. multi-state median

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