Sagent Pharmaceuticals reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-11 and was reported on 2026-04-17. 4 Indiana residents were affected. 1,383 individuals affected in total.
Affected (this filing): 1,383
Clustered 2 filings across 2 jurisdictions · filing window Apr 17, 2026 → May 1, 2026. View entity profile → Other incidents for this victim →
incident inc_e0d980c443b944be · merge_method deterministic · confidence 95%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 11, 2026
When the intrusion reportedly occurred, per the linked filings
Feb 11, 2026
Reported by NEW HAMPSHIRE AG filing
Sagent Pharmaceuticals reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-11 and was reported on 2026-04-17. 4 Indiana residents were affected. 1,383 individuals affected in total.
Affected (this filing): 1,383
Sagent Pharmaceuticals notified the NH AG of unauthorized network access occurring on or around Feb 11, 2026. Investigation concluded Mar 23, 2026, revealing limited personal info removal including names, SSNs, driver's licenses, bank info, and health insurance data. 2 NH residents affected. Notification sent Apr 17, 2026, offering credit monitoring.
Affected (this filing): 2
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.