Travere Therapeutics, Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-06-17 and was reported on 2025-10-20. 5 Indiana residents were affected. 799 individuals affected in total.
Affected (this filing): 799
Clustered 2 filings across 2 jurisdictions · filing window Oct 20, 2025 → Oct 27, 2025. View entity profile → Other incidents for this victim →
incident inc_7d40a0b75f064366 · merge_method deterministic · confidence 100%
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
Jun 17, 2025
When the intrusion reportedly occurred, per the linked filings
Jun 19, 2025
Reported by NEW HAMPSHIRE AG filing
Travere Therapeutics, Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-06-17 and was reported on 2025-10-20. 5 Indiana residents were affected. 799 individuals affected in total.
Affected (this filing): 799
Travere Therapeutics notified the NH AG of a phishing incident where an unauthorized third party accessed an employee email account on June 17, 2025. The attacker accessed personal information of 3 NH residents (names, DOB, SSN, address, phone). Notification was sent on Oct 20, 2025, offering 24 months of credit monitoring.
Affected (this filing): 3
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.