Trigger.dev says attacker stole customer environment variables

Trigger.dev, a cloud-hosted platform for building AI agents and workflows, has disclosed that an attacker gained unauthorised access to environment variables belonging to some of its customers. The company published a security incident report on Sunday 1 November 2026, saying its investigation had identified "exposure across a subset of organizations". The Register reported the disclosure on 2 November 2026.

Environment variables are the configuration values an application reads at runtime, and in software-as-a-service platforms they routinely hold API keys and other credentials. If the exposed variables contained sensitive credentials, The Register notes, an attacker could gain access to connected services and infrastructure belonging to the affected customers.

Trigger said the exploit used to obtain the access has been blocked, and that affected customers have been notified of steps they need to take to prevent further security problems. The company's report offered little further explanation. Trigger has not publicly identified which organisations were affected.

The Register said it approached Trigger, which declined to provide additional information and told the publication to wait for a full incident report.

The platform is used to build AI agents and workflows in TypeScript. Trigger describes itself as a durable execution platform, handling retries, scaling and the continuation of long-running tasks through crashes and redeployments, while providing tools to monitor what those tasks are doing. Its own marketing says customers can "build durable AI agents that survive refreshes, redeploys, and crashes", and that the platform suits "long-running tasks with retries, queues, AI observability and elastic scaling".

That design is part of what makes the exposure worth watching, according to The Register. Elastic scaling, automated retries and the ability to run many concurrent operations without timeouts could compound the consequences of compromised API keys, depending on what those credentials allow an attacker to reach. An attacker holding stolen credentials could potentially interfere with a customer's connected services or workflows.

The Register also pointed to Trigger's recent addition of webhooks, with support for services including Stripe, Supabase and Slack. That expands the range of integrations whose credentials could be affected if they were among the exposed variables.

Customers listed on Trigger's own website include the fashion brand Emporio Armani, the AI acquisitions platform GovSignals, which supports the Pentagon, and the calendar platform Cal.com. There is no indication from Trigger or The Register that any of those named customers were among the organisations affected.

One mitigating factor noted by The Register is that Trigger is open source and can be self-hosted, which it suggested may be preferable to relying on a hosted service for organisations concerned about software-as-a-service security.

Until Trigger publishes its full incident report, the number of affected organisations, the timing of the intrusion and the nature of the exploit remain undisclosed.