Diagnostics at Abbott — July 2026 breach
One linked filing — more sources may join as they report · filed Aug 6, 2026. View entity profile → Other incidents for this victim →
incident inc_72c6651fa07e431c · merged by deterministic
What the filings say
OR AGAbbott Cancer Diagnostics reported a data breach to the Oregon Attorney General. The breach was reported on 2026-08-06. The breach occurred during 7/8/2026 - 7/8/2026. The breach was discovered on 7/8/2026. 1 individuals were affected. Notice was sent on 8/5/2026.
AI-generated summary of the linked filing — not the filing's own words, and not independently verified.
Litigation Timing
Discovered → first regulatory filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- AUG 6OR AGOR AG noticeonly filing · states nationwide total 1day 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Jul 8, 2026 OR AG
- Discovered
- Jul 8, 2026 OR AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
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.