Uber Fireworks AI Breach: Driver Licenses Stolen via Vendor Key

Uber confirmed on November 13, 2026 that hackers stole U.S. driver license data after compromising credentials at AI inference vendor Fireworks AI, according to TechCrunch and state breach filings the outlet reviewed. The rideshare company says Fireworks.ai had access to some Uber data as a tech provider; when Fireworks' October incident spilled vendor keys, attackers pivoted into Uber's account with that provider.

This is the enterprise tail of the same Fireworks wave that already touched Notion AI transcripts, Cursor agent traces and marketplace malware, and model-weight theft via LLMjacking. For teams plugging customer PII into fine-tuning or eval pipelines, Uber is the reminder that inference vendors are data processors, not opaque GPUs.

TL;DR: confirmed timeline

Agents that act on your behalf need rules. See how explainx helps secure your agents →

How the vendor chain broke

Fireworks sells hosted open-model inference and training to enterprises that want proprietary data near model weights. Forbes and industry reporting have long listed Uber among Fireworks' customer set alongside Shopify, DoorDash, and developer tools like Cursor—always treat named customer lists as press attribution until each company confirms scope.

TechCrunch quotes an Uber spokesperson: notices to drivers relate to "a security incident impacting one of our third-party vendors, Fireworks.ai, which had access to some Uber data." Uber deflected operational questions to Fireworks, while Fireworks confirmed unauthorized access affecting customer data without answering Uber-specific follow-ups in the same article.

The mechanics match credential theft → SaaS pivot, the pattern Alex Stamos called breach chaining through AI suppliers in coverage we summarized for Decoder's cybersecurity episode. Attackers did not need a zero-day in Uber's ride stack; they needed working API keys at a model vendor Uber trusted with sensitive fields.

What we know about affected drivers

TechCrunch reviewed attorney general breach filings showing driver's license information among stolen fields:

Uber did not publish a global total when TechCrunch went to press, and the outlet expects more filings as states process notices. Reuters' November 13 summary aligns: roughly 1,873 in Rhode Island, with letters also going to residents of Washington, D.C., Maryland, North Carolina, New York, and Pennsylvania.

Misuse: Uber says it had not identified misuse of the data in the notifications TechCrunch saw. Drivers should still assume identity theft risk because driver's licenses are high-value fraud documents.

Remediation Uber offered

Breach letters described 90 days of complimentary credit monitoring and fraud assistance through Cyberscout, a TransUnion company, with enrollment within 90 days of the letter date—details NDTV Profit and other outlets echo from WSJ reporting.

That is standard post-breach hygiene, not a substitute for DMV account monitoring or fraud alerts if your state offers them. If you drive for Uber and received no letter, that does not prove your license was absent from the accessed bucket; it may reflect state filing lag or different data classes stored with Fireworks.

Fireworks attribution and LLMjacking context

Fireworks told TechCrunch it attributed activity to a financially motivated cybercriminal group seeking to sell tokens for LLM access—the same LLMjacking economy Google's GTIG research popularized. No group publicly claimed the Uber data slice as of TechCrunch's reporting.

The important builder lesson: thieves may monetize tokens first and still exfiltrate PII sitting beside API logs, billing tables, or evaluation datasets. Treat driver licenses in a training bucket as regulated personal data, even if your primary use case is RAG over support tickets.

How this differs from Cursor's Fireworks story

Cursor's November 13 post emphasizes coding-agent traces, internal SaaS pivot, and marketplace malware. Uber's disclosure emphasizes regulated identity documents for gig workers.

Same vendor, different blast shapes:

Cursor moved inference off Fireworks after discovery. Uber cut data connections with the provider. Neither action retroactively deletes exfiltrated files.

What enterprises should do now

A shield with a question mark marks vendor risk review after the Uber Fireworks AI breach

If you send PII, licenses, or financial fields to any inference host:

