Clustered 7 filings across 4 jurisdictions · filing window Aug 8, 2025 → Dec 23, 2025. View entity profile → Other incidents for this victim →
incident inc_7a48653266c841ea · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
PII
CA ME VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 5, 2025 → Aug 8, 2025
When the intrusion reportedly occurred, per the linked filings
Inotiv, Inc. is a publicly USA traded contract research organization (CRO) that provides nonclinical and analytical drug discovery and development services to the pharmaceutical and medical device industries.As a leading contract research org ...
Inotiv, Inc. is a publicly USA traded contract research organization (CRO) that provides nonclinical and analytical drug discovery and development services to the pharmaceutical and medical device industries.As a leading contract research org ...
Nov 21, 2025
Reported by MAINE AG filing
Dec 17, 2025
Reported by MAINE AG filing
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.
Inotiv, Inc. reported a data breach occurring between August 5 and August 8, 2025. The incident involved unauthorized access to personal information, including Social Security Numbers and basic identity data, for both adults and minors. Inotiv contained the incident, engaged external cybersecurity specialists, and notified law enforcement. The company is offering 24 months of credit monitoring and identity theft protection via Experian IdentityWorks to affected individuals.
Inotiv, Inc. reported an external system breach (hacking) occurring August 5–8, 2025, discovered November 21, 2025. A total of 9,542 individuals were affected nationwide, with 5 Maine residents impacted. The company contained the incident, engaged external cybersecurity specialists, and notified law enforcement. Affected individuals were offered 24 months of Experian IdentityWorks credit monitoring and identity theft protection.
Affected (this filing): 5
Inotiv notified consumers of a data breach involving unusual activity. The company engaged external cybersecurity specialists, notified law enforcement, and is offering 24 months of credit monitoring and identity theft protection via Experian. Data types affected include identity information.
Inotiv, Inc. (West Lafayette, IN) reported an external system breach (hacking) that occurred on August 5, 2025 and was discovered on December 17, 2025. The breach affected 10,482 individuals total, with 7 Maine residents impacted. Upon detection, Inotiv contained the incident, engaged external cybersecurity specialists, and notified law enforcement. Affected individuals were offered 24 months of Experian IdentityWorks credit monitoring. Consumer notification was sent December 23, 2025.
Affected (this filing): 7
Inotiv, Inc. filed a breach notification with the California AG covering an incident that occurred August 5–8, 2025. The notification letter is an update to an earlier December notification. Affected individuals were offered 24 months of complimentary Experian IdentityWorks credit monitoring and identity restoration services. The cause and specific data types affected are not fully detailed in the available attachment.