HackingProfessional ServicesCustomer Data InvolvedIdentity (basic)LowContained

UFCW Local 135

bd_8627dcc3b4baa43b · schema v1 · pii pii-v1

Severity

Low

Discovered

Aug 23, 2024

Filed

Feb 12, 2025

To disclose

25 weeks

Affected

Not disclosed

Linked

7 filings

Confidence

64%

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

UFCW Local 135 reported that on August 23, 2024, it became aware of suspicious activity within its network environment. An investigation determined that certain data, including names and potentially other sensitive information, was accessed and acquired by an unauthorized third party. The organization secured its environment, engaged a cybersecurity firm, and is offering identity theft protection services to affected individuals. No specific count of affected individuals was disclosed in the notice.

J jump to incidentP pin to compareR raw source

California clockDiscovered Aug 23, 2024 → Notified Feb 12, 2025173d ✗ CA 60-day late25 weeks discovery → filing

Incident timeline

discovery → filing · 25 weeks / 173 days

Aug 23, 2024

Begins

Aug 23, 2024

Discovered

Feb 12, 2025

Filed

This filing is one of 7 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitecicada3301bd_527aee3375d923822024-08-22 · +174dVerified by operator

Regulatory filings (5) · sorted by filing gap

Vermont State AGbd_aeacad5a62aeac862025-02-12Verified by operator
Vermont State AGbd_481a44e9642a44562025-01-28 · +15dVerified by operator
Montana State AGbd_ad0254d47644ec3f2025-01-28 · +15dVerified by operator
California State AGbd_e191e961b88094bf2025-01-28 · +15dVerified

Show 1 more filing ↓up to 15d gap

Indiana State AGbd_ec8ed93c39cfbcfe2025-01-28 · +15dVerified by operator

Name: UFCW Local 135
norm: ufcw local 135
Domain: ufcw135.com

Name: UFCW Local 135
norm: ufcw local 135
Domain: ufcw135.com

Discovered: Aug 23, 2024
Breach occurred: Aug 23, 2024
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Feb 12, 2025
Affected individuals: Not disclosed
Data types: Identity (basic)
Attack vector: Unknown
Threat actor: External

During the incident: Took steps to secure its environment
Engaged a specialized cybersecurity firm to investigate the nature and scope of the event
Began a comprehensive review of the data set to understand whose information was potentially affected
Notified individuals it believed to be impacted on January 28, 2024
Providing access to identity theft protection services through IDX
Changes made: Plan to enhance the security of our systems moving forward in an effort to prevent any further similar events
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 25 weeks(173 days from discovery to filing)
Compliance flags: CA 60-day late · 173d
Discovery-date grounding: letter-groundedThe discovery date is the detection date narrated in the notification letter — the defensible tier.
Clock breakdown: Statute Window Elapsed Threshold Status
California
Discovered: Aug 23, 2024
→ Notified: Feb 12, 2025
173d 60 days (analyst band, pre-2026 discoveries) CA 60-day late

Statute	Window	Elapsed	Threshold	Status
California	Discovered: Aug 23, 2024 → Notified: Feb 12, 2025	173d	60 days (analyst band, pre-2026 discoveries)	CA 60-day late

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 4 states

View merged incident ↗

Vermont State AGJan 28 · first

Montana State AGJan 28 · first

California State AGJan 28 · first

Indiana State AGJan 28 · first

Vermont State AG+15d

California State AG+15d · this page

Pattern: first filing Jan 28 (VT), last Feb 12 (CA) — a 15-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.

Source URL: https://oag.ca.gov/ecrime/databreach/reports/sb24-598567
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 12, 2025
Raw hash: 4535f0304e0d89add9f90d2d7ae901bb20f1a17a552c18ea11f8b337978ce7b3

Linked disclosures

Ransomware claims (1)

Regulatory filings (5) · sorted by filing gap

Reporting entityUFCW Local 135

Victim entityUFCW Local 135

Incidentdiscovered Aug 23, 2024

Stated responseTook steps to secure its environment

ComplianceCA 60-day late

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov