UFCW Local 135
bd_481a44e9642a4456 · schema v1 · pii pii-v1
Full breach record for UFCW Local 135 →5 incidents on fileUFCW Local 135 notified consumers of a data breach discovered on August 23, 2024, involving unauthorized access to network data. Potentially affected data includes names. The organization engaged a cybersecurity firm, secured its environment, and offered 12-24 months of credit monitoring and identity theft protection services through IDX. Notification was sent January 28, 2025.
J jump to incidentP pin to compareR raw source
Incident timeline
Aug 23, 2024
Discovered
Jan 28, 2025
Filed
vs. sector median
+14 wks slower
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitecicada3301bd_527aee3375d923822024-08-22 · +159dVerified by operator
Regulatory filings (5) · sorted by filing gap
- Montana State AGbd_ad0254d47644ec3f2025-01-28Verified by operator
- California State AGbd_e191e961b88094bf2025-01-28Verified
- Indiana State AGbd_ec8ed93c39cfbcfe2025-01-28Verified by operator
- California State AGbd_8627dcc3b4baa43b2025-02-12 · +15dVerified
Show 1 more filing ↓Show fewer ↑up to 15d gap
- Vermont State AGbd_aeacad5a62aeac862025-02-12 · +15dVerified by operator
Filing propagation · 6 filings · 4 states
View merged incident ↗Pattern: first filing Jan 28 (MT), last Feb 12 (VT) — a 15-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.