# Trigger.dev says an attacker read environment variables for a subset of customer organizations

Source: https://startwithidentity.com/blog/2026-11-05-trigger-dev-says-attacker-read-environment-variables-for-a-subset-of-organizations/
Last updated: 2026-11-05
License: content by Start with Identity. Cite the source URL.

---

Trigger.dev, an open-source platform for building AI agents and background workflows in TypeScript, posted a security disclosure on its [status page](https://status.trigger.dev/incident/1110434) on November 1 saying "there has been a security incident at Trigger.dev" and that "the attacker gained unauthorized access to environment variables" for "a subset of organizations." The company said the exploit has been blocked and that it has "emailed all impacted account owners with steps to mitigate." It has not said how the attacker got in, how many organizations were affected or which variables were read. When [The Register](https://www.theregister.com/security/2026/11/02/thieves-pilfer-environment-variables-from-trigger-ai-workflow-tool/5306998) asked for more on November 2, Trigger.dev declined and said to wait for a full incident report. As of November 5 the status entry, marked resolved, promises more details but carries no follow-up.

## Why it matters

This is the fourth developer platform in three weeks to lose customer environment variables, after [Zeabur](https://startwithidentity.com/breaches/incidents/2026-zeabur-plaintext-admin-token/), [Railway](https://startwithidentity.com/blog/2026-10-22-railway-says-attacker-decrypted-environment-variables-in-up-to-100000-workspaces/) and [Northflank](https://startwithidentity.com/blog/2026-10-30-northflank-tells-customers-to-assume-environment-variables-were-decrypted/). On a workflow platform those variables are the API keys for every service a task calls, and The Register notes Trigger.dev recently added webhook support for Stripe, Supabase and Slack. Each one is a static credential that works from anywhere until it is rotated: the [static API key abuse](https://startwithidentity.com/techniques/static-api-key-abuse/) pattern.

If you run tasks on Trigger.dev's cloud service, rotate every secret stored there even if you did not get the email, because the affected subset is not public. Then check the downstream providers' logs for calls from unfamiliar addresses since late October. Longer term, move what you can to short-lived credentials through [workload identity federation](https://startwithidentity.com/glossary/workload-identity-federation/), so the platform holds nothing worth stealing. Our [secrets management guide](https://startwithidentity.com/guides/fundamentals/what-is-secrets-management/) covers [rotation](https://startwithidentity.com/glossary/secrets-rotation/).

Source: [Trigger.dev status page](https://status.trigger.dev/incident/1110434), [The Register](https://www.theregister.com/security/2026/11/02/thieves-pilfer-environment-variables-from-trigger-ai-workflow-tool/5306998)