DisclosureLens
HackingProfessional ServicesProfessional ServicesData ExfiltratedCustomer Data InvolvedPIIIdentity (basic)LowContained

UFCW Local 135

bd_96d9cbd41c1c829d · schema v1 · pii pii-v1

Severity

Low

Discovered

Aug 23, 2024

Filed

Feb 20, 2025

To disclose

26 weeks

Affected

7state residents only

Linked

2 filings

Confidence

66%
Full breach record for UFCW Local 135 →5 incidents on file

UFCW Local 135 reported a cybersecurity event to the New Hampshire Attorney General. The breach was discovered on August 23, 2024, involving unauthorized access to network data. The incident affects 7 New Hampshire residents. Data potentially compromised includes personal information. The union engaged a forensic firm, notified individuals, and offered credit monitoring services. This is a supplemental notice.

Leak gap clock✗ Leak >180d26 weeks discovery → filing

Incident timeline

discovery → filing · 26 weeks / 181 days

Aug 23, 2024

Begins

Aug 23, 2024

Discovered

Feb 20, 2025

Filed

vs. sector median

+8 wks slower

This filing is one of 2 about the same incident.View merged incident
A leak claim by cicada3301 about this victim predates this filing by 182 days.View originating leak claim

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

Filing propagation · 2 filings

View merged incident ↗
New Hampshire State AGFeb 3 · first
New Hampshire State AG+17d · this page

Pattern: first filing Feb 3 (NH), last Feb 20 (NH) — a 17-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.