Most companies never meet the firms that run their AI features. Notion rents inference from Fireworks AI; Uber, according to its breach filings, kept data with the same vendor. When attackers broke into Fireworks in October, the damage therefore landed two companies away from the one that was breached — on Notion users whose AI chats were sitting in a vendor’s storage, and on Uber drivers whose license details were there too.

Fireworks says it spotted the first intrusion on October 6, when an attacker captured environment variables — including API keys and tokens stored as secrets — from evaluation jobs belonging to a limited number of customer accounts. It began notifying affected customers the next day and published a public bulletin on October 10. A second intrusion followed on October 24, after a cloud provider hosting Fireworks’ research machines was itself compromised the day before. That round reached billing records, resource metadata, and, for some customers, incomplete model weights and datasets.

The picture kept widening for weeks. Fireworks told Notion on the evening of November 2 that a small dataset had been accessed; Notion cut its systems off from the vendor the next morning and deleted its data there. On November 6 Fireworks warned that customer data might be involved, and on November 8 it confirmed the final dataset. Uber’s breach notices, filed with state attorneys general and reported by TechCrunch on November 13, then showed the same break-in had reached driver identity documents.

A laptop showing a blurred chat conversation, with a driver's license card and an open padlock on the desk beside it
Illustration: an AI chat on a laptop and an exposed driver's license — the two kinds of data the Fireworks breach reached. (AI Frontier Post illustration)

Notion: chats collected for analytics, then exposed#

Notion used Fireworks for two jobs: classifying chats for Insights, a feature that shows workspace owners how their teams use AI, and serving open-weight models inside Notion. The exposed data was the first kind — Notion AI chat transcripts gathered to feed Insights statistics on use cases and conversation counts.

Notion says fewer than 1% of its workspaces were affected, and that for most of them the transcripts are “unattributable”: they carry no label naming the person who wrote them or the workspace they came from, and they do not include tool call results. “Beyond what’s in the chat transcript itself, there’s no information tying the chat back to workspaces, users, or companies,” the company said. The caveat, noted by The Register, is that the text of a chat can itself contain identifying details — and credentials, if anyone pasted them in.

Notion began contacting affected customers on November 9, and on November 11 it revoked Notion API keys its investigators found inside affected messages. It has disabled Insights, stopped serving open-weight models through Fireworks, and told affected workspace owners to treat the transcripts as exposed and rotate any passwords or API keys pasted into Notion AI. Its own systems, Notion says, were not breached — the data sat with a vendor running behind its product.

Uber: drivers’ license details in the same breach#

Uber’s filings tell the other half of the story. Fireworks told Uber on October 9 that hackers had broken in and stolen internal credentials; Uber’s investigation found on October 13 that those credentials had been used on October 7 to reach Uber data, including images of drivers’ licenses and extracted text such as name, address, date of birth, and license number.

State filings so far count at least 7,870 affected drivers across Massachusetts (2,567), South Carolina (3,430), and Rhode Island (1,873), plus about 2,999 more in Iowa. Counts for Illinois and California residents have not been published, and Uber has not disclosed a national total, so the figure will almost certainly grow. Uber says it has cut its data connections with the provider, has not identified any misuse of the data, and is offering free credit monitoring through Cyberscout, a TransUnion company.

Neither company has explained why driver identity documents sat in an AI inference vendor’s environment, and reporting so far does not say which of the two intrusions exposed the Uber records. It is the second known Uber breach this year, TechCrunch counts, after an Uber Freight intrusion claimed by an extortion gang.

The gap in “zero data retention”#

Fireworks’ public documentation says it does not log or store prompt or generation data for open models without an explicit opt-in, and the company says it detected no impact to its Inference, Training SDK, or Nexus products, which run with zero data retention by default. That promise is real, and it is also narrow: it covers inference traffic. The Batch API requires dataset storage, and the Notion transcripts were retained because they fed a secondary analytics feature — classification for Insights — that ran outside the default memory-only protections.

That distinction is the lesson of the incident. A vendor can truthfully say it retains nothing from the model call itself while still holding the datasets, billing records, and analytics copies that accumulate around it. Payment card numbers were not stored, Fireworks says, and were not affected.

Fireworks attributes the intrusion to a financially motivated group that sells tokens obtained through unauthorized access to AI models through illicit routing gateways — a practice known as LLMjacking. Google’s Threat Intelligence Group and Mandiant warned on November 2 that single LLMjacking incidents have produced more than $100,000 in fraudulent charges in a day, and up to $1 million cumulatively at some organizations before access was revoked. Google’s report does not name Fireworks, so the overlap is a pattern match, not attribution. Fireworks chief executive Lin Qiao has said the intruders did not appear to be hunting for customers’ models: “Most downloads were partial and stopped.”

A chain of glowing blue connected nodes with one cracked red link in the middle, representing a broken link in a software supply chain
Illustration: one cracked link in a chain of vendors — the breach reached customers two steps removed from the company that was attacked. (AI Frontier Post illustration)

What to watch#

Fireworks has brought in Palo Alto Networks’ Unit 42, notified law enforcement, and disabled self-serve dataset uploads and downloads for Batch Inference and dataset-based training while it investigates. It has warned that its work “may reveal additional information,” and The Register, citing Bloomberg, reported it is also working with customers including Cursor and Harvey to assess the impact. The Illinois and California counts for Uber drivers are still to come.

The wider pattern is worth watching too. Wiz counted at least nine AI developer platforms that disclosed incidents in October, according to VentureBeat — a month in which stolen credentials, not model weights, were the prize. For any team buying inference or model hosting, three questions now belong in vendor review: what personal identifiers actually reach the vendor and for how long; whether research and development environments are held to production standards; and whether the vendor will say what was touched, not only what it has not detected.

For drivers, the practical step is the unglamorous one: a credit freeze is free to place and lift, and unlike a license number, it can actually be rotated. For everyone else, the takeaway is simpler — when your AI feature runs on someone else’s infrastructure, your data lives wherever that vendor keeps it, including the copies you never asked about.

Sources: WebProNews, “Notion Drops Fireworks AI After an Attack on the Vendor Exposed Some Customers’ AI Chats”; TechTimes, “Uber Data Breach: Hackers Compromised AI Vendor Fireworks, Stole Drivers’ License Data”; TEISS, “Notion AI chat transcripts exposed in breach at AI vendor Fireworks AI”. Reporting draws on statements from Fireworks AI, Notion, and Uber, and on TechCrunch’s November 13 reporting of Uber’s state breach filings.