Teamsters Local 175
bd_15fec4a7ad628dfc · schema v1 · pii pii-v1
Full breach record for Teamsters Local 175 →Teamsters Local 175 experienced an external system breach (hacking) on January 29, 2025. The incident affected 2,382 individuals, including 1 Maine resident. Compromised data included names, Social Security numbers, and commercial driver's license information. Notices were sent on March 27, 2026, offering 12 months of credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
Jan 29, 2025
Begins
Mar 19, 2026
Discovered
Apr 2, 2026
Filed
vs. sector median
18 wks faster
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Siteinc_ransombd_91f264bdb400ed712025-01-29 · +428dVerified by operator
Regulatory filings (5) · sorted by filing gap
- Massachusetts State AGbd_2a45b8fc685d0a9d2026-03-14 · +19dVerified
- Maine State AGbd_98efa1457c13b2142026-03-13 · +20dVerified
- Nebraska State AGbd_2ca2c2209e60282b2026-03-10 · +23dVerified
- Indiana State AGbd_d02e8c95fcdb913c2026-03-10 · +23dCandidate
Show 1 more filing ↓Show fewer ↑up to 23d gap
- Indiana State AGbd_e30ab306fba27b7c2026-03-10 · +23dCandidate
Filing propagation · 6 filings · 4 states
View merged incident ↗Pattern: first filing Mar 10 (NE), last Apr 2 (ME) — a 23-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.