CodeMetro
bd_57b00b16078461a8 · schema v1 · pii pii-v1
Full breach record for CodeMetro →3 incidents on fileCodeMetro suffered a ransomware attack on April 21, 2020, which was detected within hours. Attackers accessed a database server, copied and removed data, and deployed ransomware. Affected data included health-related patient information (PHI), personal identifiers (SSN, DOB), school information, and employee payroll data. CodeMetro engaged forensic investigators, notified law enforcement, and offered one year of credit monitoring via TransUnion.
J jump to incidentP pin to compareR raw source
Incident timeline
Apr 21, 2020
Begins
Apr 21, 2020
Discovered
Jun 19, 2020
Filed
vs. sector median
4 wks faster
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Indiana State AGbd_0d4f8b16d4ab2cef2020-06-19Verified
- Massachusetts State AGbd_775ef4afeec2ac602020-06-19Verified
- New Hampshire State AGbd_8a2e4358507c5d632020-06-19Verified
- HHS OCRbd_e29634f20cc85d4d2020-06-19Verified
Show 2 more filings ↓Show fewer ↑up to 3d gap
- Montana State AGbd_f125821bfab468fd2020-06-19Verified
- California State AGbd_78748fa912bcc6a72020-06-16 · +3dVerified
Filing propagation · 7 filings · 5 states
View merged incident ↗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.