Where does the OneBlood, Inc. case file come from?

Every entry is taken from the breach report OneBlood, Inc. lodged with the Oregon Attorney General. Nothing here is estimated.

Why do the incident date and the report date differ?

Companies usually investigate before they report. The gap between the two dates shows how long that took.

What does the records-affected figure count?

It is the number the company gave the state. It can cover residents of that state only, so the national total may be higher.

Does this case file change over time?

Yes. When a company files an update or a new state publishes its copy of the report, the dates and counts here are refreshed.

Case file

Case File: OneBlood, Inc. Data Breach

This file collects the dated facts on record for the OneBlood, Inc. incident. The state report is dated January 9, 2025. The incident itself is dated July 14, 2024.

Timeline

179 days separate the incident date from the date it was reported.

July 14, 2024Incident dateWhen the filing says the breach took place.
January 9, 2025Report filed in OregonDate the notice was lodged with the Oregon Attorney General.

Case facts

Filing state: Oregon
Date reported: January 9, 2025
Incident date: July 14, 2024
Receiving office: Oregon Attorney General

Case notes

OneBlood, Inc., a nonprofit blood center, has disclosed a data security incident to regulators in Oregon. The official notification regarding the breach was filed on January 9, 2025, detailing an event that first took place on July 14, 2024. The specifics of how the breach occurred are not detailed in the public records at this time.

According to the information provided in the public filing, OneBlood, Inc. has initiated an investigation into the circumstances of this security incident. The investigation aims to understand the full scope of the event and the extent of any unauthorized access to its systems.

During the incident, certain personal information may have been exposed. The exact categories of data involved have not been specified in the publicly available reports. Therefore, individuals should refer to any direct communications they receive from OneBlood, Inc. for precise details relevant to their situation.

For those who may be impacted, it is always advisable to take proactive steps to protect your data. This includes carefully monitoring all account statements and credit reports for any unusual or unauthorized activity. Should you identify any discrepancies, report them immediately to the relevant financial institution or credit bureau.

Additionally, consider placing a fraud alert on your credit files, which will require businesses to verify your identity before extending new credit. You may also explore the option of a credit freeze, which restricts access to your credit report altogether. Always be wary of unsolicited emails, phone calls, or messages that ask for personal details, as these could be phishing attempts.

Questions about this case file

Where does the OneBlood, Inc. case file come from?: Every entry is taken from the breach report OneBlood, Inc. lodged with the Oregon Attorney General. Nothing here is estimated.
Why do the incident date and the report date differ?: Companies usually investigate before they report. The gap between the two dates shows how long that took.
What does the records-affected figure count?: It is the number the company gave the state. It can cover residents of that state only, so the national total may be higher.
Does this case file change over time?: Yes. When a company files an update or a new state publishes its copy of the report, the dates and counts here are refreshed.

Oregon data breaches

Filing source: Oregon Attorney General

Named in the OneBlood, Inc. breach?

Attach your notice and a short note. An attorney checks it against this case file at no cost.

Timeline

Case facts

Case notes

Questions about this case file

More Oregon case files