Trigger.dev customer root API keys and environment variables compromised
- Why it's major
- The threat actor obtained customer root API keys giving full access to customer environments, including credentials stored in environment variables.
- Status
- Closed
- Disclosed
- Updated
- Data exposed
- Customer root API keys, environment variables, and run, deployment, and schedule metadata
TL;DR: Trigger.dev, a platform for durable AI agents and workflows, says a threat actor gained unauthorized access to customer environment variables. The 0.66% of customers affected must rotate environment credentials, and Trigger.dev revoked their API keys.
If you were affected
Trigger.dev revoked all exposed Trigger.dev API keys for the impacted environments and notified impacted customers by email and a dashboard banner. Trigger.dev asks impacted customers to:
- Treat the credentials in the affected environments as compromised.
- Regenerate your Trigger.dev API keys.
- Rotate database passwords, third-party API keys, and access tokens in the affected environments.
- Revoke the previous credentials with their respective providers.
What happened
On November 1, 2026, a threat actor gained unauthorized access to Trigger.dev systems and obtained customer root API keys for some customer environments. A customer root API key gives full access to an environment's settings, including its environment variables. The initial access vector has not been disclosed.
The intrusion affected 0.66% of all Trigger.dev customers, whose environment variables the threat actor accessed. In some customer environments, the threat actor listed recent runs, deployments, and schedules, accessing run IDs, task names, idempotency keys, run tags, deployment metadata, and run metadata. Trigger.dev says it found no evidence the threat actor accessed other customer data, production databases, or dashboard accounts, and that self-hosted deployments were not affected.
Trigger.dev detected the intrusion through infrastructure alerts on November 1, 2026, then blocked the threat actor and mitigated the attack vector. Trigger.dev revoked all affected customers' Trigger.dev API keys, rotated its own internal credentials and secrets, and reviewed API access logs across all customer environments. Trigger.dev notified affected customers by email and dashboard banner, engaged cybersecurity incident response experts, notified law enforcement, and released IP whitelisting for scoped API keys and OIDC support.
Timeline
-
N/AImpacted customers notified by a second email
-
N/AReported by Trigger.dev on X
API incident status changed to resolved
N/AImpacted customers notified by email
N/AThreat actor blocked and attack vector mitigated
N/AInfrastructure alerts detected anomalous activity by the threat actor
Independent analysis you can act on, straight to your inbox.
Thanks. is on the list.
Sources
- Security Disclosure: Sunday...status.trigger.dev, accessed Nov 1, 2026
- Security Disclosure: Sunday November 1sttrigger.dev, accessed Nov 1, 2026
- Trigger.dev on Xx.com, Nov 1, 2026
- Trigger.dev on Xx.com, Nov 6, 2026, 12:33 UTC
- Security incident report: Sunday November 1sttrigger.dev, accessed Nov 6, 2026