Connect with us

NEWS

Uber Drivers Lost Licenses in an AI Token Heist

Hackers hunting LLM tokens at Fireworks AI also took Uber driver licenses in at least three states, plus Notion chats and a Cursor key.

Published

on

Uber is telling thousands of drivers that hackers stole their license data from Fireworks AI, an outside model vendor, not from Uber’s own systems. Filings already name 7,870 people in Massachusetts, South Carolina and Rhode Island.

The thieves were hunting tokens they could resell for unpaid access to large language models. Driver identities were sitting in the same place.

At Least 7,870 Licenses Sit in Three State Filings

Uber’s consumer letter is dated November 10, 2026. A vendor told the company on October 9 that an unauthorized party had stolen internal credentials and used them to reach Uber’s account. Uber said it cut data connections that day and, on October 13, confirmed that personal information of the people now being mailed had been accessed.

An Uber spokesperson said the notices “are in relation to a security incident impacting one of our third-party vendors, Fireworks.ai, which had access to some Uber data,” and pointed further questions at Fireworks. Uber has not published a nationwide total, and it has not described the exact workload that put driver files on that platform.

The Massachusetts Office of Consumer Affairs and Business Regulation listed 2,567 residents. The South Carolina Department of Consumer Affairs listed 3,430. Uber’s own notice puts the Rhode Island figure at about 1,873. Those three published counts add to 7,870, a floor, not a national tally. Illinois said some residents had license data taken and withheld the number. California received a notice with no headcount attached.

STATE FILINGS MADE PUBLIC

State People named What the filing shows
South Carolina 3,430 Driver’s license information listed
Massachusetts 2,567 Driver’s license information listed
Rhode Island 1,873 Named in Uber’s notice
Illinois Not published License data taken, count pending
California Not published Notice filed, no headcount

Uber told people it has not identified misuse of the stolen information. It is offering free credit monitoring and fraud help through Cyberscout, a TransUnion company, and it asked drivers to watch account statements and credit reports. More state notices can still land, so 7,870 should be read as the published floor on November 16, 2026, not a closed census.

The Thieves Came for Model Tokens

Fireworks, which sells developers access to open models, does not describe this as a raid on ride-hail identity files. In a November 9 update it tied the activity to a financially motivated group that wanted unpaid model access it could fence through illicit routing gateways, a pattern researchers call LLMJacking.

The evidence indicates links to a cybercriminal threat actor group, which is financially motivated and aimed at selling tokens from unauthorized access to Large Language Models (LLMs) to illicit routing gateways, known as “LLMJacking”.

Fireworks AI, November 9, 2026 security bulletin

Google Threat Intelligence Group and Mandiant, writing on November 2, 2026, said they had already spent the year on this market. In casework across financial services, retail, technology and transportation, they recorded fraudulent charges exceeding $100,000 in a day, and cumulative bills that reached $1 million at some organizations before access was cut. One actor ran more than 500,000 LLM API calls in under eight hours through a mixer that sold an “unlimited” plan for about $60 a month, against typical consumer pricing of $100 to $250.

Those dollar figures are Mandiant’s 2026 investigations, not Uber’s invoice. They explain the motive Fireworks named. Stolen cloud keys and model tokens now pay like a product. Identity documents, billing files and training traces are what a thief can copy once the same login is already inside the building.

No known group has taken public credit for the Fireworks theft. Palo Alto Networks’ Unit 42 is on the forensic work, Fireworks said, and law enforcement has been notified.

Two Break-Ins, Eighteen Days Apart

Fireworks’ first public bulletin, last updated October 10, is narrower than the November rewrite. On October 6 at 9am PDT it found unauthorized use of its own internal credentials. An outsider had read environment variables used in evaluation jobs in a limited number of customer accounts, capturing API keys and tokens stored as secrets. At that point the company said it had not seen access to customer models, datasets, training data, personal information or inference traffic inside its perimeter.

Containment started the same morning. Customer notices began October 7 at 7am PDT. Employee API keys were rotated on October 9, the same day Uber says it was told, and the first bulletin went up that night. That is the credential path that Uber later tied to driver data.

The second path came after that cleanup. A third-party cloud provider that hosted Fireworks research machines had its own incident on October 23. On October 24, 18 days after the first detection, the unauthorized party used that foothold to reach Fireworks development machines and run a workload that hit more customer data. Fireworks said it caught that activity the same day and, as of October 25, had not seen further successful access on the platform customers use.

