HackingTechnologyInformationStolen CredentialsData ExfiltratedCustomer Data InvolvedIdentity (basic)Government IDMediumContained

UBER TECHNOLOGIES, INC.

bd_6586a4d42eaf86cf · schema v1 · pii pii-v1

Severity

Medium

Discovered

Sep 17, 2014

Filed

Feb 26, 2015

To disclose

23 weeks

Affected

15state residents only

Linked

3 filings

Confidence

66%

Full breach record for UBER TECHNOLOGIES, INC. →10 incidents on file

Uber Technologies, Inc. notified the NH Attorney General of a security breach affecting 15 NH residents. Unauthorized access occurred on May 13, 2014, involving names and driver's license numbers. Uber discovered the vulnerability in September 2014, secured the database, and offered credit monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 127 days

discovery → filing · 23 weeks / 162 days

May 13, 2014

Begins

Sep 17, 2014

Discovered

Feb 26, 2015

Filed

vs. sector median

+5 wks slower

This filing is one of 3 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

California State AGbd_5994ff85006d8e3f2015-02-27 · +1dCandidate
Massachusetts State AGbd_947a87111b7852212015-03-04 · +6dVerified

Name: UBER TECHNOLOGIES, INC.
norm: uber technologies
Domain: uber.com

Name: UBER TECHNOLOGIES, INC.
norm: uber technologies
Domain: uber.com
Industry: Technologyllm

Discovered: Sep 17, 2014
Breach occurred: May 13, 2014
Undetected for: 127 daysoccurrence → discovery
Materiality determined: —
Notification sent: Feb 26, 2015
Affected individuals: 15state-resident count only
Data types: Identity (basic)Government ID
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: External
Regulator citations: Notified New Hampshire Department of Justice
Initial access: valid_credentials

During the incident: Uber immediately changed the access protocols for the database
Uber is sending notification of the incident to all individuals whose information was contained in the files
Offering a complimentary one-year membership of Experian’s ProtectMyID Alert
Changes made: Taken additional safety measures to protect your information
Ensured that the database was no longer accessible using that information
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 23 weeks(162 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

New Hampshire State AGFeb 26 · first · this page

California State AG+1d

Massachusetts State AG+6d

Pattern: first filing Feb 26 (NH), last Mar 4 (MA) — a 6-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://mm.nh.gov/files/uploads/doj/remote-docs/uber-technologies-20150226.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 26, 2015
Raw hash: 7e21f5e9295529057255494eff6e68f2e6e72150423511d7412dd615f887c2f1

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityUBER TECHNOLOGIES, INC.

Victim entityUBER TECHNOLOGIES, INC.

Incidentdiscovered Sep 17, 2014

Stated responseUber immediately changed the access protocols for the database

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov