Spooky season is supposed to end on October 31. Somebody forgot to tell the AI developer platforms, which are still finding skeletons in their environment variables well into November.
A Sunday Disclosure Nobody Wanted
Trigger.dev, the platform developers lean on to run background jobs and AI agent workflows, disclosed on Sunday, November 1 that an attacker gained unauthorized access to environment variables for a subset of its customer organizations. The company's CTO wrote that Trigger.dev has "blocked the exploit used in this attack" and has emailed every impacted account owner with steps to mitigate.
The gaps matter as much as the details. Trigger.dev hasn't said how many organizations were affected or how the attacker got in, and no root cause has been published yet. Further updates are going to the company's status page, which is worth bookmarking if you're a customer.
Black October Gets a Bonus Episode
The timing is grim. Two days earlier, Northflank told its users to "assume all environment variables have been decrypted" and rotate every secret, after customers reported that AI API keys stored on the platform were being used by someone else. Security firm Wiz has branded the month "Black October," counting at least nine incidents at AI developer platforms, including Fireworks AI, Railway, Warp and Northflank. Wiz says no single vulnerability or dependency ties them together, and Trigger.dev's disclosure arrived after that list was published.
What links them is the loot. According to Wiz, attackers are explicitly hunting stored environment variables, and AI provider keys are the jackpot because they convert straight into expensive compute. In one case study, two stolen AWS Bedrock keys were tested within 30 minutes, then used at scale days later, likely running up more than $100,000 in usage. That's a costly way to learn your .env file was really a credit card.
The practical lesson isn't "never use a hosted platform." It's that every platform holding your secrets is part of your attack surface, and AI keys deserve the same care as payment credentials: scoped narrowly, rotated regularly, and watched through your provider's usage logs so a sudden spike gets noticed in hours, not on next month's invoice.
If you have keys parked on any of these services, rotate first and read the postmortems later. Start with the AI provider keys.
If Black October has you wondering how many third-party platforms are holding your keys right now, our free developer security checklist for supply-chain attacks is a good place to start counting.
Source: Trigger.dev