FormFactor, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2020-07-16. The breach occurred during 6/21/2020 - 6/28/2020. The breach was discovered on 6/28/2020. Notice was sent on 7/3/2020.
Clustered 2 filings across 2 jurisdictions · filed Jul 16, 2020. View entity profile → Other incidents for this victim →
incident inc_3605c22305f145a5 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
CA OR
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 21, 2020 → Jun 28, 2020
When the intrusion reportedly occurred, per the linked filings
Jun 28, 2020
Reported by OREGON AG, CALIFORNIA AG filings
FormFactor, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2020-07-16. The breach occurred during 6/21/2020 - 6/28/2020. The breach was discovered on 6/28/2020. Notice was sent on 7/3/2020.
FormFactor, Inc. issued a supplemental data breach notification to California residents regarding unauthorized access to its IT systems beginning June 21, 2020. The breach involved malware and resulted in the loss of personal data, including HR records containing Social Security Numbers and compensation details. FormFactor retained Mandiant for forensic response and is offering one year of complimentary identity theft prevention services (InfoArmor PrivacyArmor Plus) to affected individuals.
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.