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

Confirmed6 records · 4 statesUnverified claimConfirmedEnforcedlapsus$high sensitivity

Merged incident · 6 records

VirtaHealth — March 2026 breach

Clustered 6 records across 4 jurisdictions: 5 filings and 1 leak-site claim · filing window May 23, 2026 → Sep 3, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 records

States

Affected · reported

14,636

First → last dated filing

May 23, 2026 → Sep 3, 2026

Merge confidence

100%

incident inc_605f8640b07d4aa8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 19, 2026–Mar 22, 2026, discovered Mar 24, 2026 — the first regulatory filing landed 60 days later; 1 later filing was flagged late. 14,636 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 103-day schedule across 4 dated filings beginning May 23, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

60days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Leak precedence

48days 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

103days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksCalifornia✗ CA 30-day late · 85dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 19, 2026breach begins

Mar 24, 2026discovered

notification delay · 60 days

May 23, 2026first dated filing

Sep 3, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

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

MAR 29Leak sitelapsus$ postfirst record · attacker claim · unverifiedday 0
MAY 23HHS OCRHHS OCR noticestates nationwide total 14,636operator-confirmed+55d
JUN 12CA AGCA AG noticeno count statedoperator-confirmed+75d
JUN 30HHS OCRHHS OCR noticestates nationwide total 602auto-linked+93d
SEP 1MA AGMA AG noticefiling day not on record · 66 MA residentsauto-linked—
SEP 3SC AGSC AG noticemost recent · 119 SC residentsauto-linked+158d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 19, 2026 – Mar 22, 2026
Discovered: Mar 24, 2026· 5d undetected
Data types: Health (basic) · Identity (basic) · Government ID · PHI · PII
Attack vector: Unauthorized Access

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)

14,636

Sum of filed state slices

185· 1.3% of stated

99% 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: deterministic
Confidence: 1.00 · above the 0.85 auto-merge floor
Reviewed: operator-reviewed Aug 9, 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

103 days

Cadence

~1 / 34.3d

vs. multi-state median

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