Gracenote — May 2017 breach

Clustered 4 filings across 4 jurisdictions · filing window Jun 15, 2017 → Jun 23, 2017. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

First → last filing

Jun 15, 2017 → Jun 23, 2017

Merge confidence

100%

incident inc_e4498b530f684ae6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe a physical incident. Intrusion May 18, 2017, discovered May 19, 2017 — the first regulatory filing landed 27 days later. 1 individual reported across the linked filings. Data reported: Government ID, Identity (basic), and Employment. Notifications rolled out on a 8-day schedule across 4 filings beginning Jun 15, 2017. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

27days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

8days

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 clocksOregon✓ OR AG ≤45dFull 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.