Skip to content
Security Incidents at Trigger.dev and Kernel: API Key Compromises

Security Incidents at Trigger.dev and Kernel: API Key Compromises

First seen 6 Nov 2026, 20:45 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 6, 2026 at 20:46 UTC
  • •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.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated 15d ago How this analysis works

Timeline

2026-11-01
Trigger.dev incident detected
Unauthorized access to customer root API keys was detected, affecting 0.66% of customers.
Trigger.Dev
2026-11-02
Kernel incident detected
Kernel reported unauthorized access using a compromised API key, affecting 0.28% of customers.
Kernel.Sh
2026-11-03
Kernel access to servers confirmed
The attacker accessed 4 GPU-enabled servers, with cryptomining activity confirmed on one.
Kernel.Sh

More articles in this cluster (2)

Common questions

How many customers were affected by each incident?
Trigger.dev was affected by 0.66% of its customers, while Kernel's incident impacted 0.28%.
What actions should affected customers take?
Affected customers should rotate their API keys and credentials in the impacted environments.
What was the attack vector for these incidents?
Trigger.dev's incident involved unauthorized access to API keys, while Kernel's incident stemmed from a compromised API key used to access logging data.