---
title: "Fireworks AI pauses its Batch API as Uber notifies 149,346 people"
description: "The November 17 bulletin splits October into two intrusion chains, one dating to August, and retires the product line built on storing customer data. Investors marking inference providers up on this week's praise for Fireworks' response are pricing the wrong document."
publisher: "The Inference"
section: "Security"
published: 2026-11-19T17:31:15.117Z
modified: 2026-11-19T17:31:15.117Z
canonical: https://theinference.org/article/fireworks-ai-pauses-its-batch-api-as-uber-notifies-149-346-people-whose-data-was-taken-in-the-breach
language: en
keywords: "Fireworks AI, Data Breach, Security, Uber, AI Infrastructure"
---

# Fireworks AI pauses its Batch API as Uber notifies 149,346 people

> The November 17 bulletin splits October into two intrusion chains, one dating to August, and retires the product line built on storing customer data. Investors marking inference providers up on this week's praise for Fireworks' response are pricing the wrong document.

[Fireworks'](https://theinference.org/markets/companies/fireworks-ai) bulletin of November 17, 2026, is being read as the end of a security story [1][2]. It is just as much a business document. The same pages that declare both October intrusion chains contained and remediated widen the confirmed scope to account and billing records for every account opened before October 30, and the product line whose job is storing customer data, the Batch API, is now paused with its stored inputs and outputs marked for permanent deletion [1][2].

## One breach is now two, and one letter cannot close both

The first chain runs from August 3 to October 7: an intruder combined stolen internal credentials with a vulnerability in one of Fireworks' own services to reach secrets, model files and datasets for a small number of customers, and Unit 42 has finished that forensics [1]. The second began on October 23 at a third-party cloud provider hosting Fireworks' development machines and reached part of production; a second firm, AprosSyber, is still investigating [1]. Closure evidence now has to name the chain, because every secret Fireworks ever held stays live at the provider that issued it: deleting it from Fireworks revokes nothing [3].

## What survived is what was never stored

Fireworks found no impact to Inference, Training SDK or Nexus, the products that keep nothing at rest, and [its own documentation](https://docs.fireworks.ai/accounts/zero-data-retention) names the exceptions: stored responses, batch jobs and training are the features that hold customer content [1][4]. The response concedes the pattern. Batch, the bulk product sold at half the serverless token price, is paused, dataset uploads are retired platform-wide, and the stored data is being deleted [2]. Customers moved first. [Notion](https://theinference.org/markets/companies/notion), which held a contractual zero-data-retention commitment from Fireworks, learned its data had been retained anyway and disconnected on November 3 [5]. Cursor moved all inference traffic off the platform [6].

Zero data retention was the only control that held.

## Uber has paid the first invoice

[Uber](https://theinference.org/markets/companies/uber)'s [filings](https://www.bleepingcomputer.com/news/security/uber-notifies-drivers-of-data-breach-affecting-nearly-150-000-people/) put the damage at 149,346 people notified, with names, addresses, birth dates and license numbers taken [7]. None of Uber's cloud alerting fired, because the credentials used were valid and the data flows permitted, so the missing control is behavioral detection [8]. A license number does not rotate, which means the fraud exposure outlives every credential change, and Uber has disclosed no cost [7][8]. A private vendor's breach lands its first measurable invoice on a listed customer.

## The praise prices the wrong week

Today a sponsored essay crowns Fireworks the industry's model of incident response [9]. The praise prices the first week of October; [the bulletin prices everything since](https://fireworks.ai/security-bulletins): [a second chain still under investigation](https://theinference.org/article/harvey-told-of-a-second-more-serious-fireworks-hack-has-yet-to-say-whether-law-firm-data-was-exposed), a retired product line, two named customers gone.

Wiz traced two keys stolen in this wave to [more than $100,000 of list-price inference](https://theinference.org/article/a-950-botnet-burns-your-ai-credits-while-your-site-stays-up), and Zeabur, another platform hit in the same campaign, is ending service by the end of the year [10][3]. This is not a case against AI infrastructure; it is the market pricing storage.

## Back the builders that keep nothing

Whatever terms Fireworks secures for [the round it has been shopping](https://theinference.org/article/fireworks-ai-wants-40-billion-for-tokens-nobody-can-publicly-count), this bulletin is now in the diligence [3]. Mark private inference names on their retention architecture, and back the builders making keep-nothing the default: short-lived credentials, hard spend caps, and alarms that fire when a valid credential starts bulk-reading a secret store [3].

## Takeaway

The November 17 bulletin is a business document as much as a breach notice: it widens confirmed scope to every account opened before October 30 and pauses the Batch API, the one product built on storing customer data. Uber's 149,346 notified drivers show the first invoice landing on a listed customer, and zero data retention was the only control that held.

## Sources

1. [Fireworks AI, Update on October 2026 security incidents, security bulletins, 17 November 2026](https://fireworks.ai/security-bulletins)
2. [Fireworks AI documentation, Batch API, accessed 19 November 2026](https://docs.fireworks.ai/guides/batch-inference)
3. [Cloud Security Alliance, Black October: AI Developer Platform Breaches and Industrialized LLMjacking, 4 November 2026](https://labs.cloudsecurityalliance.org/research/csa-research-note-black-october-ai-dev-platform-breaches-202/)
4. [Fireworks AI documentation, Zero Data Retention policy, accessed 19 November 2026](https://docs.fireworks.ai/accounts/zero-data-retention)
5. [Notion, Notice about the Fireworks AI incident that may impact some Notion workspaces](https://www.notion.com/help/security-incident-involving-a-third-party-ai-vendor)
6. [Cursor, An update on our recent security incident, 13 November 2026](https://cursor.com/blog/security-incident-update)
7. [BleepingComputer, Uber notifies drivers of data breach affecting nearly 150,000 people, 17 November 2026](https://www.bleepingcomputer.com/news/security/uber-notifies-drivers-of-data-breach-affecting-nearly-150-000-people/)
8. [Security.io, Fireworks separates two incidents as Uber scope reaches 149,346 drivers, 18 November 2026](https://www.security.io/articles/2026/11/18/fireworks-uber-driver-data-breach)
9. [MarkTechPost, Not If, But How: Responding to Security Incidents in the Age of AI Attackers, 19 November 2026 (sponsored)](https://www.marktechpost.com/2026/11/19/ai-security-incident-response-playbook-2026/)
10. [Wiz Research, Black October for AI Developer Platforms, 30 October 2026, updated through November](https://www.wiz.io/blog/black-october-for-ai-developer-platforms)


---

Fireworks AI pauses its Batch API as Uber notifies 149,346 people — The Inference. Canonical: https://theinference.org/article/fireworks-ai-pauses-its-batch-api-as-uber-notifies-149-346-people-whose-data-was-taken-in-the-breach
