UBER TECHNOLOGIES, INC.
bd_5aac63ae95779a49 · schema v1 · pii pii-v1
Full breach record for UBER TECHNOLOGIES, INC. →10 incidents on fileUber Technologies, Inc. notified the NH AG of a 2016 data breach where unauthorized actors accessed Uber's AWS environment using compromised credentials. The incident affected approximately 600,000 US drivers, exposing names and driver's license numbers. Access occurred Oct 13-Nov 15, 2016. Uber discovered the breach in Nov 2016 but delayed notification until Nov 2017, offering 12 months of credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
Oct 13, 2016
Begins
Nov 15, 2016
Discovered
Nov 21, 2017
Filed
vs. sector median
+35 wks slower
Linked disclosures
Why this link?Regulatory filings (5) · sorted by filing gap
- Montana State AGbd_74ccb250c0dca8c32017-11-21Verified
- Oregon State AGbd_8cb0530a7d7281d12017-11-21Candidate
- Washington State AGbd_cb676ca7c713e68b2017-11-21Verified
- California State AGbd_dfe6822f4d0881262017-11-21Verified
Show 1 more filing ↓Show fewer ↑up to 7d gap
- Massachusetts State AGbd_103b55f80b2fd5c62017-11-28 · +7dVerified
Filing propagation · 6 filings · 6 states
View merged incident ↗Pattern: first filing Nov 21 (MT), last Nov 28 (MA) — a 7-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.