OraSure Technologies, Inc. — March 2024 breach

Clustered 6 filings across 6 jurisdictions · filing window Apr 12, 2024 → Aug 7, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

Affected · reported

1,701

First → last filing

Apr 12, 2024 → Aug 7, 2024

Merge confidence

100%

incident inc_1b18df9d9bf64770 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe hacking. Intrusion Mar 25, 2024–Mar 27, 2024, discovered Mar 27, 2024 — the first regulatory filing landed 16 days later. 1,701 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Notifications rolled out on a 117-day schedule across 6 filings beginning Apr 12, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

16days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Materiality delta

14days

Discovery to SEC materiality determination

SEC filing delay

2days

Materiality determination to SEC 8-K filing

Filing span

117days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence — no leak-site claim in this cluster.

Regulatory clocksSEC✓ SEC 4-day OK · 2dMassachusetts✓ MA credit monitoring 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.