Wiz links a run of AI developer platform breaches to stolen keys
Wiz says nine AI developer platforms had security incidents in October, with attackers hunting stored environment variables and the AI provider keys inside them.
On 30 October 2026, researchers at Wiz published "Black October", an account of a run of security incidents at AI developer platforms that month. Wiz lists Fireworks AI, Andromeda, Zeabur, Lightning AI, OpenCode, Railway, Warp, CommandCode and Northflank.
Wiz says no single flaw connects them, and the reported causes differ. What they share, it says, is a targeted hunt for environment variables stored on these platforms, especially ones that hold AI provider keys. Stolen keys are then used for LLMjacking, where someone else's account pays for AI usage.
Wiz says stolen keys were tested within 30 minutes of access. In one case it saw about 800,000 Amazon Bedrock calls over some 30 hours. In another, about 1.7 million calls in 13 hours after a key appeared in a reseller pool. It estimates that these two cases alone likely ran past $100,000 at list price. Wiz links two resale operations to the stolen keys, but says it cannot firmly tie either to the original break-ins.
Zeabur's own preliminary report shows the scale at one company. It confirms that an attacker read 3,218,965 service environment variable records and profile data for 321,810 accounts. Zeabur says long-lived admin credentials had been stored in plain text in a private configuration repository, and it told all users to replace every credential held in their environment variables.
Why it matters
Environment variables are often treated as the safe place for keys, and for code they are safer than a hardcoded value. But a hosting platform has to be able to read them, so they gather many customers' secrets in one spot.
AI keys also turn into money quickly. Unlike a stolen password, a working key can be resold and used at once, and the bill lands on its owner.
What you can do
- List every platform that holds your AI keys, including any you tried once and forgot.
- If you use a named platform, read its notice and follow it. Assume stored variables are exposed if it says so.
- Replace affected keys at the provider, then redeploy. Do not stop at changing the value on the platform.
- Set spending limits and alerts with each AI provider.
- Use a separate key per project, with the narrowest scope that works, so one loss stays small.
- Check usage and billing from the start of October for calls you do not recognise.
Prycheck can show plain text keys on your own computer, though it cannot see secrets stored on a hosting platform.
Sources
- Wiz: Black October for AI developer platforms
- Zeabur: October 2026 security incident
- Helix: Black October incident overview
Source: Wiz