Skip to the content
AI and Cybersecurity Learning and Practice Center Test automation Open the Learning Center

IncidentAI infrastructure

Uber: hackers used Fireworks AI's internal credentials to reach its data, and 149,346 people were notified

HighUberFireworks AI

TechCrunch reported on November 13, 2026, and updated the story on November 16, that Uber confirmed a security incident at one of its third-party vendors, which Uber's spokesperson named as Fireworks.ai. Uber's notices show that names, addresses, dates of birth and driver's license numbers were stolen; its notice to Oregon's attorney general says it notified 149,346 people, and it has not said how many are drivers. TechCrunch lists notices in California, Iowa, Illinois, Massachusetts, Rhode Island, South Carolina, Texas and Vermont. Uber says Fireworks told it on October 9 that hackers had broken in, and that its alerts on its Fireworks environment did not fire because the attackers used Fireworks' own internal credentials. A Fireworks spokesperson confirmed unauthorized access to some of its systems that affected customer data and did not answer TechCrunch's questions. As TechCrunch reports it, Fireworks' own bulletin describes a financially motivated group seeking to sell LLM access tokens, and no group has claimed the theft.

Replay the attack step by step in the Learning Center

How it happened

  1. Hackers broke into Fireworks AI, an AI infrastructure provider, and Fireworks told Uber on October 9.
  2. They used Fireworks' own internal credentials to reach the Uber data it held, so the alerts Uber had enabled on its Fireworks environment did not fire.
  3. Names, addresses, dates of birth and driver's license numbers were stolen, and Uber filed breach notices with several state attorneys general.

Impact

Personal data and driver's license numbers of 149,346 people, per Uber's Oregon filing; Uber has not said how many are drivers.

The fix

Uber notified the people affected and filed notices with state attorneys general, and deferred other questions to Fireworks, which has not answered TechCrunch's questions. The Notion entry in this library lists what Fireworks says it changed after its October incidents.

Lessons

  • Your own alerts do not see an attacker who arrives with your vendor's credentials; ask what the vendor logs and tells you.
  • Share the least data you can with an AI vendor, and ask how long it keeps it.
  • One AI vendor's breach reaches all of its customers: Notion, Cursor and Uber have each traced an incident to Fireworks.

Sources