Baltimore City Public Schools
bd_313c761c5298f2b2 · schema v1 · pii pii-v2
Full breach record for Baltimore City Public Schools →Baltimore City Public Schools experienced a cybersecurity incident on February 13, 2025, affecting certain IT systems. The breach involved the unauthorized access to files containing names and other personal data. The organization notified law enforcement, engaged external cybersecurity experts, and completed a review of affected files by April 15, 2025. Remediation included installing endpoint detection and response software and resetting all user passwords. Affected individuals were offered two years of complimentary credit monitoring and identity theft restoration services.
J jump to incidentP pin to compareR raw source
Incident timeline
Feb 13, 2025
Begins
Feb 13, 2025
Discovered
Apr 24, 2025
Filed
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Indiana State AGbd_1aa674a0a361f7e32025-04-24Verified
- Idaho State AGbd_e3c3ec5edab659912025-04-28 · +4dCandidate
- Vermont State AGbd_9ab6c0fe1104bebb2025-04-29 · +5dVerified
- Massachusetts State AGbd_b126e5260febdbd02025-04-29 · +5dVerified
Show 2 more filings ↓Show fewer ↑up to 5d gap
- Maine State AGbd_bb5f9b0432bd4ec52025-04-29 · +5dCandidate
- New Hampshire State AGbd_da05d89cd8b7eef72025-04-29 · +5dVerified
Filing propagation · 7 filings · 7 states
View merged incident ↗Pattern: first filing Apr 24 (IN), last Apr 29 (NH) — a 5-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.