Skip to content
The Cybersecurity Focus
The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

  • Home
  • Home
The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

  • Home
  • Home
BreachexploitVulnerability

Uber Data Breach Exposes Drivers’ Personal Records

By ogwatermelon
November 17, 2026 5 Min Read
0
November 17, 2026

Uber confirmed a data breach that exposed the personal information of 149,346 drivers after hackers compromised AI infrastructure provider Fireworks AI. The stolen records include names, home addresses, dates of birth, driver’s license numbers, and images of driver’s licenses stored in a cloud environment Uber built for the vendor.

What Happened: Uber Data Breach Exposes 149,346 Driver Records

Uber is notifying 149,346 people that hackers stole their personal information during an October 2026 incident at one of the company’s third-party service providers. The ride-hailing giant confirmed to TechCrunch that the provider was Fireworks AI, a platform that lets developers run open-weight large language models such as Mistral, Llama, and Gemma.

Uber’s own notification letters, filed with attorneys general in California, Iowa, Maine, Oregon, Texas, Vermont, Massachusetts, Rhode Island, Illinois, and South Carolina, describe the sequence of events. On October 9, 2026, the provider notified Uber that an unauthorized third party had compromised its internal credentials. Uber immediately severed its data connections and launched an investigation.

By October 13, Uber determined that the stolen credentials had been used to access Uber data connected to the service provider. Notification letters went out to affected individuals on November 10. The Oregon filing set the total at 149,346 affected people, and Uber has not ruled out further increases.

Technical Details of the Uber Fireworks AI Breach

How Attackers Entered the Environment

Fireworks AI disclosed two separate October incidents. In the first, attackers accessed environment variables holding API keys and tokens stored as secrets for a limited number of accounts. In the second, a third-party cloud provider hosting Fireworks R&D machines suffered a breach on October 23, and the attacker used that foothold on October 24 to reach Fireworks development machines and run an unauthorized workload.

That unauthorized workload gave the attacker access to the customer data Uber had stored in a dedicated cloud bucket. Fireworks attributed both incidents to a financially motivated cybercriminal group that sells stolen model tokens for resale through illicit LLM routing gateways, a technique known as LLMjacking.

Why Detection Failed

Uber said its Fireworks environment was subject to its cloud security management processes and overseen by its Cloud Security team. Monitoring was in place. However, no alerts fired because the attacker used the provider’s own valid internal credentials rather than anything anomalous. The compromise of the vendor’s system is what allowed the access to proceed quietly.

Uber also noted that the provider’s compromised credentials did not grant access to other Uber systems. The blast radius was limited to the storage environment Uber created specifically to support the vendor’s work.

What Was Actually Stolen

  • Identity data: Full names, home addresses, and dates of birth.
  • Driver’s license data: License numbers plus images of the physical licenses.
  • Vendor-side data: Resource metadata, billing and shipping addresses, invoice and payment history, account balances, credit usage, and incomplete model weights and datasets.

Fireworks said it does not store customer payment card numbers, so card data was not exposed in the vendor’s environment. However, Uber’s driver records included license images, which are a common target for identity fraud and synthetic identity schemes.

Business and Operational Impact

This Uber data breach lands on a company with more than 149,000 driver identities now circulating, and it connects to a wider pattern of third-party AI vendor compromise. Notion and Cursor have also confirmed losses from the same Fireworks incident, and Mandiant reports LLMjacking cases across North America, South America, and Asia Pacific in financial services, retail, technology, and transportation.

  • Identity fraud risk: Stolen names, dates of birth, addresses, and driver’s license images are a complete identity-theft kit. Synthetic identity fraud and fraudulent driver’s license applications are the primary downstream risks.
  • Regulatory exposure: Uber filed breach notices across at least ten US states. Driver’s license data falls under state privacy statutes and DMV identity requirements, which typically trigger mandatory notification and regulatory penalties for inadequate safeguards.
  • Third-party concentration risk: A single AI vendor compromise exposed data for multiple customers at once. Any company that stores regulated data with an AI or cloud vendor shares this blast radius.
  • Detection gap exposure: Valid-credential abuse from a trusted vendor bypassed monitoring entirely. This is a blind spot for most identity and cloud security tooling that alerts on anomalous behavior.
  • Financial cost pressure: Uber reported $14.8 billion in quarterly revenue. Notification, credit monitoring, legal defense, and potential class-action settlements add material cost, and reputational damage affects both drivers and riders.

Mitigation and Recommendations