THE OCTOBER CLOCK INSIDE FIREWORKS

  1. October 6, 2026, 9am PDT: Fireworks finds unauthorized use of internal credentials and starts containment.
  2. October 7, 2026: Customer notices begin; evaluation-job secrets are the known loss.
  3. October 9, 2026: Uber is told; it cuts data connections; Fireworks publishes its first bulletin.
  4. October 13, 2026: Uber’s investigation finds that Uber data, including personal information, was accessed.
  5. October 23, 2026: A cloud provider hosting Fireworks research machines has a security incident.
  6. October 24, 2026: The same unauthorized party reaches Fireworks development machines and runs a workload.
  7. October 25, 2026: Fireworks reports no further successful access on the customer platform.
  8. November 9, 2026: Fireworks widens the picture to billing data, secrets, datasets and incomplete models.
  9. November 10, 2026: Uber’s driver letters are dated.

The November update lists what an internal application could show after that second hop: resource metadata, billing and shipping addresses, invoices, payment history, account balances and credit usage, plus, for a limited set of accounts, secrets, datasets and incomplete model weights. Payment card numbers are not stored at Fireworks, the company said, and were not taken.

Driver Files Lived Beside the Model Jobs

Fireworks still says it has not detected impact to Inference, the Training SDK or Nexus, which it calls zero data retention by default. That sentence is doing a lot of work. The product path that answers a prompt and then forgets it is not the path that got hit.

Evaluation jobs are the scoring runs a lab uses to test a model against a set of examples. Those jobs take environment variables, and customers had parked API keys and tokens there as secrets. Research machines held datasets and unfinished weights. A read-only bucket used to share traces for training sat behind a vendor key. Notion later found chat transcripts from a classification feature living on Fireworks after the inference contract had promised not to keep traffic.

Uber has not said why driver license records were in that stack. The filing language is only that Fireworks had access to some Uber data and that an outsider used stolen vendor credentials to reach it. For a driver, the distinction is academic. The license number left through a lab that was supposed to be running models, and the people who took it came to selling tokens from unauthorized access, not to build a dossier on gig workers.

That is the ugly geometry of this incident. A zero-retention promise on live inference can be true on the product path and still leave identity files, billing ledgers and training leftovers in rooms the same login can open.

Notion, Cursor and the Same Vendor Key

Uber is the name on the state letters. It is not the only customer that has now said Fireworks held something the token thieves could copy. Notion and Cursor each published their own accounts, and the leftovers do not look alike, which is the point. One vendor key sat behind three different kinds of private file.

WHAT EACH CUSTOMER SAYS LEFT THE VAULT

  • Uber drivers: Personal information including driver’s license data, with 7,870 people named so far in three states and more notices possible.
  • Notion workspaces: Notion AI chat transcripts used for the Insights feature, touching fewer than 1% of Notion workspaces, most of them unattributable.
  • Cursor users: Coding-agent traces, mostly from 2025 and outside Privacy Mode, after an attacker used an access key issued to Fireworks to copy a shared read-only bucket.

Fireworks first pinged Notion on the evening of November 2 and described a small set of data that Notion found was synthetic test material. By the morning of November 3, Notion had cut every connection. It deleted the data sitting in Fireworks on November 4. On November 6 the vendor said customer data might have been reached. On November 8 it confirmed the final set. Notion mailed affected customers on November 9.

Those transcripts powered Insights, a feature that classified how people used Notion AI. Notion says that for the vast majority of hit workspaces the chats were not labeled with a person or a workspace and held no tool-call results. It told customers to treat the data as exposed, rotate any passwords or keys pasted into Notion AI, and note that Insights is off and open-weight models are no longer served through Fireworks. On November 11 it revoked exposed Notion API keys found in those messages. On November 12 it reported third-party keys from the same messages to the vendors that issued them.

