Gyft, Inc.
bd_c457021f6f189436 · schema v1 · pii pii-v1
Full breach record for Gyft, Inc. →Gyft, Inc. reported that an unknown party accessed without authorization two cloud providers used by Gyft from October 3 through December 18, 2015. The attacker could view or download user information including names, addresses, dates of birth, phone numbers, email addresses, gift card numbers, and potentially login credentials for users active between March 19 and December 4, 2015. No credit card numbers were compromised. Gyft forced password resets and reset Coinbase tokens for affected users.
J jump to incidentP pin to compareR raw source
Incident timeline
Oct 3, 2015
Begins
Feb 5, 2016
Filed
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Oregon State AGbd_28b6696925d8493f2016-02-05Verified
- Montana State AGbd_818e629a19d3271b2016-02-05Verified
- New Hampshire State AGbd_e585e4aa7bcd55df2016-02-05Verified
- Washington State AGbd_267d04bc797267582016-02-04 · +1dCandidate
Show 2 more filings ↓Show fewer ↑up to 4d gap
- Massachusetts State AGbd_230b59e852602a1e2016-02-09 · +4dVerified
- Hawaii State AGbd_a6a861496184cd872016-02-09 · +4dVerified
Filing propagation · 7 filings · 7 states
View merged incident ↗Pattern: first filing Feb 4 (WA), last Feb 9 (HI) — a 5-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.