DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed6 records · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedkazuhigh sensitivity
Merged incident · 6 records

zHealth, Inc. — January 2026 breach

Clustered 6 records across 4 jurisdictions: 5 filings and 1 leak-site claim · filing window Jul 29, 2026 → Sep 15, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 records

States

4

Affected · reported

118,563

First → last filing

Jul 29, 2026 → Sep 15, 2026

Merge confidence

100%

incident inc_21c3dd3454bb4483 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jan 20, 2026–Jan 21, 2026, discovered Jun 15, 2026 — the first regulatory filing landed 44 days later; 1 later filing was flagged late. 118,563 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 3 more. Notifications rolled out on a 48-day schedule across 5 filings beginning Jul 29, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
44days

Discovered → first regulatory filing

Discovery variance
80days

Range of discovered_at dates across filings

Leak precedence
184days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
48days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dOregon✗ OR AG >45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 20, 2026breach begins
Jun 15, 2026discovered · members disagree
notification delay · 44 days
Jul 29, 2026first filing
Sep 15, 2026most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing and leak-site claim in this incident

  1. JAN 26Leak sitekazu postfirst record · attacker claim · unverifiedday 0
  2. JUL 29HHS OCRHHS OCR noticestates nationwide total 118,563+184d
  3. SEP 11CA AGCA AG noticeno count stated+228d
  4. SEP 11OR AGOR AG noticestates nationwide total 118,563+228d
  5. SEP 11WA AGWA AG notice1,332 WA residents+228d
  6. SEP 15TX AGTX AG noticemost recent · states nationwide total 118,563+232d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 20, 2026 – Jan 21, 2026
CA AG
Discovered
Jun 15, 2026CA AG + OR AG + WA AGSep 3, 2026TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + TX AG + CA AG +1
Attack vector
Unauthorized Access
HHS OCR

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)

118,563

Sum of filed state slices

9,859· 8.3% of stated

92% 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 claim1 member

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

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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 6, 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

48 days

Cadence

~1 / 12d

vs. multi-state median

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