Indigo Wild
bd_33162c0539929f6c · schema v1 · pii pii-v1
Full breach record for Indigo Wild →Indigo Wild notified the Washington AG of a data security incident discovered on April 17, 2017. Malicious code inserted into its e-commerce site by cybercriminals potentially exposed personal and payment card information of approximately 501 Washington residents for orders placed between November 14, 2016, and April 17, 2017. The company remediated the issue, notified payment networks and law enforcement, and sent notification letters on May 12, 2017.
J jump to incidentP pin to compareR raw source
Incident timeline
Nov 14, 2016
Begins
Apr 17, 2017
Discovered
May 12, 2017
Filed
vs. sector median
4 wks faster
Linked disclosures
Why this link?Regulatory filings (5) · sorted by filing gap
- Oregon State AGbd_17c8cdde05d621c92017-05-12Candidate
- New Hampshire State AGbd_b37750685fd2d4af2017-05-12Verified
- Massachusetts State AGbd_7148803d17e9d0252017-05-15 · +3dVerified
- California State AGbd_8c049d25fb0f53bc2017-05-15 · +3dVerified
Show 1 more filing ↓Show fewer ↑up to 25d gap
- Montana State AGbd_c1df3ed79fd2e5d32017-06-06 · +25dVerified
Filing propagation · 6 filings · 6 states
View merged incident ↗Pattern: first filing May 12 (OR), last Jun 6 (MT) — a 25-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.