DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79
State AGConfirmed5 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

UFCW Local 342 — April 2025 breach

Clustered 5 filings across 4 jurisdictions · filing window Mar 9, 2026 → Mar 23, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

4

Affected · reported

56,615

First → last filing

Mar 9, 2026 → Mar 23, 2026

Merge confidence

100%

incident inc_fdb97072055a4771 · merged by deterministic · confidence 100%

Confirmed breach. One breach, 5 legal records. Intrusion Apr 25, 2025–Apr 28, 2025, discovered Apr 28, 2025 — the first regulatory filing landed 315 days later (flagged late). 56,615 individuals reported across the linked filings. Notifications rolled out on a 14-day schedule across 5 filings beginning Mar 9, 2026. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
315days

Discovered → first regulatory filing

Discovery variance
290days

Range of discovered_at dates across filings

Filing span
14days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 25, 2025breach begins
Apr 28, 2025discovered · members disagree
notification delay · 315 days
Mar 9, 2026first filing
Mar 23, 2026most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAR 9ME AGME AG noticefirst filing · states nationwide total 56,615day 0
  2. MAR 9MA AGMA AG notice105 MA residentsday 0
  3. MAR 12NH AGNH AG notice15 NH residents+3d
  4. MAR 20VT AGVT AG noticeno count stated+11d
  5. MAR 23NH AGNH AG noticemost recent · 15 NH residents+14d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 25, 2025
ME AG
Discovered
Apr 28, 2025NH AGFeb 12, 2026ME AGfilings disagree on discovery
Data types
Government ID · Identity (basic) · Financial account
ME AG + MA AG + NH AG +1
Attack vector
Unauthorized Access
ME AG
Response
Secured our network · Reported the incident to law enforcement · Commenced a prompt and thorough investigation
NH 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)

56,615

Sum of filed state slices

150· 0.3% of stated

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

US56,615
MA105
ME30
NH15

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing5 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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
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

14 days

Cadence

~1 / 3.5d

vs. multi-state median

2.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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.