Indigo Wild — November 2016 breach

Clustered 6 filings across 6 jurisdictions · filing window May 12, 2017 → Jun 6, 2017. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

Affected · reported

1,354

First → last filing

May 12, 2017 → Jun 6, 2017

Merge confidence

100%

incident inc_f3791077abff4c0e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe unauthorized access. Intrusion Nov 14, 2016–Apr 17, 2017, discovered Apr 17, 2017 — the first regulatory filing landed 25 days later. 1,354 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, PCI, and 2 more. Notifications rolled out on a 25-day schedule across 6 filings beginning May 12, 2017. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

25days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

25days

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 ≤45dCalifornia✓ CA 60-day OK · 25dFull 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.