All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed11 records · 10 statesUnverified claimConfirmedEnforceddunghillhigh sensitivity

Merged incident · 11 records

SYSCO CORPORATION — January 2023 breach

Clustered 11 records across 10 jurisdictions: 10 filings and 1 leak-site claim · filing window May 5, 2023 → May 17, 2023 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 records

States

Affected · reported

126,243

First → last dated filing

May 5, 2023 → May 17, 2023

Merge confidence

100%

incident inc_686d2c50068c46bd · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jan 14, 2023–Mar 5, 2023, discovered Jan 14, 2023. 126,243 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Notifications rolled out on a 12-day schedule across 9 dated filings beginning May 5, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Discovery variance

50days

Range of discovered_at dates across filings

Filing span

12days

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 clocksOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 68dWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 73dHawaii✓ HI CRA notice dueSouth Carolina✓ SC CRA notice dueMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 14, 2023breach begins

Jan 14, 2023discovered · members disagree

May 5, 2023first dated filing

May 17, 2023most 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

JAN 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
MAY 5IN AGIN AG noticefirst filing · states nationwide total 126,243operator-confirmedday 0
MAY 16NH AGNH AG notice199 NH residentsoperator-confirmed+11d
MAY 16OR AGOR AG noticestates nationwide total 126,243operator-confirmed+11d
MAY 16CA AGCA AG noticeno count statedoperator-confirmed+11d
MAY 17HI AGHI AG notice1,186 HI residentsoperator-confirmed+12d
MAY 17WA AGWA AG notice1,977 WA residentsoperator-confirmed+12d
MAY 17ME AGME AG noticestates nationwide total 126,243operator-confirmed+12d
MAY 17SC AGSC AG notice1,503 SC residentsoperator-confirmed+12d
MAY 17MA AGMA AG notice1,613 MA residentsoperator-confirmed+12d
MAY 27Leak sitedunghill postmost recent · attacker claim · unverifiedoperator-confirmed+22d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jan 14, 2023
Discovered: Jan 14, 2023IL AGMar 5, 2023NH AG + OR AG + CA AG +4filings disagree on discovery
Data types: Financial account · Identity (basic) · Government ID · PII
Attack vector: Unauthorized Access

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)

126,243

Sum of filed state slices

8,818· 7.0% of stated

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

US126,243

WA1,977

IN1,673

MA1,613

SC1,503

HI1,186

ME667

NH199

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 filing10 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

12 days

Cadence

~1 / 1.5d

vs. multi-state median

2.0× 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.