Nullify

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Home
›
Incidents
›
Northflank Security Incident: What Happened and What to Rotate
Leaked secrets
Adjacent

Northflank Security Incident: What Happened and What to Rotate

An attacker targeted secrets held in Northflank's control plane, and Northflank told every customer to assume their environment variables were decrypted and rotate all keys.

Nullify Team
·
Disclosed
October 30, 2026
·
Updated
November 17, 2026

What happened in the Northflank security incident?

On its status page, Northflank says a threat alert reached it at 11:43 UTC on October 30, 2026 and patches went out from 12:02 UTC. It says the activity was focused on secrets held in its control plane, that the exploit was patched within 60 minutes of notification, and that it patched a vulnerability it identified as CVE-2026-98432 across its fleet, including bring-your-own-cloud clusters.

At 13:58 UTC Northflank told customers to assume all environment variables had been decrypted and to disable or rotate all keys. Later that day it said users had reported unauthorized use of AI API keys supplied to the platform. A November 6 update says the first known decryption of secrets happened between 02:39 and 03:08 UTC on October 30, and that it found no evidence customer workloads or workload data were accessed.

Who is affected by the Northflank incident?

  • Every Northflank customer: the company told all customers to assume their environment variables were decrypted.
  • AI provider keys stored as Northflank variables, which users reported being used without authorization.
  • Bring-your-own-cloud clusters received the same patch.

How to check if you're affected

  1. Review billing and usage logs at every AI provider whose keys were stored on Northflank.
  2. Review provider logs for every other secret stored on the platform.
  3. Use Northflank's platform audit logs, which it enabled for all customers, including free users, on October 31.

What to do now

  1. Rotate all environment variables and secrets stored on Northflank, and revoke the old keys at each provider.
  2. Use Northflank's add-on secret rotation for Postgres, MongoDB, MySQL, Redis, MinIO and RabbitMQ.
  3. Disable public add-on access where it's enabled.

What the Northflank incident means for secrets stored in platforms

A deployment or AI platform that injects environment variables at runtime has to be able to decrypt them, so one compromise of its control plane or build system can expose every customer's keys at once. Treat platform-stored variables as copies of a credential, not as the credential's only home: keep an inventory of which keys live where, scope each key to the one service that needs it, set spend limits on AI provider keys, and make rotation a scripted step rather than a scramble. When a provider tells you to rotate, revoke the old key at the issuer, because deleting the variable from the platform doesn't invalidate it.

Where Nullify fits

How Nullify Covers This Class of Attack

Adjacent
Secrets Detection

Nullify finds credentials in code and verifies which ones still work with the provider that issued them (AWS, GCP, Azure, GitHub, GitLab, Stripe and Slack), so live keys rank first, then routes rotation to each owner. Rotation happens with the provider; Nullify doesn't rotate keys.

These secrets were stored in the platform, not in your code. Nullify's live-key check helps where the same keys also sit in your repositories or config.

Frequently Asked Questions

What happened in the Northflank security incident?

On October 30, 2026, an attacker exploited Northflank's control plane to target stored secrets. Northflank patched within an hour of notification, told all customers to assume their environment variables were decrypted, and later said users reported unauthorized use of AI API keys.

Should Northflank customers rotate their keys?

Yes. Northflank told all customers to disable or rotate every key stored as an environment variable. Revoke the old keys at each provider, rotate add-on credentials with Northflank's rotation tool, and turn off public add-on access.

Were Northflank workloads accessed?

Northflank says it found no evidence that customer workloads or workload data were accessed. The activity it describes was focused on secrets held in its control plane.

Update Log

  • Nov 17, 2026: page published from Northflank's status page updates through November 6.

Check your own code for the bug behind this incident

Nullify's AI harness finds, proves and fixes the same class of vulnerability in your code and dependencies, and hands your team a merge-ready pull request.