149,346 — the precise number Uber disclosed to Maine regulators — is now the tally of drivers whose personal information was taken after attackers breached an AI-training vendor and then accessed Uber data through a compromised third‑party account.
Scope and timeline of the incident
Uber notified nearly 150,000 drivers by letter on November 10 that their information had been accessed following a breach of a third‑party service provider. In a filing with Maine's Office of the Attorney General, Uber said the incident exposed the personal information of 149,346 drivers, including names, driver’s license numbers, dates of birth, and addresses.
Uber's account of events places the first notification from the service provider on October 9, 2026. "On October 9, 2026, a service provider notified Uber that an unauthorized third party had compromised the service provider's internal credentials and used them to access Uber's account with the service provider," Uber said. "After being notified of this incident, Uber immediately severed data connections with the service provider and launched an investigation. On October 13, 2026, our investigation determined that the unauthorized party had used the compromised credentials to access Uber data connected to the service provider."
How Fireworks and a cloud provider fit into the chain
Although Uber did not name the hacked service provider in its notifications, reporting from TechCrunch tied the incident to an October 24 security incident at AI training provider Fireworks, itself compromised after what TechCrunch described as a third‑party cloud provider hack. Fireworks has attributed the attack to a financially motivated cybercriminal group that it links to a pattern of large language model hijacking — sometimes called "LLMjacking."

Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scrambleCollateral incidents at Cursor and Notion, and malware delivery
The Fireworks compromise was not an isolated occurrence. According to reporting summarized in the same account, the Fireworks breach also led to security incidents at AI coding platform Cursor and the digital workspace platform Notion. Cursor reported that attackers stole data from a limited number of customers and, in Cursor's words, "infected users' devices with backdoor malware." Notion likewise reported data theft from a limited set of customers.
What Uber did after discovery
Uber says it severed the data connections it maintained with the service provider once it was notified and launched an investigation. The company told reporters and regulators that its investigation, concluded on October 13, determined that the compromised third‑party credentials had been used to access connected Uber data. BleepingComputer reached out to an Uber spokesperson for more information; the company was not immediately available for additional comment at the time the reporting was published.
What this means for drivers, security teams, and regulators
- Drivers: Nearly 150,000 drivers received notification letters on November 10; exposed fields include names, driver's license numbers, dates of birth, and addresses — data that can be used for identity theft and targeting of follow‑on scams.
- Security teams and vendors: The incident underlines a chain‑of‑trust risk created by third‑party and cloud provider relationships. Fireworks attributes the attack to a financially motivated group tied to LLMjacking, and the compromise propagated to other software vendors (Cursor and Notion), including the delivery of backdoor malware in Cursor's case.
- Regulators and enforcement offices: Uber placed this disclosure in a filing with Maine's Office of the Attorney General; the state filing records the detailed driver count and the types of data exposed and therefore is now part of the public record for regulatory review.
Uber's disclosure echoes the company's earlier public breach history: the report recalls a December 2022 disclosure involving a third‑party provider named Teqtivity and references long‑standing incidents the company has previously acknowledged, including a 2016 breach and a 2022 incident involving the Lapsus$ extortion group. In the current matter, the proximate vector reported by Uber was compromised service‑provider credentials, while reporting links that compromise to Fireworks and an upstream cloud provider.
The durable lesson in the facts assembled here is straightforward: credential compromise at one point in a supply chain can expose downstream customer data across multiple services. What the public record does not yet show — and what remains to be confirmed — is which cloud provider was the initial vector in the Fireworks incident and whether additional customers beyond those reported at Cursor, Notion, and Uber will disclose similar impacts.




