Confirmed breach. Intrusion Jan 29, 2025, discovered Jan 2, 2026 — the first regulatory filing landed 90 days later. 1 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine⏱ ME AG >30d · 90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
1
Data types
3
PII · Government ID · Credentials
Jurisdictions
1
ME
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 29, 2025
When the intrusion reportedly occurred, per the linked filings
Teamsters Local 175 (WV labor union) suffered an external system breach on 2025-01-29, discovered 2026-01-02. SSNs, names, and CDL info of 2,382 individuals (1 ME resident) may have been accessed. Notification sent 2026-03-27; 12-month credit monitoring offered via Cyberscout/TransUnion.
Affected (this filing): 1
ME AG >30d · 90dME resident >60d · 84d
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.