Trigger.dev is the 11th AI dev platform on Wiz's breach list

Trigger.dev, a hosted platform developers use to build AI agents and background workflows in TypeScript, said on Sunday, November 1, that an attacker got into the environment variables of "a subset of organizations" on its service. CTO Eric Allam wrote that the company has blocked the exploit and emailed the owners of every affected account with steps to take. The status page marked the incident resolved at 10:50pm UTC and lists the API as the affected service. Trigger.dev has not said how the attacker got in, which variables were read or how many customers are affected. A spokesperson pointed The Register to a full incident report that is still to come.

Why it matters to IT buyers

Environment variables on a platform like this usually hold the keys a workload runs on: model API keys, payment and email service keys, database passwords. The Register noted that Trigger.dev recently added webhook support for Stripe, Supabase and Slack, so the keys for those services may sit there too. The Register notes Trigger.dev lists Emporio Armani, GovSignals and Cal.com as customers but has not named any affected one. Mallory's breach summary says no misuse of stolen keys has been publicly confirmed yet.

The list now has 11 names

Wiz researchers Benjamin Read and Rami McCarthy published their "Black October" report on October 30, listing nine AI developer platforms that disclosed breaches that month. Our Northflank story covered it. Wiz has since added two names to the list as publicly reported: Nvidia's Brev, with an incident dated October 4 to 20, and Trigger.dev on November 1. Wiz says neither has shared attacker techniques or indicators. The full list is now Fireworks AI, Andromeda, Zeabur, Lightning AI, OpenCode, Railway, Warp, CommandCode, Northflank, Brev and Trigger.dev.

The October cases show why speed matters. In two enterprise cases Wiz followed from those earlier breaches, not from Trigger.dev, the first test call with a stolen Bedrock key came within 30 minutes of the credential access at the vendor. Wiz puts the cost of the two cases at likely more than $100,000 at list price.

The October advisories self-hosters should not miss

Trigger.dev is open source and can be self-hosted. On October 21 three advisories were published for it:

• CVE-2026-114069 (CVSS 8.6 under version 4.0): in versions before 4.6.0, the envvars API endpoint hands back the root key, TRIGGER_SECRET_KEY, of the staging, production and preview environments. A key limited to read:envvars can use it to read plaintext secrets, start tasks and mint admin JWTs.
• CVE-2026-114068 (CVSS 3.1 score 8.3): before 4.6.0, a missing check on the waitpoint token endpoint lets an authenticated attacker block runs that belong to other organizations.
• CVE-2026-114073 (CVSS 3.1 score 5.5): the CLI before 4.5.9 writes resolved environment variable values into debug deployment logs, so CI logs and support bundles can leak credentials.

byteiota ties the first of these to the November 1 attack. Trigger.dev has not named a flaw, and the CVE records do not mention the incident, so treat that link as unconfirmed. Either way, a self-hosted instance below 4.6.0 is exposed to it. The latest release, v4.7.7 from October 22, also moves task runtimes to patched Node.js builds that fix the Brotli flaw CVE-2026-111497, but existing deployments keep the old runtime until they are redeployed.

What IT teams should do

1. Find every Trigger.dev account and self-hosted instance in use.
2. Read the email Trigger.dev sent to account owners. If you did not get one, byteiota's advice is the safer default: assume you were affected and rotate.
3. Revoke and reissue each secret stored there at the service that issued it. Deleting a variable from the dashboard does not kill the key.
4. Check usage and billing for each AI provider and payment service from November 1 onward, and search Bedrock CloudTrail logs as our Northflank story describes.
5. On self-hosted instances, upgrade to 4.6.0 or later (v4.7.7 is current), upgrade the CLI to 4.5.9 or later, redeploy tasks, then rotate the root key and any secret that appeared in debug logs.
6. Ask Trigger.dev for its full incident report, and give each outside platform its own narrowly scoped keys.

Railway and GhostAction customers can follow our earlier rotation guides.

Sources: Trigger.dev disclosure, Trigger.dev status page, The Register, Runtime Wire, Mallory, byteiota, Wiz, OpenCVE on CVE-2026-114069, Strix on CVE-2026-114068, Strix on CVE-2026-114073, Trigger.dev v4.7.7 release.