SYNOPSYS, INC. — May 2008 breach
One linked filing — more sources may join as they report · filed Jun 20, 2008. View entity profile → Other incidents for this victim →
incident inc_6f996a43691c4349 · merged by deterministic
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.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- JUN 20NH AGNH AG noticeonly filing · states nationwide total 3,053day 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- May 26, 2008 NH AG
- Discovered
- Jun 10, 2008· 15d undetected NH AG
- Data types
- Identity (basic) · Government ID NH AG
- Attack vector
- Third-Party / Supply Chain NH AG
- Response
- Notifying all affected former Avant! employees and their dependents via first-class U.S. mail · Providing affected former Avant! employees and their dependents with access to AIG's Ambassador ID Theft Service at no charge for six months NH AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Count reconciliation
per-state reported counts
Nationwide (stated in a filing)
3,053
Sum of filed state slices
34· 1.1% of stated
99% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
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.