Clustered 3 filings across 3 jurisdictions · filing window Nov 21, 2023 → Jan 17, 2024. View entity profile → Other incidents for this victim →
incident inc_ac99470c66e34d20 · 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.
MI MT WA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 28, 2023
When the intrusion reportedly occurred, per the linked filings
May 28, 2023
Reported by WASHINGTON AG filing
TGI Direct, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2023-11-21. The breach occurred on 5/28/2023. 123 Montana residents were affected.
Affected (this filing): 123
TGI Direct, a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2023-05-28 and filed notice on 2024-01-17. 3,428 Washington residents were affected. 234 days elapsed between awareness and notification. 0 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 3,428
TGI Direct reported to HHS on 2024-01-17 a Hacking/IT Incident affecting 11,556 individuals. Breached information located on Network Server. A software application exposed PHI including names, dates of birth, addresses, and diagnoses. The business associate notified HHS, affected individuals, and media, provided substitute notice, complimentary credit monitoring, and implemented additional safeguards.
Affected (this filing): 11,556
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.