DisclosureLens
UnknownHealthcareHigh

OneBlood, Inc.

bd_177bc67008aedc06 · schema v1 · pii pii-v1

Severity

High

Discovered

Dec 23, 2024

Filed

Jan 9, 2025

To disclose

17 days

Affected

167,400

Linked

6 filings

Confidence

95%
Full breach record for OneBlood, Inc. →3 incidents on file

OneBlood, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2025-01-09. The breach occurred during 7/14/2024 - 7/29/2024. The breach was discovered on 12/23/2024. 167,400 individuals were affected. Notice was sent on 1/9/2025.

Oregon clock✓ OR AG ≤45d17 days discovery → filing
⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 162 days
discovery → filing · 17 days

Jul 14, 2024

Begins

Dec 23, 2024

Discovered

Jan 9, 2025

Filed

This filing is one of 6 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

Show 1 more filing ↓up to 308d gap

Filing propagation · 6 filings · 6 states

View merged incident ↗
Massachusetts State AGJan 9 · first
South Carolina State AGJan 9 · first
Indiana State AGJan 9 · first
Maine State AGJan 9 · first
Oregon State AGJan 9 · first · this page
Maryland State AG+308d

Pattern: first filing Jan 9 (MA), last Nov 13 (MD) — a 308-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.