Baltimore City Public Schools
bd_bb5f9b0432bd4ec5 · schema v1 · pii pii-v1
Full breach record for Baltimore City Public Schools →Baltimore City Public Schools experienced an external system breach (hacking) between Feb 8-24, 2025, discovered on Feb 13, 2025. Approximately 20,665 individuals were affected, including 2 Maine residents. The incident involved unauthorized access to files containing names and other personal identifiers. The school district notified law enforcement, engaged external experts, and offered 24 months of credit monitoring and identity theft protection services to affected individuals.
J jump to incidentP pin to compareR raw source
Incident timeline
Feb 8, 2025
Begins
Feb 13, 2025
Discovered
Apr 29, 2025
Filed
vs. sector median
+1 wks slower
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Vermont State AGbd_9ab6c0fe1104bebb2025-04-29Verified
- Massachusetts State AGbd_b126e5260febdbd02025-04-29Verified
- New Hampshire State AGbd_da05d89cd8b7eef72025-04-29Verified
- Idaho State AGbd_e3c3ec5edab659912025-04-28 · +1dCandidate
Show 2 more filings ↓Show fewer ↑up to 5d gap
- Indiana State AGbd_1aa674a0a361f7e32025-04-24 · +5dVerified
- Nebraska State AGbd_313c761c5298f2b22025-04-24 · +5dVerified
Filing propagation · 7 filings · 7 states
View merged incident ↗Pattern: first filing Apr 24 (IN), last Apr 29 (ME) — 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.