State AGConfirmed6 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 6 filings
GS1 US — July 2017 breach
Clustered 6 filings across 6 jurisdictions · filed Oct 25, 2018. View entity profile → Other incidents for this victim →
⚠ 1 cross-filing discrepancy →Merge100%
incident inc_34503387297f4140 · merged by deterministic · confidence 100%
Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe unauthorized access. Intrusion Jul 7, 2017–Oct 2, 2018, discovered Oct 1, 2018 — the first regulatory filing landed 24 days later. 78,907 individuals reported across the linked filings. Data reported: PCI, Financial account, Identity (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.
Litigation Timing
SupplementalNotification delay
24days
Discovered → first regulatory filing
Discovery variance
0days
Range of discovered_at dates across filings
Filing span
0days
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 clocksCalifornia✓ CA 60-day OK · 24dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline
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.