DisclosureLens
COLORADOHackingHealthcareHealthcareHealth (basic)Identity (basic)Low

VirtaHealth

bd_4b9cd878952d35ce · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Jun 30, 2026

To disclose

—

Affected

602

Linked

6 records

Confidence

69%
Full breach record for VirtaHealth →

Virta Health reported to HHS on 2026-06-30 a Hacking/IT Incident affecting 602 individuals. Breached information located on Network Server.

Leak gap clock⏱ Leak >30d
⚠ 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

Jun 30, 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 lapsus$ about this victim was first seen 86 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 OCRMay 23 · first
California State AG+20d
HHS OCR+38d · this page
Massachusetts State AG+101d
South Carolina State AG+103d

Pattern: first filing May 23 (CO), last Sep 3 (SC) — a 103-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.