Confirmed breach. discovered Jul 9, 2024 — the first regulatory filing landed 181 days later (flagged late). 1 individuals reported across the linked filings.
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.
Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
1
Data types
2
PII · Identity (basic)
Jurisdictions
1
NH
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Repligen Corporation notified the NH AG of unauthorized access to its systems discovered on July 9, 2024. The incident affected one New Hampshire resident's personal information. Repligen contained the incident, consulted federal law enforcement, and offered Experian identity protection services. Notification was mailed on January 3, 2025.
Affected (this filing): 1
Leak >180d
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.