Skip to main content
Emerging ThreatsData Breaches

Trigger.dev Exposes Environment Variables in Security Breach

Technology office with workstations and security team responding to incident.

"exposure across a subset of organizations," Trigger.dev said in its Sunday security incident report — a short, stark admission that environment variables held by some customers were visible to an unauthorized actor.

Trigger.dev's account and immediate steps

The company said its investigation identified "exposure across a subset of organizations" and that an attacker had gained unauthorized access to environment variables belonging to those organizations. Trigger reported that whatever exploit was used to gain access has been blocked, and that affected customers have been notified of the steps they need to take to prevent further security problems. The vendor declined to provide any additional information when contacted and directed inquiries to a forthcoming full incident report.

Why environment variables are central to the risk

Trigger’s brief disclosure underscored a basic, often-underappreciated point in cloud and SaaS operations: environment variables routinely hold credentials and configuration data that grant access to other services. The Register’s coverage quoted the obvious but consequential implication — if compromised environment variables contain sensitive credentials, "an attacker could basically end up with the keys to the kingdom," potentially gaining access to connected services and digital infrastructure.

Platform features that could magnify an incident

Trigger.dev is positioned as a durable execution platform for AI agents and long-running TypeScript workflows. The company advertises features such as retries, elastic scaling, AI observability, and the ability to keep tasks running across crashes and redeployments. Those same capabilities that customers rely on for resilience can, according to the reporting, increase the potential impact of exposed credentials: elastic scaling, automated retries, and concurrent operations without timeouts could let an attacker act at speed and scale if API keys or other secrets were stolen.

New webhooks and the integration surface: Stripe, Supabase, Slack

The platform recently added webhook support for third-party services, explicitly naming Stripe, Supabase and Slack. Trigger’s move to integrate webhooks broadens the range of systems tied to its environment variables, and therefore the set of downstream services that could be implicated if those variables were exposed. The company has not released a list of which organizations were affected or which integrations — if any — were accessed by the intruder.

Named customers and the unanswered disclosure

Trigger’s public-facing site lists a mix of customers, including Emporio Armani, GovSignals and Cal.com among others. The company has not identified whether any of these named organizations were among the "subset" impacted. Trigger's refusal to provide details beyond its short advisory leaves the question of which customers were exposed unresolved until the promised full incident report is issued.

What this means for technologists, affected enterprises, and open-source operators

  • Technologists and security teams: They will be watching the full incident report for specifics about the vector and scope, and will be mindful that exposed environment variables can translate into lateral access to connected services — a point the company and the coverage explicitly highlight.
  • Affected enterprises and procurement leaders: Organizations that use Trigger.dev should confirm whether they were among the notified customers and follow the vendor’s recommended mitigation steps; Trigger has said it has notified affected customers and provided steps to prevent further security problems.
  • Open-source operators and self-hosting proponents: Trigger is open source and can be self-hosted — an option the coverage notes may appeal to users wary of relying solely on a hosted service in the wake of credential exposure.

Trigger's advisory is terse but serious: environment variables are a high-value target when they contain API keys and secrets, and the platform features that make Trigger attractive could also enlarge an attacker’s potential impact. The central concrete next step is the one the vendor itself has set — the full incident report. Until that document appears and Trigger answers follow-up questions about scope, vector and remediation specifics, customers and observers must work from the limited facts the company has disclosed: unauthorized access to environment variables occurred, the exploit has been blocked, affected customers have been notified, and Trigger will publish a fuller account.

Original story: https://www.theregister.com/security/2026/11/02/cloud-hosted-ai-workflow-tool-has-environment-variables-snatched-in-security-incident/5306998