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

Ahold Delhaize — November 2024 breach

Clustered 10 records across 9 jurisdictions: 9 filings and 1 leak-site claim · filing window Jun 26, 2025 → Jul 1, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 records

States

9

Affected · reported

2,242,521

First → last dated filing

Jun 26, 2025 → Jul 1, 2025

Merge confidence

100%

incident inc_329e9de210664764 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Nov 5, 2024–Nov 6, 2024, discovered Nov 6, 2024. 2,242,521 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 2 more. Notifications rolled out on a 5-day schedule across 7 dated filings beginning Jun 26, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
5days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayRhode Island✗ RI AG >45dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 5, 2024breach begins
Nov 6, 2024discovered
Jun 26, 2025first dated filing
Jul 1, 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. APR 16Leak siteinc_ransom postfirst record · attacker claim · unverifiedday 0
  2. JUN 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JUN 26DE AGDE AG noticeno count stated+71d
  4. JUN 26IN AGIN AG noticestates nationwide total 2,242,521+71d
  5. JUN 26SC AGSC AG notice121,465 SC residents+71d
  6. JUN 26NE AGNE AG noticefiling day not on record · no count stated—
  7. JUN 26VT AGVT AG noticeno count stated+71d
  8. JUN 27MA AGMA AG notice77,112 MA residents+72d
  9. JUL 1RI AGRI AG notice8,787 RI residents+76d
  10. JUL 1NH AGNH AG noticemost recent · 48,958 NH residents+76d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 5, 2024 – Nov 6, 2024
DE AG
Discovered
Nov 6, 2024· 1d undetected
IL AG + DE AG + SC AG +4
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID
IL AG + DE AG + SC AG +5
Attack vector
Unauthorized Access
DE 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)

2,242,521

Sum of filed state slices

259,854· 11.6% of stated

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

US2,242,521
SC121,465
MA77,112
NH48,958
RI8,787
IN3,532

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 filing9 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
Reviewed
operator-reviewed Aug 23, 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

5 days

Cadence

~1 / 0.8d

vs. multi-state median

1.2× faster

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.