HackingProfessional ServicesProfessional ServicesCustomer Data InvolvedIdentity (basic)Government IDHighContained

Teamsters Local 175

bd_15fec4a7ad628dfc · schema v1 · pii pii-v1

Severity

High

Discovered

Mar 19, 2026

Filed

Apr 2, 2026

To disclose

14 days

Affected · nationwide

2,3821 in this filing

Confidence

65%

Full breach record for Teamsters Local 175 →2 incidents on file

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

Leak gap clock✗ Leak >180d14 days discovery → filing

⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 414 days

discovery → filing · 14 days

Jan 29, 2025

Begins

Mar 19, 2026

Discovered

Apr 2, 2026

Filed

vs. sector median

16 wks faster

Tracked as a single-filing incident — the only disclosure on record for this event so far.Confirmed2,382 affectedView incident

A leak claim by inc_ransom about this victim predates this filing by 428 days.View originating leak claim

Name: Teamsters Local 175
norm: teamsters local 175
Domain: teamsters175.org

Name: Teamsters Local 175
norm: teamsters local 175
Domain: teamsters175.org
Industry: Professional Servicesllm

Discovered: Mar 19, 2026
Breach occurred: Jan 29, 2025
Undetected for: 414 daysoccurrence → discovery
Materiality determined: —
Notification sent: Mar 27, 2026
Affected individuals: 2,382state + nationwide
Data types: Identity (basic)Government ID
Data elements: Social Security number
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing Application
Threat actor: External
Regulator citations: Filed notification with Maine Attorney General
Initial access: exploit_public_facing

During the incident: Secured the compromised systems
Engaged a third-party team of forensic investigators
Initiated an investigation into the unauthorized access
Changes made: Continuously upgrading security measures
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 14 days(14 days from discovery to filing)
Compliance flags: Leak >180dME AG ≤30d · 14d
Discovery-date grounding: AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.
Clock breakdown: Statute Window Elapsed Threshold Status
Maine
Discovered: Mar 19, 2026
→ Filed with AG: Apr 2, 2026
14d 30 days ME AG ≤30d

Statute	Window	Elapsed	Threshold	Status
Maine	Discovered: Mar 19, 2026 → Filed with AG: Apr 2, 2026	14d	30 days	ME AG ≤30d

Status: No extraction artifact recorded for this disclosure.

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.

Source URL: https://www.maine.gov/agviewer/content/ag/985235c7-cb95-4be2-8792-a1252b4f8318/f98b68b1-17b0-4ec2-9005-fe4f1df33efe.html
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 2, 2026
Raw hash: c50d754b2a9b90f001f591956e3ddd4f70f2f860da4fb027705dfc77cb255025

Reporting entityTeamsters Local 175

Victim entityTeamsters Local 175

Incidentdiscovered Mar 19, 2026

Stated responseSecured the compromised systems

ComplianceLeak >180d

Extraction provenanceno artifact recorded

Source provenancewww.maine.gov