Incident · 8-K Item 1.05
OraSure Technologies reports exfiltrated files and reaffirms quarterly revenue guidance
Compiled from public records. Updated 2026-11-08. By the cisonews.net Desk.
OraSure Technologies, Inc. told the SEC in a Form 8-K dated April 12, 2024 that an unauthorized third party gained access to company data from certain information systems after the company became aware of the incident on or about March 27, 2024. The filing says files were exfiltrated, that the company was still investigating whether they held sensitive or personal information, and it states no count of affected people.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
What happened and when
The filing lists April 10, 2024 as the date of the earliest event reported and carries a signature date of April 12, 2024. After detection, the company says it started response protocols and brought in outside help. It says it believes the incident is contained and that its core financial and operational systems kept their integrity.
What information was involved
The filing confirms that some files left the company's systems but does not say what they contained. No data categories are named, so readers cannot tell from the filing whether customer, patient, employee or business records were involved. The company also says it is weighing what notices it must send.
Operations, finances and guidance
OraSure states that the incident had not had a material effect on its operations or finances as of the filing date. It also says its systems are running and that it does not expect a material effect on future results. In Item 7.01 of the same filing, the company repeated its earlier revenue outlook.
What Indiana's attorney general recorded
Indiana's attorney general lists OraSure Technologies Inc in its 2024 breach report, with notice sent on July 9, 2024 for a breach that occurred on March 25, 2024: 4 Indiana residents and 1,701 people affected in total. The total is the figure the organization reported to Indiana.
What OraSure's later filings say about the April 2024 incident
OraSure never amended the April 12, 2024 8-K, and its next three quarterly reports mention cybersecurity incidents only in a generic list of risks. The incident is named once, in the cybersecurity section of the annual report for 2024, filed on March 7, 2025. That report says the company has been subject to cybersecurity incidents in the past, "including the publicly disclosed April 2024 security incident", and that it does not believe risks from cybersecurity threats, including those from earlier incidents, have materially affected its operations, financial systems or financial condition.
The annual report for 2025, filed on March 9, 2026, no longer names the April 2024 incident. Its risk factor keeps a general line that the company, like others in its industry, has experienced cybersecurity incidents in the past.
| Filed | Filing | What it says about the incident |
|---|---|---|
| April 12, 2024 | Form 8-K, Item 1.05 | Files exfiltrated; contents under review; no material effect so far |
| May 9, Aug 6 and Nov 6, 2024 | Forms 10-Q | Only a generic risk line on cybersecurity incidents |
| March 7, 2025 | Form 10-K for 2024 | Named as "the publicly disclosed April 2024 security incident"; no material effect |
| March 9, 2026 | Form 10-K for 2025 | No longer named; a general line on past incidents |
None of these filings gives a count of the people affected. The only count on record is the 1,701 in Indiana's report, above. For how other companies in the log closed out an incident in their later reports, see After the 8-K.
Did the OraSure data breach have a material impact?
Not according to the company. The 8-K said the incident had not had a material effect on its operations or finances when it was filed. The 10-K for 2024 says the company does not believe risks from cybersecurity threats, including earlier incidents, have materially affected its operations, financial systems or financial condition.
What the filing leaves open
The company says its work was not finished. The filing does not state how many people may be affected, what kinds of personal information may be in the files, whether notification letters will be sent, or who the unauthorized party was. No amended 8-K is on record; the later 10-K is covered above. Indiana's report, above, shows that notices went out on July 9, 2024, with 1,701 people affected in total.
How this disclosure's timing compares
OraSure Technologies disclosed 16 days after the discovery date its filing gives. Across the 46 other filings under 8-K Item 1.05 on cisonews.net that date discovery to the day, the median gap is 6 days.
The rule behind an Item 1.05 filing
Form 8-K Item 1.05 is where a public company reports a cybersecurity incident it has determined to be material. Under the rule the SEC adopted on July 26, 2023, the filing is generally due four business days after the company determines that the incident is material. Source: U.S. Securities and Exchange Commission, press release 2023-139. The guide What is SEC Form 8-K Item 1.05, and what counts as a disclosed cyber incident? reads the rule in full, and the glossary defines Form 8-K Item 1.05.
Other life sciences & medical devices incidents on cisonews.net
- Dexcom, Inc., Breach notice, first disclosed November 13, 2026
- LeMaitre Vascular, Inc., Breach notice, first disclosed September 18, 2026
- Boston Scientific, 8-K Item 1.05, first disclosed August 26, 2026
- Amgen, 8-K Item 1.05, first disclosed July 31, 2026; 39,594 affected in total (Indiana Attorney General)
- Fresenius Kabi USA, LLC, Breach notice, first disclosed June 17, 2026
Sources
- 2024-04-12 · AOraSure Technologies, Inc., Form 8-K (SEC EDGAR), published April 12, 2024
- 2024-08-06 · AOraSure Technologies, Inc., Form 10-Q for the quarter ended June 30, 2024 (SEC EDGAR), published August 6, 2024
- 2025-03-07 · AOraSure Technologies, Inc., Form 10-K for 2024 (SEC EDGAR), published March 7, 2025
- 2026-03-09 · AOraSure Technologies, Inc., Form 10-K for 2025 (SEC EDGAR), published March 9, 2026
- 2026-11-09 · AIndiana Attorney General, data breach year-to-date report (2024), published November 9, 2026
- 2023-07-26 · AU.S. Securities and Exchange Commission, press release 2023-139, published July 26, 2023
Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.