Cursor’s November 13 incident update is blunter. “It started at Fireworks,” the company wrote. The key Cursor had issued to the vendor was exposed there, and the attacker copied a bucket of traces Cursor was allowed to use for model training. A small number of those traces still held credentials. Cursor puts trace exposure at fewer than 0.05% of users outside Privacy Mode, and API-credential exposure at less than 0.01% of customers. From there the attacker reached some of Cursor’s SaaS tools and, on October 29, placed a malicious unauthorized copy of Anthropic’s Claude Code extension in the cache that serves Cursor’s VS Code marketplace. Privacy Mode prompts and code were not in the traces. Cursor moved all inference off Fireworks, killed the key, and rebuilt the marketplace.

Oludare Ogunlana, a professor who writes on cyber privacy, put the common failure in one line on November 16: the model did not leak the data, the decision to send it there did. A zero-retention clause is a claim until someone tests where the copies actually live.

August Already Brought a Freight Extortion Claim

This is Uber’s second known data incident of 2026, and the first one did not run through Fireworks. In August the Helix extortion group listed Uber Freight, the trucking and logistics unit, on a leak site and claimed nearly 1 million files from mailboxes, cloud drives, accounts-payable material and dispatch documents.

Sam Hallock, a spokesperson for Uber Freight, said the unit was investigating unauthorized access to a portion of its systems and repositories, that the incident had been identified, contained and remediated, and that federal law enforcement had been engaged. He said operations continued without disruption. Uber Freight did not confirm Helix’s file count or say whether it paid.

The two events do not share a method. Helix is an extortion brand that dumps files and asks for money. The Fireworks crew, per the vendor, came for model tokens. For a driver reading a November letter, that split is cold comfort. In one calendar year the parent company has now had a logistics unit in an extortion claim and a ride-hail driver file sitting at an AI vendor that got popped twice in October.

What Should Affected Uber Drivers Do?

The useful document is the letter, not the headline. Uber’s sample notice leaves the data-elements field as a placeholder, so the only way to know which fields were in a given file is to read the copy that arrived in the mail. Massachusetts has already said license information was among what was involved. Other states may list different mixes.

STEPS THE NOTICE POINTS TO

  • Read the letter: Confirm you are in the notified group and see which data types Uber listed for you, because the public sample does not fill that field.
  • Enroll in Cyberscout: Uber is paying for credit monitoring and fraud assistance through Cyberscout; use the code and deadline printed on your notice, not a number from a stranger on the internet.
  • Watch statements: Uber asked people to review account statements and credit reports and has said it has not identified misuse so far.
  • Freeze credit if you want a harder stop: A freeze at the major bureaus is a separate step from the free monitoring offer and is something a driver can place without waiting on Uber.

Riders looking for trip history or card numbers in this incident will not find them in the filings that have surfaced. The notices on file are driver notices. That does not make a license number a small thing. It is a government ID, it is hard to rotate, and it is now in the hands of a group that, if Fireworks is right, came to steal compute and will sell whatever else copies easily.

Fireworks is still in active monitoring. Notion is still investigating. Cursor says the last attacker activity it saw was blocked. Uber’s count is still open in California and Illinois. The licenses named in those three state filings are not coming back off the market because a vendor rotated keys.

Disclaimer: This article is news reporting on public breach notices, vendor bulletins and company statements, and it is for information only. It is not legal advice, identity-theft counseling, or a recommendation to enroll in or skip any credit-monitoring product. Readers who received an Uber notice, or who think their license data may have been involved, should read the letter they were sent and consult a qualified attorney or a consumer-protection office in their state before taking action that has legal or credit consequences. Headcounts, enrollment windows and investigation findings reflect the filings and bulletins cited here and can change as more states publish numbers or as Fireworks, Uber, Notion or Cursor update their accounts.

Harry is the editor of COVER 365, an independent publication he owns and runs, and a journalist of ten years who moved from reporting into editing. Anything the site reviews has been used before it is judged. A phone, a car, a game or a piece of travel gear is tested in ordinary conditions, its measured results are set against the maker's specification sheet, and where the two disagree the article says which one to trust and why. No product gets a verdict Harry has not earned by using it. Off the test bench, the same rule of primary evidence applies: business stories come from filings and results, science from the published paper, sports from the governing body's records, and news from statements and transcripts rather than second hand accounts. Coverage runs across technology, auto, gaming, lifestyle and travel as well as news, business, science, sports and entertainment, for readers in every part of the world. Every figure is checked before publication and corrected publicly under a stated policy when wrong. Reader mail is answered at support@cover365.in.

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending