DisclosureLens
CALIFORNIAHackingHealthcareHealthcareHealth (basic)Identity (basic)HighContained

zHealth, Inc.

bd_f73668fb4abe49ff · schema v1 · pii pii-v2

Severity

High

Discovered

—

Filed

Jul 29, 2026

To disclose

—

Affected

118,563

Linked

6 records

Confidence

69%

zHealth, Inc. reported to HHS on 2026-07-29 a Hacking/IT Incident affecting 118563 individuals. Breached information located on Network Server.

Leak gap clock✗ Leak >180d
⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.
⚠ No discovery dateThe OCR public portal omits the discovery date, so the 60-day notification clock cannot be evaluated from this source — only that the filing was submitted.

Incident timeline — partial

? — ?

Breach window unknown

Jul 29, 2026

Filed

No interval is drawn: no breach start or discovery date is on record for this filing.

This filing is one of 6 records about the same incident.View merged incident
A leak claim by kazu about this victim was first seen 184 days before this filing.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (4) · sorted by filing gap

Filing propagation · 5 filings · 4 states

View merged incident ↗
HHS OCRJul 29 · first · this page
California State AG+44d
Oregon State AG+44d
Washington State AG+44d
Texas State AG+48d

Pattern: first filing Jul 29 (CA), last Sep 15 (TX) — a 48-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.