ZenPatient — December 2025 breach

Clustered 4 filings across 3 jurisdictions · filing window Jul 17, 2026 → Jul 21, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

15,750

First → last filing

Jul 17, 2026 → Jul 21, 2026

Merge confidence

100%

incident inc_4213b9043641498f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. Intrusion Dec 5, 2025–Feb 12, 2026, discovered Feb 27, 2026 — the first regulatory filing landed 140 days later (flagged late). 15,750 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

140days

Discovered → first regulatory filing

Discovery variance

124days

Range of discovered_at dates across filings

Filing span

4days

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 30-day late · 140dHIPAA✓ HHS notifiedTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.