1. Map subprocessors — Fireworks-class vendors belong in SOC 2 review tier zero, same as your primary cloud.
2. Minimize fields — Do not park driver licenses in fine-tuning buckets if embeddings suffice; redact in traces.
3. Rotate keys — Assume October 2026 Fireworks keys are burned; scan repos for stale references.
4. Contract language — Require breach notice SLAs and delete-on-termination for customer artifacts.
5. Monitor vendor status pages — Uber learned on Oct 9; your runbooks should beat weeks-late AG filings.

For agent-specific controls—blocking dangerous tool calls after credential theft—teams deploying coding agents pair vendor reviews with runtime guardrails. AgentBeam's overview of the Cursor–Fireworks chain walks through how to detect and contain supplier-key pivot patterns if your product orchestrates third-party models.

Second Uber breach in 2026

TechCrunch notes this is Uber's second known data breach in 2026, after an Uber Freight incident where an extortion gang claimed credit. The Fireworks case is vendor-mediated, not freight-specific, but it reinforces that AI supply chain incidents now sit beside traditional ransomware on Uber's risk register.

How state breach notifications work (and why totals lag)

U.S. breach law is state-by-state, which is why TechCrunch could cite Massachusetts, South Carolina, and Rhode Island counts days before Uber published a single national number. California's attorney general portal hosts the notice Reuters summarized: Uber learned October 9, confirmed access October 13, and began mailing drivers thereafter.

Drivers in California may receive letters even when a public count is missing—TechCrunch explicitly says Uber notified California residents without publishing how many. If you run gig platforms or marketplaces, mirror this sequence in your vendor incident runbook: assume AG filings will expose your vendor's name before your press shop is ready.

Notion, Cursor, and Uber: one vendor, different data classes

explainx.ai already documented Notion AI transcripts and Cursor traces in separate posts. Uber adds government-issued ID numbers—a higher regulatory tier under state breach laws and FTC expectations for identity theft prevention.

Fireworks attributed the intrusion to LLMjacking-oriented criminals, but driver licenses are not useful for reselling Claude tokens. That mismatch suggests either opportunistic full-bucket exfiltration or multiple actors in the same environment—exact attribution remains vendor-stated, not court-proven.

Checklist for teams still on Fireworks (or similar hosts)

Use this whether you build ride-hail models or code agents:

• Inventory integrations — grep infrastructure for fireworks.ai endpoints; map which buckets include PII vs embeddings-only.
• Rotate keys — treat Q4 2026 keys as compromised if they ever reached Fireworks eval buckets.
• Move inference — Cursor's public response was to leave Fireworks entirely; weigh whether your threat model requires the same.
• Red-team vendor SSO — stolen vendor creds bypassed Uber application controls; test subprocessor account monitoring.
• Update SOC 2 answers — auditors will ask whether your AI subprocessors stored government IDs this quarter.

Questions gig workers search after breach headlines

Is my Uber account hacked? Uber's notices target drivers whose license data sat with Fireworks, not every rider account. If you received no letter, Uber's filings still allow for future state totals.

Was Fireworks hacked? Fireworks confirmed unauthorized access affecting customer data in its October 2026 bulletins—see our main Fireworks timeline.

Should I stop driving for Uber? The breach is a document exposure event, not proof of ride-hailing system compromise. Practical steps are credit monitoring enrollment and DMV fraud watches, not account deletion by default.

Regulatory and industry read

State AG filings turn private vendor incidents into public counts, which is why thousands became headline news before Uber issued a global total. EU and U.S. AI Act procurement clauses increasingly ask whether training vendors also store production PII—Uber answers yes, for some driver fields.

Congressional chip-export drama is unrelated technically, but the same week shows trust erosion across U.S. technology stacks: buyers scrutinize who touches data, not only who ships silicon.

Related reading

• Fireworks October 2026 breach: weights, billing, LLMjacking
• Cursor ties Fireworks key to agent traces and malware
• Notion AI transcripts on Fireworks
• November 2026 cyberattacks tracker
• Hugging Face on open-hub security tradeoffs
• What is an agent harness?
• Chainalysis breach lessons for agentic credential theft

Facts reflect TechCrunch's November 13, 2026 reporting and state breach notices cited there unless another primary source is linked.