Trigger.Dev Security Incidents at Trigger.dev and Kernel: API Key Compromises
Article Content
- •Trigger.dev experienced unauthorized access to customer API keys, affecting 0.66% of customers.
- •Kernel's incident involved a compromised API key leading to unauthorized access to logging data.
- •Both companies have engaged cybersecurity experts and notified affected customers with remediation guidance.
On November 1, 2026, Trigger.dev reported a security incident involving unauthorized access to customer root API keys, affecting 0.66% of customers. The attacker accessed environment variables and listed recent runs and deployments, but no other customer data was compromised. Trigger.dev engaged cybersecurity experts and law enforcement, notifying affected customers and recommending credential rotations. Separately, Kernel reported a data security incident on November 2, 2026, where a compromised API key was used to access a logging provider, exposing a small number of API keys and third-party secrets. Kernel's breach impacted 0.28% of its customers, and the attacker was linked to a cryptomining campaign. Both companies have taken steps to mitigate the incidents and communicated with affected customers.
Ask AI about this cluster
Answers cite the sources they use
Timeline
More articles in this cluster (2)
Common questions
How many customers were affected by each incident?
What actions should affected customers take?
What was the attack vector for these incidents?
Continue Reading
Lazarus Group Targets 30 South Korean Servers Using PHP Vulnerabilities North Korea-linked Lazarus Group has targeted 30 servers in South Korea as part of a larger cyber operation involving 581 servers across 10 countries. The attacks exploit two critical remote code execution vulnerabilities in PHP (CVE-2026-109618 and CVE-2026-109619), allowing unauthorized server command execution. The…