GLOBALClaimed by Lockbit5First sighting
Posted to leak site Dec 28, 2025bd_c934b72175f66e32
Mt. Spokane Pediatrics offers comprehensive healthcare services for patients from birth through youn...
Clustered 4 filings across 2 jurisdictions · filing window Dec 28, 2025 → Apr 30, 2026. View entity profile → Other incidents for this victim →
incident inc_4081ce6292cc48e4 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
WA
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mt. Spokane Pediatrics offers comprehensive healthcare services for patients from birth through youn...
Jan 1, 2026
Reported by WASHINGTON AG filing
Mt. Spokane Pediatrics offers comprehensive healthcare services for patients from birth through youn...
Jan 3, 2026
Reported by Leak Site filing
Mt. Spokane Pediatrics reported to HHS on 2026-04-30 a Hacking/IT Incident affecting 32021 individuals. Breached information located on Network Server.
Mt. Spokane Pediatrics, a health sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2026-01-01 and filed notice on 2026-04-30. 29,410 Washington residents were affected. 119 days elapsed between awareness and notification. 0 days to identify the breach. 0 days to contain the breach.
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.
Affected (this filing): 32,021
Affected (this filing): 29,410