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

Quantum Health, Inc. — May 2026 breach

Clustered 9 filings across 9 jurisdictions · filing window Jul 1, 2026 → Aug 18, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

184,376

First → last filing

Jul 1, 2026 → Aug 18, 2026

Merge confidence

100%

incident inc_86f67d1d6b8e42e7 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion May 29, 2026–Jun 1, 2026, discovered Jun 1, 2026 — the first regulatory filing landed 30 days later (flagged late). 184,376 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 2 more. Notifications rolled out on a 48-day schedule across 9 filings beginning Jul 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
30days

Discovered → first regulatory filing

Discovery variance
56days

Range of discovered_at dates across filings

Filing span
48days

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 clocksOregon✗ OR AG >45dCalifornia✗ CA 30-day late · 56dMassachusetts⏱ MA AG >30dWashington⏱ WA AG >30dHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 29, 2026breach begins
Jun 1, 2026discovered · members disagree
notification delay · 30 days
Jul 1, 2026first filing
Aug 18, 2026most 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. JUL 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUL 29HHS OCRHHS OCR noticestates nationwide total 2,104+28d
  3. JUL 29NH AGNH AG notice5 NH residents+28d
  4. JUL 30MA AGMA AG notice1 MA residents+29d
  5. AUG 14OR AGOR AG noticestates nationwide total 184,376+44d
  6. AUG 14CA AGCA AG noticeno count stated+44d
  7. AUG 14WA AGWA AG notice5,909 WA residents+44d
  8. AUG 17SC AGSC AG notice6,481 SC residents+47d
  9. AUG 18TX AGTX AG noticemost recent · 68,451 affected+48d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 29, 2026 – Jun 1, 2026
NH AG
Discovered
Jun 1, 2026IL AG + NH AG + MA AG +4Jul 27, 2026TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
IL AG + HHS OCR + NH AG +5
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)

184,376

Sum of filed state slices

80,847· 43.8% of stated

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

US184,376
TX68,451
SC6,481
WA5,909
NH5
MA1

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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

48 days

Cadence

~1 / 6d

vs. multi-state median

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