Yesway — May 2023 breach

Clustered 4 filings across 4 jurisdictions · filing window Jan 24, 2024 → Jan 26, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

5,822

First → last filing

Jan 24, 2024 → Jan 26, 2024

Merge confidence

100%

incident inc_148def7501d3454a · merged by deterministic · confidence 100%

Part of the Paycor supply-chain incident (2023) — at least 16 organizations filed notifications naming this third party.

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe a third-party compromise. Intrusion May 29, 2023–Jun 1, 2023, discovered Nov 30, 2023 — the first regulatory filing landed 55 days later. 5,822 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

55days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

2days

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 clocksMaine⏱ ME AG >30d · 55dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.