DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteSEC 8-KState AGConfirmed16 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedqilinhigh sensitivity
Merged incident · 16 filings

Inotiv, Inc. — August 2025 breach

Clustered 16 filings across 10 jurisdictions · filing window Aug 8, 2025 → May 18, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

16 filings

States

9

Affected · reported

10,482

First → last filing

Aug 8, 2025 → May 18, 2026

Merge confidence

100%

incident inc_c6297f5113ff435c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings and 2 unverified claims. Intrusion Aug 5, 2025–Aug 8, 2025, discovered Aug 8, 2025. 10,482 individuals reported across the linked filings. Data reported: Government ID, PII, PHI, and 4 more. Notifications rolled out on a 143-day schedule across 14 filings beginning Aug 8, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
0days

Discovered → first regulatory filing

Discovery variance
131days

Range of discovered_at dates across filings

Leak precedence
Same day

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
143days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay

Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 5, 2025breach begins
Aug 8, 2025discovered · members disagree
notification delay · 0 days
Aug 8, 2025first filing
Dec 29, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. AUG 8Leak siteqilin postfirst filing · attacker claim · unverifiedday 0
  2. AUG 8SEC 8-KSEC 8-K noticeno count statedday 0
  3. AUG 11Leak siteqilin postattacker claim · unverified+3d
  4. SEP 25SEC 8-KSEC 8-K noticeno count stated+48d
  5. DEC 2IN AGIN AG noticestates nationwide total 10,482+116d
  6. DEC 2NE AGNE AG noticeno count stated+116d
  7. DEC 2NH AGNH AG noticeno count stated+116d
  8. DEC 2CA AGCA AG noticeno count stated+116d
  9. DEC 2ME AGME AG noticestates nationwide total 9,542+116d
  10. DEC 3MA AGMA AG notice40 MA residents+117d
  11. DEC 22VT AGVT AG noticeno count stated+136d
  12. DEC 23NE AGNE AG noticeno count stated+137d
  13. DEC 23ME AGME AG noticestates nationwide total 10,482+137d
  14. DEC 23NH AGNH AG notice14 NH residents+137d
  15. DEC 23CA AGCA AG noticeno count stated+137d
  16. DEC 29TX AGTX AG noticemost recent · states nationwide total 10,482+143d
  17. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 5, 2025
IN AG
Discovered
Aug 8, 2025SEC 8-KNov 21, 2025ME AG + NH AGDec 17, 2025ME AG + TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
SEC 8-K + NH AG + CA AG +5
Attack vector
Ransomware
SEC 8-K

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)

10,482

Sum of filed state slices

4,159· 39.7% of stated

60% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US10,482
IN3,158
TX940
MA40
NH14
ME7

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing12 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement2 members

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 23, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

143 days

Cadence

~1 / 9.5d

vs. multi-state median

17.9× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.