Trigger.dev: attacker accessed environment variables and root API keys for 0.66% of customers · updates

Trigger.dev: attacker accessed environment variables and root API keys for 0.66% of customers: Hacker News threads the Nov 6 security incident report.

Sat, 07 Nov 2026 00:00:00 GMT

Source

Trigger.dev: attacker accessed environment variables and root API keys for 0.66% of customers: Trigger.dev publishes the full incident report (0.66% of customers, root API keys, run/deployment/schedule listing, no evidence of broader data access), and marks the status-page disclosure Resolved at 12:27 UTC.

Fri, 06 Nov 2026 00:00:00 GMT

Source

Trigger.dev: attacker accessed environment variables and root API keys for 0.66% of customers: ~20:27 UTC: Trigger.dev sends a second email to impacted customers with environment details and credential-rotation guidance.

Mon, 02 Nov 2026 00:00:00 GMT

Source

Trigger.dev: attacker accessed environment variables and root API keys for 0.66% of customers: Trigger.dev receives infrastructure alerts for anomalous activity, identifies it as malicious, blocks the attacker and mitigates the attack vector; attacker had obtained customer root API keys and accessed environment variables for a subset of organizations.

Sun, 01 Nov 2026 00:00:00 GMT

Source

Trigger.dev: attacker accessed environment variables and root API keys for 0.66% of customers: ~21:36 UTC: Trigger.dev emails impacted account owners and posts a short security disclosure; CTO Eric Allam says the exploit is blocked and environment variables were exposed for a subset of organizations.

Sun, 01 Nov 2026 00:00:00 GMT

Source

Trigger.dev: attacker accessed environment variables and root API keys for 0.66% of customers: @triggerdotdev posts that there has been a security incident, impacted account owners were emailed, and more information will follow.

Sun, 01 Nov 2026 00:00:00 GMT

Source