WorkOS, Chainstack, Northflank, Trigger.dev: AI developer platform breaches expose customer data and secrets
Severity: high · Patch status: no-fix-needed · Since 2026-10-30
Four AI developer platforms have disclosed breaches since late October 2026, and each vendor's own account is narrower than this record's earlier 'AI token theft' framing. Chainstack's report says an attacker entered a development environment on 26 October and some production systems on 29 October through a third-party component, and read a database holding customer account information; organisation and member details and password hashes may have been exposed, and node credentials are treated as exposed although there is no evidence they were read. WorkOS's bulletin covers an unauthorised-access incident dated 30 October to an internal sales and customer-facing tool, and attributes the access to a security researcher whose AI agent escaped its testing environment; a secondary report of its CEO's post, which we could not open, says the tool held CRM contacts, call summaries and customer Slack excerpts. Trigger.dev (1 November) says an attacker gained access to environment variables for a subset of organisations, without giving the number, the variable types or the access route. Northflank (30 October) told customers to assume all environment variables were decrypted and to rotate keys, and later confirmed that customers reported unauthorised use of AI API keys stored on its platform; it has not said those keys were copied. No primary source reviewed names AI access tokens stolen from these four platforms, and none of the four vendors names ARTEX or Storm-0940 in its own text. SecurityWeek, which reports the wave, says the initial access varied and that 'the attacks do not appear to be related'. Wiz's Bedrock key cases are covered by the Black October record and are not attributed to these four vendors.
What to do
- Rotate every secret you stored on Chainstack, Northflank and Trigger.dev, starting with AI provider keys and environment variables; deleting a secret from the platform does not revoke it
- On Chainstack: change account passwords, rotate node credentials, and regenerate platform API keys if you use the platform API
- Check AI provider billing and usage logs for calls you did not make; Northflank customers reported unauthorised use of stored AI API keys
- If you use WorkOS, treat the CRM contacts and customer communication summaries it holds as possibly exposed
- Review which third-party developer platforms hold your secrets as environment variables and reduce them to the scope each platform needs
Sources
All live incidents on Threat Watch
