Centrelake Medical Group, Inc.
bd_1e7f4398452ebdf4 · schema v1 · pii pii-v1
Full breach record for Centrelake Medical Group, Inc. →2 incidents on fileCentrelake Medical Group, Inc. experienced a malware incident where an unknown third party introduced a virus that encrypted files and prohibited access. Suspicious activity began on January 9, 2019, and was discovered on February 19, 2019. The incident potentially affected protected health information, including names, SSNs, and medical records, of patients in California and other states. The organization engaged third-party forensics, restored systems, and offered identity monitoring services.
J jump to incidentP pin to compareR raw source
Incident timeline
Jan 9, 2019
Begins
Feb 19, 2019
Discovered
May 15, 2019
Filed
vs. sector median
on median
Linked disclosures
Why this link?Regulatory filings (5) · sorted by filing gap
- New Hampshire State AGbd_e9c07bcc541493352019-04-22 · +23dVerified
- Montana State AGbd_2f595599bea258d22019-04-16 · +29dVerified
- HHS OCRbd_4d4ab4bdac39256b2019-04-16 · +29dVerified
- California State AGbd_5a79055f0c129f242019-04-16 · +29dVerified
Show 1 more filing ↓Show fewer ↑up to 29d gap
- Massachusetts State AGbd_95491b3edc63f1312019-04-16 · +29dVerified
Filing propagation · 6 filings · 4 states
View merged incident ↗Pattern: first filing Apr 16 (MT), last May 15 (CA) — a 29-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
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.