Fireworks AI Breach Exposes Uber, Notion and Cursor Data, Showing How One Vendor Can Compromise Many
Uber, Notion and Cursor have each confirmed that data was stolen after a hack of Fireworks AI, a company that lets developers access and run open-weight AI models. TechCrunch reported the news on Monday (Nov. 16), and Fireworks confirmed it found unauthorised access to some of its systems that affected customer data.
Fireworks said the chain of events began on October 23, when a third-party cloud provider hosting its research and development machines suffered a security incident. On October 24, an unauthorised party used that access to reach Fireworks development machines and run an unauthorised workload, which led to further customer data impact. Fireworks said it detected the activity the same day and moved to remediate and close known critical vulnerabilities. The exposed data included resource metadata, billing information (not including payment card numbers), and model weights and datasets.
The downstream effects varied. Uber is notifying nearly 150,000 drivers that their name, address, date of birth and driver's licence number were stolen from a vendor that had access to some Uber data. Cursor said an attacker obtained an access key it had issued to Fireworks, then used a stolen credential from the exposed data to publish a malicious extension. Cursor notified customers on October 30 and blocked the last attacker activity on November 1. Notion said less than 1% of its workspaces were affected and that it has contacted those customers.
The incident fits a wider pattern. PYMNTS cited Verizon research finding that 30% of data breaches in the year to October 31, 2024 involved a third party such as a supplier, hosting partner or outsourced IT provider.
Why it matters
The Cursor case shows that a credential issued to a vendor can become the attacker's route back into the customer, so trust in a supplier's environment is only as strong as its weakest hosting layer. Businesses that share personal data or access keys with AI and developer tool providers are exposed, as the Uber driver data shows. This forces a decision on what vendors actually need to hold, and how quickly shared keys can be revoked and rotated.
What to do
- Inventory the access keys and API credentials you have issued to vendors and rotate any that are no longer needed.
- Review which personal data, such as driver's licence details, each third-party provider holds and remove what is unnecessary.
- Check developer tools and extensions for unexpected or newly published add-ons that could be malicious.
- Ask vendors how they would notify you of an incident at their own hosting providers.