OneBlood, Inc.
bd_a2871e1428a6a480 · schema v1 · pii pii-v1
Full breach record for OneBlood, Inc. →OneBlood, Inc. reported an external system breach (hacking) occurring between July 14 and July 29, 2024. The incident involved unauthorized copying of files containing names and Social Security numbers. OneBlood discovered the suspicious activity on July 28, 2024, and notified federal law enforcement. 281 Maine residents were affected. Notification was sent on January 9, 2025, offering 12 months of credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
Jul 14, 2024
Begins
Jul 28, 2024
Discovered
Jan 9, 2025
Filed
vs. sector median
+15 wks slower
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- Vermont State AGbd_02db70a5225d0d432025-01-09Verified
- Oregon State AGbd_177bc67008aedc062025-01-09Candidate
- Massachusetts State AGbd_21809a99aff28c142025-01-09Verified
- South Carolina State AGbd_26194deb18bd76452025-01-09Verified
Show 3 more filings ↓Show fewer ↑up to 308d gap
- Indiana State AGbd_6e9d8e191ff20a4d2025-01-09Verified
- Illinois State AGbd_58c1898a7fe867ad2025-01-01 · +8dVerified by operator
- Maryland State AGbd_4d599b95055a1ac12025-11-13 · +308dVerified
Filing propagation · 8 filings · 8 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last Nov 13 (MD) — a 316-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.