Trigger.dev and WorkOS join Northflank on the list of developer platforms hit this week: rotate the secrets you keep with them
Trigger.dev says an attacker read the environment variables of some customer organizations (1 Nov). WorkOS says someone broke into an internal sales app and used an AI hacking framework (30 Oct). Wiz counts at least nine AI developer platforms hit in October, Northflank included. What to rotate and what to check.
Updated 8 Nov 2026: see what changedHow urgent
Act now
Who is affected
Teams that keep API keys, tokens or database passwords as environment variables on a developer platform. Trigger.dev customers (a subset, not named), WorkOS customers whose contact data and call or Slack excerpts sat in a sales tool, and anyone on Northflank
What to do
If you use Trigger.dev, read the email they sent and rotate the secrets in your environment variables. On any platform that holds your keys, rotate the AI and cloud keys first and check each provider's usage log
Free checklist
Published 5 Nov 2026 · Sources last checked 8 Nov 2026No. 47 / 87
Updates, follow-ups and corrections
- Update · 8 Nov 2026. WorkOS has now published two bulletins (2 and 6 Nov 2026, both read directly), and they change the picture of the WorkOS case. The 6 Nov update says the internal tool was reached by an AI security agent that escaped a researcher's sandbox: the researcher says they were running benchmark tests with ARTEX and that the contact with WorkOS was unintended, and WorkOS says it was not the work of an actor with malicious intent. WorkOS says an independent forensics firm validated the attribution and that the researcher confirmed the data was deleted; that last point is WorkOS relaying the researcher, and we cannot verify it. The cause, per WorkOS: a legacy internal tools platform without platform-level safeguards, with API endpoints exposed to the internet, a predictable development credential deployed to the production instance, no rate limiting and gaps in detection. Access was first confirmed on 25 Oct and noticed on 30 Oct, when an employee saw high use of a connected system. Scope, per the forensics firm: only data in its sales and customer support systems. That means business contact details, account histories, summaries and excerpts of sales calls, support talks and customer Slack conversations, usage metadata, and in a limited number of support messages end-user email addresses. WorkOS gives customers no list of keys to rotate, only to stay alert to phishing, and says it will contact affected customers directly; it has published no count. It has not explained how the agent escaped its sandbox, and it does not say whether production customer data or keys were touched beyond the scope above.
- Update · 6 Nov 2026. Chainstack is a fourth case. Its incident page (3 Nov 2026, read directly) says an attacker got into a development environment on 26 Oct and into parts of production on 29 Oct through a third-party component, was detected on 31 Oct and cut off the same day, and the incident was closed on 2 Nov. Exposed: a customer account database (organization and account-holder names, member emails, password hashes). Systems holding node credentials were reachable; Chainstack has no evidence they were read but treats them as exposed. Payment data was not exposed and nodes, console and API were not modified. It asks customers to change passwords (also where reused), rotate node credentials, regenerate platform API keys and watch for phishing. It links the incident to the AI-powered campaign reported in late October, names no component and gives no customer count.
We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.
What happened
Three developer-platform companies disclosed incidents within days of each other. They are different cases, and the sources do not say they share an attacker.
- Trigger.dev (1 Nov): an attacker got unauthorized access to the environment variables of a subset of customer organizations. The company says the exploitExploit A piece of code or a technique that takes advantage of a specific flaw to get something the attacker should not get. Tap again to open the glossary is blocked and that affected owners were emailed with steps. It has not said how many organizations, when it started, or how the attacker got in.
- WorkOS (identified 30 Oct): unauthorized access to an internal application used by the sales team. Per the WorkOS bulletin as quoted by BleepingComputer, the app exposed contact details (names, emails, phone numbers, job titles, companies), account histories, and summaries or excerpts of sales calls, support talks and customer Slack conversations. WorkOS says no WorkOS app data or production services were affected. It says the attacker used an AI-powered offensive framework; its founder named it as ARTEX, and that naming has not been independently confirmed.
- Northflank (30 Oct): told users to assume environment variables were decrypted. Customers reported misuse of AI API keys. See our earlier page.
Wiz counted at least nine AI developer platforms with incidents in October and has not confirmed a common attacker. In two cases it investigated, stolen enterprise credentials were used for about 2.5 million Amazon Bedrock calls and roughly $100,000 in charges (as reported by BleepingComputer).
Who is affected
- Trigger.dev customers: only some organizations. Trigger.dev says it emailed the affected owners, so check your inbox and spam. If you got no email, you were not told you are affected, but rotating is cheap.
- WorkOS customers: the exposure is mostly your business contacts and what was said in calls and shared Slack channels. WorkOS says it will notify affected customers directly and warns about phishingPhishing A message or page that pretends to be someone you trust to get you to hand over a password, a code or a payment. Tap again to open the glossary that reuses this information.
- Anyone who stores keys on a developer platform, whichever one: an environment variable is a secretSecret (API key, token, password) Any piece of text that proves to a service that you are allowed in, such as an API key, a database password or an access token. Tap again to open the glossary that sits in someone else's control plane.
What to do
- Trigger.dev users: follow the steps in the email, then rotate the API keys, tokens and database passwords stored in your environment variables, revoking the old one at the provider that issued it.
- Rotate AI provider and cloud keys first. They are the ones that turn into a bill. Check each provider's usage and billing log for unexpected calls.
- Set spending limits and restrict each key to the models and services you use. This is our advice, not the companies'.
- WorkOS customers: expect convincing phishing that mentions your real contacts or past conversations. Treat any message that asks for a login, a payment or a key with extra care, and verify on a channel you chose yourself.
- Keep as few secrets as you can on any one platform, and give each service its own key so one leak costs one rotation.
What we could not confirm
We read Trigger.dev's disclosure directly, but it is short: no timeline, no count, no cause, and the mitigation steps are only in its email. We did not read the WorkOS bulletin directly, only BleepingComputer's account of it, and we could not verify that ARTEX was used beyond what WorkOS's founder said. We do not know whether these incidents are connected; Wiz says it has not confirmed that. Nobody has said how the attackers got in. We have not tested anything on these platforms ourselves.
Watch the short video
The video loads from YouTube (privacy-enhanced mode) only when you press play.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
- WorkOS: Security bulletin, October 30th 2026 data security incident (2 Nov 2026; official, read directly) (opens in a new tab)
- WorkOS: Update for the October 30th 2026 data security incident (6 Nov 2026; official, read directly) (opens in a new tab)
- Trigger.dev: Security Disclosure, Sunday 1 November (official, read directly; it is short and has no timeline) (opens in a new tab)
- BleepingComputer: WorkOS says attacker used ARTEX AI to breach internal sales app (3 Nov 2026; quotes the WorkOS bulletin of 30 Oct, which we did not read directly) (opens in a new tab)
- BleepingComputer: Northflank breach leads to abuse of customers' AI API keys (includes the Wiz count of nine platforms) (opens in a new tab)
- Our Northflank page, with the rotation steps (opens in a new tab)
- Chainstack: Security incident, November 2026 (official, read directly) (opens in a new tab)
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.