In short
- Trigger.dev, a platform for building AI agents and workflows in TypeScript, disclosed a breach on 1 Nov 2026: an attacker read environment variables of some organisations.
- The company blocked the exploit and emailed affected account owners; a full report is promised later.
In short: Trigger.dev, a platform developers use to build AI agents and long-running background jobs, has confirmed a breach. An attacker read the environment variables of some organisations, which is usually where keys to payments, databases and AI models live.
What is known
- The company posted the incident on its status page as “Security Disclosure: Sunday November 1st”, marked resolved on 1 Nov 2026 at 22:50 UTC.
- It affected part of the API service and “a subset of organizations”. The company did not say how many customers or which variables were involved.
- Trigger.dev says it blocked the exploit and emailed owners of affected accounts with mitigation steps. A full report is promised later, with no date.
- According to The Register, the company declined further detail until that report. The platform recently added webhook support for services such as Stripe, Supabase and Slack, so many customers have a long list of connected services.
What I would do right now
This is my own opinion, not the vendor’s advice:
- check the account owner’s inbox (spam included) for a message from Trigger.dev,
- do key rotation for every secret stored on the platform, starting with payments and databases,
- review logs of connected services since 1 November for unusual sign-ins and spending,
- set spending caps wherever possible, especially on AI services.
How to read this
So far there is only the company’s short notice and The Register’s report, so I do not know how the attacker got in. Trigger.dev is open source and can run on your own server, but that does not protect you from mistakes in your own setup. I write more about protecting keys in AI projects in the AI code security hub, and about automations in the n8n automation hub.