HackingTechnologyTransportation & LogisticsInformationStolen CredentialsCapture Stored DataData ExfiltratedCustomer Data InvolvedTargetedIdentity (basic)Government IDMediumContained

UBER TECHNOLOGIES, INC.

bd_e49463d64649434e · schema v1 · pii pii-v1

Severity

Medium

Discovered

Jan 31, 2023

Filed

Apr 3, 2023

To disclose

9 weeks

Affected

Not disclosed

Linked

5 filings

Confidence

65%

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

Uber Technologies, Inc. reported a data breach where an unauthorized third party accessed systems and exfiltrated driver data between Jan 23-31, 2023. Genova Burns, Uber's legal counsel, detected suspicious activity on Jan 31, 2023. Impacted data included names, SSNs, DOBs, and addresses. Uber engaged forensic specialists, changed passwords, notified law enforcement, and offered 12 months of identity monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 8 days

discovery → filing · 9 weeks / 62 days

Jan 23, 2023

Begins

Jan 31, 2023

Discovered

Mar 1, 2023

Scope determined

Apr 3, 2023

Filed

vs. sector median

10 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Maine State AGbd_175250c300d3a0672023-03-31 · +3dCandidate
Indiana State AGbd_6276a733491ccf822023-03-31 · +3dVerified
Montana State AGbd_9c3577144d8fc3102023-03-31 · +3dVerified
Massachusetts State AGbd_ddc7f89a54cf6ef52023-03-31 · +3dVerified

Name: UBER TECHNOLOGIES, INC.
norm: uber technologies

Name: UBER TECHNOLOGIES, INC.
norm: uber technologies
Industry: TechnologyllmTransportation & Logisticsllm

Discovered: Jan 31, 2023
Breach occurred: Jan 23, 2023 – Jan 31, 2023
Undetected for: 8 daysoccurrence → discovery
Materiality determined: Mar 1, 2023
Notification sent: —
Affected individuals: Not disclosed
Data types: Identity (basic)Government ID
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Notified law enforcement and is cooperating with its investigation
Initial access: valid_credentials

During the incident: Engaged outside forensic and data security specialists to investigate
Undertook a comprehensive review to determine what was impacted
Secured the environment by changing all system passwords
Notified law enforcement and is cooperating with its investigation
Offering 12 months of complimentary identity monitoring services through Kroll
Changes made: Taking additional steps to improve security and better help protect against similar incidents in the future
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 5 states

View merged incident ↗

Maine State AGMar 31 · first

Indiana State AGMar 31 · first

Montana State AGMar 31 · first

Massachusetts State AGMar 31 · first

New Hampshire State AG+3d · this page

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-20230403.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 3, 2023
Raw hash: 36a8a0e7b2d6cff5fbff2eaa9ad2badec73bf9770e560c28c713f299c542d29a

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityUBER TECHNOLOGIES, INC.

Victim entityUBER TECHNOLOGIES, INC.

Incidentdiscovered Jan 31, 2023

Stated responseEngaged outside forensic and data security specialists to investigate

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov