The Fireworks AI Breach Hit Uber, Notion, and Cursor Through One Shared Cloud
A security incident at AI infrastructure provider Fireworks AI exposed customer data belonging to Uber, Notion, and Cursor. The attack shows how one shared cloud account can become a master key to a dozen companies.

One provider, three victims, and a poisoned marketplace
A cyberattack at AI infrastructure provider Fireworks AI has exposed customer data belonging to Uber, Notion, and Cursor, and the details are a textbook case of how supply chain breaches actually work. Fireworks AI confirmed that a third-party cloud provider hosting its research and development machines experienced a security incident on October 23. The attackers got into that environment, and from there they reached the data of Fireworks AI's customers. One breach, three household names, and none of the three was the original target.
The Cursor incident is the most instructive part. According to reports this week, the attackers used an access key stored at Fireworks AI to copy data from a shared storage bucket, then used credentials found inside that bucket to reach more of Cursor's systems. On October 29, they placed malicious copies of the Claude Code extension on the cache serving Cursor's marketplace. Anyone who installed or updated that extension from the poisoned cache could have received a tampered version. Cursor has confirmed the intrusion and the marketplace tampering, and the incident is now part of the official record of the week.
How the Fireworks AI breach unfolded
The chain of failures is worth walking through slowly, because every link in it is a mistake a lot of companies are still making. First, a cloud provider hosting research machines had a security incident. Research environments are often treated as lower priority than production, with looser access controls and older credentials lying around. Attackers know this, and they aim for it.
Second, an access key for a shared storage bucket was stored in that environment. Shared buckets are convenient right up until they are not: one key can open data belonging to many customers, and the blast radius of a single stolen credential is the whole bucket. Third, the bucket contained more credentials, which the attackers used to move deeper into Cursor's systems. Each step was a small, ordinary failure. Together, they handed attackers the keys to a marketplace used by millions of developers.
The marketplace tampering is the part that should worry the industry most. A compromised extension marketplace turns a trusted update channel into a delivery mechanism for malware. Developers install extensions without thinking twice, and a coding extension runs with deep access to your files, your terminal, and your credentials. Cursor caught the tampering and disclosed it, but the incident is a reminder that the software supply chain now includes the places developers get their tools, not just the code they write.
This was not the only breach this week
The Fireworks AI incident landed in a crowded week for breaches. Shipping giant Maersk confirmed data theft after the WhiteArmor ransomware group demanded $5 million and claimed about 100GB of data from a logistics platform. An active campaign is targeting cloud-hosted ConnectWise ScreenConnect environments, with attackers abusing the remote support tool to install unauthorised remote access clients and deploy a worm called SCKit. A misconfiguration at Baltic telecom provider CSCTelecom exposed more than 125 million SMS messages from European banks, airlines, and healthcare providers. The University of Texas at Arlington confirmed a ransomware attack by the Qilin gang that stole personal information in October.
The pattern across all of them is the same one we keep writing about: the breach rarely starts at the company in the headline. It starts at a vendor, a legacy system inherited through an acquisition, a misconfigured database, or a research environment nobody was watching. The Optimizely breach earlier this month hit 178 companies including Zoom and Salesforce through a single vendor. The Infoblox breach started with a supplier, not a hacker at the front door. Fireworks AI is the latest entry in a list that gets longer every week.
What to do about it
If you use Cursor, update your extensions from a clean source and check whether anything you installed around October 29 looks wrong. If you use Uber or Notion, watch for phishing that uses details only a data breach could provide, and make sure your passwords are unique, because credential stuffing is the usual next step after a breach like this.
If you run a company, the lessons are structural. Audit what your vendors can access, and assume any credential stored in a research or staging environment will eventually leak. Scope cloud access keys as narrowly as you can, rotate them, and never let one key open a shared bucket full of other people's data. Segment your marketplaces and extension caches from your research infrastructure. And when a vendor tells you about an incident, treat it as your incident too, because your customers will.
The uncomfortable truth is that Fireworks AI did the right thing by disclosing, and the breach still happened. Disclosure is damage control, not prevention. Prevention is the boring work of access control, key hygiene, and assuming your vendors will be breached. Do that work now, while it is a checklist, and not later, while it is an incident report.


