Clustered 4 filings across 2 jurisdictions · filing window Nov 13, 2024 → Jan 8, 2025. View entity profile → Other incidents for this victim →
incident inc_61179fb2054b47e5 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
WA
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 13, 2024
Reported by WASHINGTON AG filing
Since 1968, Youth Eastside Services helped children, teens and families struggling with depression, grief, trauma, substance abuse, anxiety, gender- or cultural-identity issues, behavioral issues, ADHD, and autism. It provides counseling, substance abuse treatment, education and prevention, and psychiatric services in East King County.
Youth Eastside Services, a non-profit/charity sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2024-11-13 and filed notice on 2024-12-20. 755 Washington residents were affected. 37 days elapsed between awareness and notification. 0 days to identify the breach. 1 days to contain the breach.
Youth Eastside Services reported to HHS on 2024-12-20 a Hacking/IT Incident affecting 23492 individuals. Breached information located on Network Server. The incident involved ransomware encrypting PHI (demographic, clinical, financial). The entity offered credit monitoring and implemented security safeguards.
Since 1968, Youth Eastside Services helped children, teens and families struggling with depression, grief, trauma, substance abuse, anxiety, gender- or cultural-identity issues, behavioral issues, ADHD, and autism. It provides counseling, substance abuse treatment, education and prevention, and psychiatric services in East King County.
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): 755
Affected (this filing): 23,492