Confirmed breach. Intrusion Aug 20, 2023, discovered Aug 25, 2023 — the first regulatory filing landed 325 days later (flagged late). 765,937 individuals reported across the linked filings.
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.
Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
765,937
Data types
—
Jurisdictions
2
IN NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Aug 20, 2023
When the intrusion reportedly occurred, per the linked filings
MNGI Digestive Health reported a data breach to the Indiana Attorney General. The breach occurred on 2023-08-20 and was reported on 2024-07-15. 127 Indiana residents were affected. 765,937 individuals affected in total.
Affected (this filing): 765,937
Leak >180d
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
MNGI Digestive Health reported a data security incident where unauthorized access occurred on August 20, 2023, discovered on August 25, 2023. The breach potentially affected personal and protected health information, including SSNs, of 23 New Hampshire residents. MNGI engaged cybersecurity experts, secured its network, and provided complimentary identity protection services. No evidence of misuse was found.
Affected (this filing): 23
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.