Immediate Actions for Defenders

  1. Inventory every third-party AI and cloud vendor that holds sensitive data in your environment, especially identity, license, and financial records.
  2. Rotate all credentials and access keys shared with those vendors, then revoke and reissue any secrets stored in environment variables or CI/CD pipelines.
  3. Audit provider-side access logs rather than relying on your own anomaly detection, since trusted-credential abuse may never trigger your alerts.
  4. Segment vendor data into dedicated storage accounts with no path to production or identity systems.
  5. Require vendors to notify you within a fixed window, with contractual rights to audit their credential handling.

Guidance for Affected Drivers

Drivers who received a notification should treat their license image as a live credential. Monitor credit card and bank accounts for unauthorized charges, and place a fraud alert with the major credit bureaus. Also watch for fraudulent license renewals, insurance claims filed in your name, and synthetic identity accounts opened using your date of birth and address.

Because the exposed data includes license images rather than numbers alone, replacing the physical license may be necessary. Affected individuals should confirm with their state DMV whether a new card with a new number is warranted.

Furthermore, companies that bought LLM inference from Fireworks should audit their cloud bills for unauthorized usage. GTIG and Mandiant reported LLMjacking campaigns driving cloud AI charges as high as $1 million through fraudulent calls on stolen API keys.

Bottom line: This Uber data breach is a textbook case of concentration risk meeting a detection blind spot. Attackers did not need a vulnerability in Uber’s stack. They used a valid vendor credential, and the monitoring never fired. Review what your AI and cloud vendors can reach, and treat that reach as equivalent to your own production access.

Key Information

Incident: Uber third-party data breach via Fireworks AI (October 2026)
Affected Records: 149,346 drivers (names, addresses, dates of birth, driver’s license numbers and images)
Attribution: Financially motivated cybercriminal group conducting LLMjacking operations
Disclosure Date: November 10, 2026 (driver notifications); November 16, 2026 (vendor confirmed publicly)
Remediation Status: Credentials revoked and rotated by Uber and Fireworks; vendor access severed; Fireworks working with Unit 42
Related Victims: Notion, Cursor, and other Fireworks AI customers

References

  1. Sergiu Gatlan, “Uber notifies drivers of data breach affecting nearly 150,000 people,” BleepingComputer, November 17, 2026, https://www.bleepingcomputer.com/news/security/uber-notifies-drivers-of-data-breach-affecting-nearly-150-000-people/ (accessed November 17, 2026).
  2. Zack Whittaker, “Uber says hackers stole information on close to 150,000 driver’s licenses during data breach,” TechCrunch, November 16, 2026, https://techcrunch.com/2026/11/16/uber-confirms-hackers-stole-thousands-of-drivers-license-information-in-data-breach/ (accessed November 17, 2026).
  3. Jonathan Greig, “Uber says nearly 150,000 impacted by third-party breach,” The Record from Recorded Future News, November 16, 2026, https://therecord.media/uber-says-150000-impacted-third-party-breach (accessed November 17, 2026).
  4. Lawrence Abrams, “Fireworks AI discloses new breach after cloud provider hack,” BleepingComputer, November 16, 2026, https://www.bleepingcomputer.com/news/security/fireworks-ai-discloses-new-breach-after-cloud-provider-hack/ (accessed November 17, 2026).
  5. Fireworks AI, “October 2026 Security Incident Update,” https://fireworks.ai/security/bulletins/october-2026-security-incident-update (accessed November 17, 2026).
  6. Uber Technologies, Inc., Data Breach Notification, Maine Office of the Attorney General, November 2026, https://www.documentcloud.org/documents/28919097-maine-oag-uber-filing/ (accessed November 17, 2026).

Tags:

BreachExploitVulnerability
Author

ogwatermelon

Follow Me
Other Articles
Previous

Optimizely Supply Chain Attack Infects CNN, Fox News, BBC, and 175 Other Sites

Next

California Sues OpenAI Over AI Agents Escaping Sandboxes

AI Android Backdoor Botnet Breach Cloud CVE Exploit Hack Incident Infostealer KEV Linux Mac Malware Network News Phishing Ransomware RCE supp supply chain Virtualization Vishing Vulnerability Windows World Worm Zero Day

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Archives

  • November 2026
  • October 2026
  • September 2026
  • August 2026
  • July 2026
  • June 2026
  • May 2026

Categories

  • AI
  • Android
  • Apple
  • Backdoor
  • BotNet
  • Breach
  • Cloud
  • CVE
  • exploit
  • Hack
  • Incident
  • Infostealer
  • KEV
  • Linux
  • Mac
  • Malware
  • News
  • Phishing
  • Ransomware
  • RCE
  • supply-chain
  • Uncategorized
  • Virtualization
  • Vishing
  • Vulnerabilities
  • Vulnerability
  • Windows
  • World
  • Worm
  • Zero Day
Copyright 2026 — The Cybersecurity Focus. All rights reserved.