Uber Data Breach Impacts 150,000 People: Hackers compromised a third-party
Uber is notifying 149,346 drivers after hackers used compromised third-party vendor credentials to steal driver licenses and sensitive personal identification.
By Dillip Chowdary • Nov 16, 2026 • Source: SecurityWeek

At a glance
- Affected drivers
- 149,346 people
- Breach discovery
- October 9
- Credential compromise
- October 7
- Investigation confirmation
- October 13
- Third-party vendor
- Fireworks AI
- Remediation offer
- Free credit monitoring and fraud assistance
In this post
Uber is notifying roughly 150,000 drivers across the United States that their sensitive personal records and identity documents were compromised in an October data breach involving a third-party services provider, according to SecurityWeek's report. Attackers obtained authorized service credentials to enter a dedicated cloud environment managed by Uber's internal security team. The unauthorized access exposed driver names, residential addresses, dates of birth, and scanned government identification records without triggering active system alarms.
This report details the technical discovery timeline, the scope of exposed driver records, regulatory filings across multiple state attorneys general, and the involvement of generative machine learning vendor Fireworks AI. It is written for platform drivers evaluating their identity exposure, fleet operators managing regulatory compliance, and cloud security engineers auditing service provider credential delegations. Readers will find verified incident dates, affected population totals, and remediation terms provided directly by corporate filings.
01Compromised credentials and the severed link
The security incident originated on October 7 when unauthorized actors used valid third-party credentials to penetrate the isolated data repository. Uber discovered the unauthorized intrusion two days later on October 9. Incident response teams severed all external network connections to the external contractor immediately upon discovery while initiating forensic reviews of recent transaction requests.
Internal forensic investigators worked through system logs to establish the initial point of entry and trace data movement. By October 13, investigators confirmed that threat actors specifically exploited authentication material belonging to the third-party services partner. The compromised access allowed the intruder to reach internal databases containing driver identification profiles that Uber had previously transferred for processing.
Uber confirmed that the compromised supplier credentials remained strictly confined to that single shared storage boundary. The external account lacked administrative rights or routing pathways into core operational infrastructure, dispatch dispatch systems, or passenger profile databases. Forensic teams found no traces of lateral movement originating from the hijacked integration endpoint into broader corporate networks.
02Valid logins and silent security alerts
The compromised files were stored in a dedicated cloud repository designed and operated directly by Uber's Cloud Security team. Engineers had implemented standard automated monitoring rules alongside threshold alerts across the infrastructure. Despite active security monitors, the intrusion generated no automated warnings because the threat actor authenticated using legitimate partner credentials.
Legitimate credential abuse bypassed baseline anomaly detection frameworks by mimicking scheduled data transfers between Uber and its supplier. Security monitoring tools evaluated the session as normal operational activity authorized under the vendor integration agreement. This absence of telemetry alarms permitted the intruder to browse and retrieve identity records across the shared partition before manual discovery.
Note: The service provider's compromised credentials did not provide access to other Uber systems, according to formal disclosures from the company. Investigators confirmed the boundary held secure during the intrusion, and the corporate security evaluation remains an active inquiry as technicians verify peripheral logging.
03Driver license images and government identity records
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
The stolen data assets included high-resolution images of physical driver licenses alongside structured identity records submitted during driver onboarding. Hackers harvested personal information containing full driver names, physical home addresses, and verified dates of birth. The breach exposed primary identity documents that drivers must submit to maintain active commercial driving status on the platform.
Beyond basic contact details, the exfiltrated records encompassed sensitive driver license numbers and official government-issued identification numbers. These records represent permanent identity data points frequently targeted in synthetic identity creation and downstream identity theft schemes. Uber confirmed that driver financial payment methods, passenger trip histories, and credit card numbers were not housed within this compromised storage environment.
The breach directly compromised the primary document scans drivers uploaded to satisfy state licensing regulations. Retaining unredacted driver license files in third-party processing environments creates elevated identity exposure when supplier authentication mechanisms fail. Company security personnel cataloged the exfiltrated database objects to determine the exact number of impacted drivers requiring mandatory state disclosures.
04State attorney filings and free credit monitoring
Uber submitted mandatory regulatory breach disclosures to state oversight agencies across the United States. Formal notification filings arrived at consumer protection offices in California, Iowa, Massachusetts, South Carolina, Texas, and Vermont. The report delivered to the Texas Attorney General's Office confirmed that the breach impacted a verified count of 149,346 drivers.
The company initiated direct communications to notify drivers whose files were accessed during the October intrusion. To mitigate consumer exposure, Uber is offering affected drivers enrollment in complimentary credit monitoring services alongside dedicated identity fraud resolution assistance. Impacted drivers received written instructions detailing how to activate identity restoration tools and place security freezes on major credit bureaus.
State data privacy statutes require commercial operators to notify affected consumers when government identification numbers are accessed without authorization. Regulators in California, Massachusetts, and Texas monitor disclosures to verify whether notifications occurred within required statutory periods. Uber documented the timeline from initial breach discovery on October 9 to formal credential revocation in its regulatory filings.
05Fireworks AI disclosures and model exposure
Breach notifications sent to state regulators omitted the vendor name, but an Uber spokesperson confirmed to TechCrunch that the incident involved Fireworks AI. Fireworks AI operates a specialized cloud infrastructure service dedicated to executing and fine-tuning open source artificial intelligence models. Uber shared data assets with the platform to support specific model workloads prior to the October credential compromise.
Fireworks AI initially claimed that forensic reviews showed no evidence of unauthorized access to customer personal information, trained weights, or uploaded data collections. However, in an updated public statement issued on November 9, the artificial intelligence vendor reversed its initial position. The company acknowledged that the cyberattack compromised account information, customer billing details, partial data collections, and unfinished AI models.
The security incident at Fireworks AI extended beyond Uber, impacting customer records at several other technology platforms including Notion and Apify. Vendor security personnel continue to audit shared infrastructure to trace unauthorized access to customer dataset directories and fine-tuning environments. The incident highlights vulnerabilities in third-party artificial intelligence supply chains where shared API credentials allow lateral exposure into sensitive corporate data.
Frequently asked questions
How many people were affected by the Uber data breach?
Uber reported to the Texas Attorney General's Office that the breach affected a total of 149,346 people. The incident primarily involved platform drivers whose personal data had been shared with a third-party services provider.
What personal information was stolen in the breach?
The compromised files included images of physical driver's licenses, full names, addresses, dates of birth, driver's license numbers, and government-issued identification numbers.
How did the hackers access the data without triggering security alerts?
The threat actor authenticated using valid, compromised credentials belonging to the third-party provider on October 7. Because the credentials were legitimate, automated security monitors configured by Uber's Cloud Security team did not trigger alerts.
Which third-party provider was involved in the security incident?
An Uber spokesperson confirmed that the incident involved Fireworks AI, a cloud platform used for running and fine-tuning open source AI models. Fireworks AI later acknowledged that customer datasets, incomplete models, and billing data were also affected.
Sources
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Advertisement