DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed13 records · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcicada3301high sensitivity
Merged incident · 13 records

UFCW Local 135 — August 2024 breach

Clustered 13 records across 9 jurisdictions: 12 filings and 1 leak-site claim · filing window Jan 28, 2025 → Feb 20, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 records

States

9

Affected · reported

63,921

First → last dated filing

Jan 28, 2025 → Feb 20, 2025

Merge confidence

100%

incident inc_5587c06ca80d4c4d · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 23, 2024, discovered Aug 23, 2024 — the first regulatory filing landed 158 days later (flagged late); 2 later filings were also flagged late. 63,921 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 23-day schedule across 10 dated filings beginning Jan 28, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
158days

Discovered → first regulatory filing

Discovery variance
145days

Range of discovered_at dates across filings

Leak precedence
159days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
23days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap✗ Leak >180dCalifornia✗ CA 60-day late · 158dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 23, 2024breach begins
Aug 23, 2024discovered · members disagree
notification delay · 158 days
Jan 28, 2025first dated filing
Feb 20, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. AUG 22Leak sitecicada3301 postfirst record · attacker claim · unverifiedday 0
  2. JAN 28VT AGVT AG noticeno count stated+159d
  3. JAN 28ME AGME AG noticestates nationwide total 62,692+159d
  4. JAN 28MA AGMA AG notice105 MA residents+159d
  5. JAN 28MT AGMT AG notice27 MT residents+159d
  6. JAN 28NE AGNE AG noticefiling day not on record · no count stated—
  7. JAN 28CA AGCA AG noticeno count stated+159d
  8. JAN 28IN AGIN AG noticestates nationwide total 63,921+159d
  9. FEB 3NH AGNH AG notice6 NH residents+165d
  10. FEB 12CA AGCA AG noticeno count stated+174d
  11. FEB 12VT AGVT AG noticeno count stated+174d
  12. FEB 20NH AGNH AG noticemost recent · 7 NH residents+182d
  13. DEC 17MD AGMD AG noticefiling day not on record · 32 MD residents—
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 23, 2024
ME AG
Discovered
Aug 23, 2024VT AG + MT AG + CA AG +2Jan 15, 2025ME AG + NE AGfilings disagree on discovery
Data types
Credentials · Identity (basic) · Government ID · PII
VT AG + ME AG + MT AG +4
Attack vector
Unauthorized Access
VT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

63,921

Sum of filed state slices

228· 0.4% of stated

100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US63,921
MA105
IN55
MD32
MT27
NH7
ME2

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing12 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

23 days

Cadence

~1 / 2.6d

vs. multi-state median

3.8× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.