OneBlood, Inc. — July 2024 breach

Clustered 6 filings across 6 jurisdictions · filing window Jan 9, 2025 → Nov 13, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

Affected · reported

167,400

First → last filing

Jan 9, 2025 → Nov 13, 2025

Merge confidence

100%

incident inc_fe13df2cdde744fb · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe unauthorized access. Intrusion Jul 14, 2024–Jul 29, 2024, discovered Jul 28, 2024 — the first regulatory filing landed 165 days later (flagged late). 167,400 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 308-day schedule across 6 filings beginning Jan 9, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

165days

Discovered → first regulatory filing

Discovery variance

148days

Range of discovered_at dates across filings

Filing span

308days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine✗ ME AG >90d · 165dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.