BAYMARK HEALTH SERVICES, INC.
bd_d75ef725e07d4c8d · schema v1 · pii pii-v1
Full breach record for BAYMARK HEALTH SERVICES, INC. →2 incidents on fileBayMark Health Services, Inc. disclosed a ransomware incident affecting 2,263 Washington residents. Unauthorized access occurred between Sept 24 and Oct 14, 2024. Patient data including SSNs, driver's licenses, and PHI was exposed. Notification sent May 2, 2025.
J jump to incidentP pin to compareR raw source
Incident timeline
Sep 24, 2024
Begins
Oct 11, 2024
Discovered
May 2, 2025
Filed
vs. sector median
+17 wks slower
Linked disclosures
Why this link?Regulatory filings (10) · sorted by filing gap
- Oregon State AGbd_0773210a4cd26ea62025-05-02Verified
- Indiana State AGbd_1cedfa4d4dcc2eaa2025-05-02Verified
- New Hampshire State AGbd_52c70a5301f6009f2025-05-02Verified
- Maine State AGbd_9433a040cd8602212025-05-02Verified
Show 6 more filings ↓Show fewer ↑up to 114d gap
- California State AGbd_d9bc679cc6a12d272025-05-02Verified
- Nebraska State AGbd_e672487f946f1c322025-05-02Verified
- Vermont State AGbd_fea57e1ef45f00b72025-05-02Verified
- HHS OCRbd_1556e1ab2237060e2025-01-08 · +114dVerified by operator
- Nebraska State AGbd_4365a1babe67b2d72025-01-08 · +114dCandidate
- California State AGbd_e84759092a766ea52025-01-08 · +114dVerified
Showing first 10 of 15 linked disclosures.
Filing propagation · 11 filings · 9 states
View merged incident ↗Pattern: first filing Jan 8 (TX), last May 2 (WA) — a 114-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Cascade drawn from the first 10 linked disclosures of 15 — the full spread may be wider.
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.