DisclosureLens
UnknownMedium

Teamsters Local 175

bd_d02e8c95fcdb913c · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Mar 10, 2026

To disclose

—

Affected · nationwide

27,16211 in this filing

Linked

7 records

Confidence

95%
Full breach record for Teamsters Local 175 →

Teamsters Local 175 reported a data breach to the Indiana Attorney General. The breach occurred on 2026-01-02 and was reported on 2026-03-10. 11 Indiana residents were affected. 27,162 individuals affected in total.

Leak gap clock✗ Leak >180d
⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

Incident timeline

Jan 2, 2026

Begins

Mar 10, 2026

Filed

This filing is one of 7 records about the same incident.View merged incident
A leak claim by inc_ransom about this victim was first seen 381 days before this filing.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (5) · sorted by filing gap

Show 1 more filing ↓up to 23d gap

Filing propagation · 6 filings · 4 states

View merged incident ↗
Nebraska State AGMar 10 · first
Indiana State AGMar 10 · first
Indiana State AGMar 10 · first · this page
Maine State AG+3d
Massachusetts State AG+4d
Maine State AG+23d

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

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.