Uber says hackers stole driver license data via vendor Fireworks AI

Uber is notifying drivers that personal information and driver license data were stolen in an October 2026 incident at Fireworks AI, a third-party vendor that gives developers access to open AI models. According to TechCrunch, Fireworks told Uber on 9 October that unauthorized parties had used stolen internal credentials. State filings reported by TechCrunch list 2,567 people in Massachusetts, 3,430 in South Carolina and 1,873 in Rhode Island. Uber has not disclosed a nationwide total, and its notice letter is dated 10 November 2026. For businesses that automate work, the case shows that a vendor holding copies of personal documents can become the weak point, even when the business's own systems were not breached.
In short
- Uber says a stolen-credential breach at its AI vendor Fireworks AI exposed driver license data.
- State filings reviewed by TechCrunch list 7,870 people across Massachusetts, South Carolina and Rhode Island, with no national total.
- Uber's own systems were not described as the point of entry; the access ran through the vendor.
- Any business that sends personal documents to an AI tool should inventory those copies and set deletion dates.
- Rotate vendor-held keys and tokens when a vendor issues a breach notice.
What happened
According to TechCrunch, Uber is notifying drivers that their personal information and driver license details were taken in a security incident at Fireworks AI. Uber told TechCrunch the notices relate to a security incident affecting one of its third-party vendors, and it deferred further questions to Fireworks. Uber's notice describes access through the vendor and does not say attackers entered Uber's own systems.
Fireworks' own bulletin says it identified unauthorized use of internal credentials on 6 October 2026. It started containment that morning, rotated employee API keys on 9 October and revoked more user keys and service-account tokens on 10 October. A later part of the same bulletin series says a third-party cloud provider hosting Fireworks research machines suffered an incident on 23 October, and Fireworks reported no further successful access to its production platform as of 25 October, according to a separate report on its statement.
State filings are the only public count so far. The table below shows the three counts that TechCrunch reviewed.
| State | People named in filings |
|---|---|
| Massachusetts | 2,567 |
| South Carolina | 3,430 |
| Rhode Island | 1,873 |
Adding those three counts gives 7,870. That sum is arithmetic on the filings, not a nationwide figure. Illinois and California residents were also notified, but the reporting did not give a count for them, and TechCrunch expects the total to rise as more notifications come in.
Why it matters for businesses that automate work
Many automation tools copy documents, IDs and customer details into a vendor's cloud so that a model or workflow can read them. This case shows that the copy can be exposed without anyone breaking into the business that owns the data. The attackers in Fireworks' account were after access to the vendor's systems and model usage. The personal records were stored in an account the drivers never dealt with directly.
Reporting on the incident also notes that it is not clear why Uber held driver license details in a third-party AI account, and Uber has not published the full list of data types taken. For a business owner, the question is not only whether a vendor is secure. It is also whether that vendor needed the data in the first place.
What changes in practice
A business of any size that sends documents or personal data to an AI tool should start with a plain inventory. List each vendor that holds personal data, including ID images, bank details and contact lists. Then ask who at the business approved the copy and why it is still there.
- Ask whether the vendor needs an image of an ID, or whether a yes or no verification result would do.
- Set a deletion date for copies held by automation tools, and check that the vendor deletes them.
- When a vendor issues a notice, rotate any API keys and service tokens it holds. Fireworks' bulletin tells customers to rotate third-party credentials named in their notice.
- Ask the vendor how it protects its own internal accounts and whether it uses access restrictions on them.
- Keep a log of which tool accessed which record, so that a notice can be answered with facts.
Automation can route documents, cut the number of fields collected and keep a log of access. It cannot make a vendor's internal accounts safer. That is a contract and security question, and it should be settled before a tool is connected. The size of any exposure depends on how much data each tool holds, which a business has to measure for itself.
What to watch next
Several open questions will shape how this story develops. Illinois and California counts have not been published. Uber has not said whether it will keep working with Fireworks AI. Fireworks' bulletin index lists an update on the October 2026 incident dated 9 November 2026, and the company's later statements will show which data it confirms was involved. Each new state filing will add to the count, so the 7,870 figure should be treated as a floor, not a total.
Sources
How AiStaffo would automate this
AiStaffo would begin by mapping which vendor tools hold ID images, bank details or contact lists, and which of those copies the workflow actually needs. The automation would then connect the document intake to a verification step that returns a pass or fail result, so that the raw ID image is not stored in the AI tool. Logs would record which tool accessed which record and when, and reminders would prompt key rotation whenever a vendor sends a notice. The business owner still chooses which vendors are approved, sets retention periods and reviews each vendor's answers on its own account security. Book a free automation audit.
Questions people ask
Did Uber's own systems get hacked in the Fireworks AI incident?
How many drivers were affected by the Uber driver license breach?
What should a driver do after receiving an Uber breach notice?
What did Fireworks AI say caused the breach?
Should a business stop using AI vendors after a breach like this?
Book a free automation audit
Thirty minutes. We look at one process you run every week and tell you exactly what an AI worker would take off your desk, and what it would not.

































