Northflank says to assume all environment variables were decrypted: rotate every secret, AI keys first
Northflank reported a security incident on 30 Oct 2026 and told users to assume their environment variables were decrypted and to rotate all keys. Users report that AI API keys stored on the platform were already used. On 2 Nov Northflank said the attack was contained. Here is what to rotate and what to check.
Updated 8 Nov 2026: see what changedHow urgent
Act now
Who is affected
Anyone who stores API keys, database passwords or other secrets on Northflank (environment variables, secret groups, global secrets, addons). Whether bring-your-own-cloud (BYOC) clusters were affected is not clear from the status page
What to do
Rotate every secret stored in Northflank now, starting with AI provider keys, cloud credentials and payment keys, then check each provider's usage and billing logs
Free checklist
Published 2 Nov 2026 · Sources last checked 8 Nov 2026No. 35 / 87
Updates, follow-ups and corrections
- Update · 8 Nov 2026. Northflank's status page now has a 6 Nov update (read directly). It says the first known decryption of secrets happened between 02:39 and 03:08 UTC on 30 October, about nine hours before the first security alert at 11:43 UTC. It repeats that it found no evidence that customer workloads or workload data were accessed, and says customers on forward-deployed or dedicated control planes are unaffected (it does not say whether that covers every bring-your-own-cloud setup). It says multiple users confirm that their AI keys were used. Its advice now also includes reviewing provider logs for unusual activity and turning on IP restrictions and budget limits wherever available, on top of rotating all integration and project secrets. It still has not published a root cause or a count of affected customers; it says it will share confirmed findings and a root cause analysis once available.
We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.
What happened
On 30 October 2026 Northflank, a cloud platform for deploying apps and databases, posted a security incident on its status page. According to that page, a threat alert arrived at 11:43 UTC, engineers deployed patchesPatch (security update) A fix released by the maker of a piece of software to close a flaw or a bug. Tap again to open the glossary within the hour, and at 13:58 UTC Northflank told users to "assume all environment variables have been decrypted" and to disable and rotate all keys.
At 23:38 UTC the same day, the page says users reported unauthorized use of AI API keys stored on the platform. Northflank enabled audit logs for all customers, including free users, and added one-click secretSecret (API key, token, password) Any piece of text that proves to a service that you are allowed in, such as an API key, a database password or an access token. Tap again to open the glossary rotation for Postgres, MongoDB, MySQL, Redis, MinIO and RabbitMQ addons.
On 2 November Northflank posted that the attack was contained within an hour of the first alert and that it saw no sign the attacker stayed in the environment. It said running workloads were unaffected, that the attack focused on secrets in the control plane, that independent forensic auditors are reviewing it, and that CVE-2026-98432 was patched across the fleet, BYOC clusters included. A root cause analysis will follow once findings are confirmed.
Who is affected
- Anyone with secrets on Northflank: environment variables in workloads, secret groups and global secrets. Northflank's guidance is to treat them all as exposed, even if you see no misuse.
- BYOC users: the status page does not say whether you are affected. Ask Northflank, and rotate while you wait.
- Northflank also revoked access tokens, sessions, VCS integrations, and cross-account IAM roles and service accounts where it could act on your behalf. You will need to sign in again and reconnect.
What to do
- Rotate every secret stored in Northflank now, even without suspicious activity. Northflank's order: AI provider keys, cloud credentials, payment keys, private keys, then database and service credentials.
- Revoke the old credential at the provider that issued it, create a new one, update it in Northflank and redeploy. Revoking only inside Northflank does not stop a copied key from working.
- Check usage and billing at each AI provider for unexpected requests, especially since 29 Oct. If you see unexpected spend, contact the provider directly.
- Check Northflank's audit logs for API keys, users, SSH keys or webhooks you did not create.
- Disable public access on addons where it is on, as Northflank advises, and reconnect your Git integrations.
- Set spending limits and restrict new AI keys to the models you use. This is our advice, not Northflank's.
What we could not confirm
We read Northflank's status page directly and a third-party summary of it. Northflank has not said how the attacker got in, how many customers were affected, or which secrets were actually taken; the AI key misuse comes from user reports relayed on the status page. The status page mentions CVE-2026-98432 as patched but does not say it was the way in. We have not tested anything on Northflank ourselves.
Watch the short video
The video loads from YouTube (privacy-enhanced mode) only when you press play.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
- Northflank status page: Security Incident (30 Oct to 2 Nov 2026, official, read directly) (opens in a new tab)
- Qovery: Northflank security incident, secrets and your own cloud (31 Oct 2026, third-party write-up that summarizes the status page) (opens in a new tab)
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.