Clustered 2 filings across 2 jurisdictions · filing window Jul 26, 2024 → Jul 29, 2024. View entity profile → Other incidents for this victim →
incident inc_2a7fc63bf893411c · merge_method llm · confidence 57%
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.
PII
IN ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 8, 2024
When the intrusion reportedly occurred, per the linked filings
Jul 2, 2024
Reported by MAINE AG filing
Local Teamsters Union 781 reported a data breach to the Indiana Attorney General. The breach occurred on 2024-01-08 and was reported on 2024-07-26. 201 Indiana residents were affected. 5,148 individuals affected in total.
Affected (this filing): 5,148
Local Teamsters Union 781 (Elmhurst, IL) reported a data security incident affecting 5,148 individuals nationwide, including 1 Maine resident. The breach is described only as 'Other' on the Maine AG form, with no specific data types or attack vector enumerated. The incident occurred between January 8, 2024 and March 21, 2024 and was discovered on July 2, 2024. Written notifications were sent on July 26, 2024, accompanied by 12 months of IDX credit monitoring and identity protection services. The notice does not specify the attack mechanism (e.g., ransomware, phishing, unauthorized access) nor the categories of personal information acquired.
Affected (this filing): 5,148
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.