Confirmed breach. Intrusion Apr 18, 2022, discovered Apr 18, 2022 — the first regulatory filing landed 60 days later (flagged late). 880 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksOregon✗ OR AG >45dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
880
Data types
—
Jurisdictions
2
OH OR
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Apr 18, 2022
When the intrusion reportedly occurred, per the linked filings
Breach discoveredAG web form
Apr 18, 2022
Reported by OREGON AG filing
60 days
🇺🇸OHHHS OCRFirst filinglinked via same-victim cross-source · 100%
Tosoh America, Inc. reported to HHS on 2022-06-17 a Hacking/IT Incident affecting 880 individuals. Breached information located on Email. Employees were subjects of an email phishing scheme compromising PHI (names, DOB, SSN). CE provided credit monitoring and retrained staff.
Affected (this filing): 880
🦫Oregon State AGMost recentlinked via same-victim cross-source · 100%
Tosoh America, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2022-06-17. The breach occurred during 4/18/2022 - 4/18/2022. The breach was discovered on 4/18/2022. 880 individuals were affected. Notice was sent on 6/17/2022.
Affected (this filing): 880
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.