Confirmed breach. discovered Jun 8, 2025 — the first regulatory filing landed 222 days later (flagged late). 4,391 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksWashington✗ WA AG >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
4,391
Data types
—
Jurisdictions
1
WA
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
PROVAIL, a health sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2025-06-08 and filed notice on 2026-01-16. 4,391 Washington residents were affected. 222 days elapsed between awareness and notification. 1 days to identify the breach. 1 days to contain the breach.
Affected (this filing): 4,391
WA AG >90dLeak >180d
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.