Northflank Breach: Rotate Every Secret and AI Key Now

If you host anything on Northflank, stop reading for a second and go rotate your secrets. The cloud platform says attackers may have decrypted the environment variables its customers stored with it, and some people have already seen their AI API keys used by someone else.

What happened

Northflank, a platform developers use to deploy apps, containers, databases and AI workloads without running their own servers, posted a security incident on its status page on October 30. According to its own timeline, cloud security firm Wiz sent a threat alert at 11:43 UTC, and Northflank engineers were looking at it a minute later. Network policy patches followed through the afternoon, and the company brought in Wiz's incident response team.

By 13:58 UTC the advice had become blunt: assume every environment variable has been decrypted, and disable or rotate all keys. Later that night Northflank confirmed that users were reporting unauthorised use of AI API keys they had stored on the platform. BleepingComputer reported the abuse and flagged it on X.

Northflank hasn't said how the attackers got in or how many customers are affected. Since the incident, it has switched on secret rotation for Postgres, MongoDB, MySQL and Redis add-ons, and turned on audit logs for every account, free ones included.

Why it matters

Environment variables are where most apps keep the good stuff: database passwords, cloud credentials, payment keys and, more and more, keys for OpenAI, Anthropic and other AI providers. An AI key is basically a credit card with a meter attached. Whoever holds it can run up a bill on your account or resell the access.

This also isn't a one-off. Wiz's "Black October" report counts at least nine incidents at AI developer platforms this month, including Railway, OpenCode, Warp and Lightning AI. In one example Wiz describes, stolen credentials were used for roughly 2.5 million Amazon Bedrock calls, worth about $100,000 in usage. I wrote about the Railway breach earlier this month, and the advice there applies here almost word for word.

What to do

• Rotate every secret you've stored in Northflank: workload secrets, secret groups and global secrets. Revoke the old key with the provider that issued it first, then generate a new one and update Northflank. Changing the value in Northflank alone doesn't kill the leaked key.
• Use the new rotation option for any Postgres, MongoDB, MySQL or Redis add-ons, and turn off public access to add-ons if you'd enabled it.
• Check usage and billing dashboards at your AI providers for spikes you can't explain, and set hard spending limits if you haven't. Report anything odd to both the provider and Northflank support.
• Open the newly enabled audit logs and look for logins, deployments or secret reads you don't recognise.

If you use more than one of these AI-friendly hosting platforms, it's worth doing a quick key audit across all of them this weekend. It's a boring hour, but a lot cheaper than a surprise five-figure API bill.