UFCW Local 135
bd_527aee3375d92382 · schema v1 · pii pii-v1
Full breach record for UFCW Local 135 →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cicada3301 on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
UFCW International Members of UFCW Local 135 have the backing of more than 1.3 million fellow members of the UFCW International Union across the United States and Canada. Together, we are an effective force for better wages, secure benefits and stronger rights at the workplace. Data will be released soon if the company doesn't contact us!
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Aug 22, 2024
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (10) · sorted by filing gap
- Maine State AGbd_3fa4e3c2e9074da52025-01-28 · +159dVerified by operator
- Vermont State AGbd_481a44e9642a44562025-01-28 · +159dVerified by operator
- Massachusetts State AGbd_a2ca6b05961adf042025-01-28 · +159dVerified by operator
- Montana State AGbd_ad0254d47644ec3f2025-01-28 · +159dVerified by operator
Show 6 more filings ↓Show fewer ↑up to 482d gap
- Nebraska State AGbd_ad84e69b611b952f2025-01-28 · +159dVerified by operator
- New Hampshire State AGbd_b0b38b0aba60be5f2025-02-03 · +165dVerified
- California State AGbd_8627dcc3b4baa43b2025-02-12 · +174dVerified
- Vermont State AGbd_aeacad5a62aeac862025-02-12 · +174dVerified by operator
- New Hampshire State AGbd_96d9cbd41c1c829d2025-02-20 · +182dVerified
- Maryland State AGbd_a2d4d73e19193ad72025-12-17 · +482dVerified by operator
Showing first 10 of 12 linked disclosures.
Filing propagation · 10 filings · 8 states
View merged incident ↗Pattern: first filing Jan 28 (ME), last Dec 17 (MD) — a 323-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Cascade drawn from the first 10 linked disclosures of 12 — the full spread may be wider.
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.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
cicada3301
According to ransomware.live, Cicada3301 is a ransomware-as-a-service group (tracked as Repellent Scorpius by Palo Alto) that emerged in mid-2024 using Rust-based ransomware targeting Windows, Linux, and ESXi systems, suspected to be a successor of BlackCat/ALPHV and running an affiliate program with 20% commissions.