Northflank reports unauthorised AI API-key use after a secrets breach
Northflank asks customers to rotate project and integration secrets even without visible suspicious activity. Changing a variable does not revoke a copied key at its provider.
Going deeper
Generated image · SecuFocus
At a glance
Key points
Have you stored cloud, AI or database credentials in Northflank? Its November 2 update calls for rotation of project and integration secrets, even if you have not noticed unusual activity. Customers have reported unauthorised AI-key use. Revoke old credentials with the services that issued them, deploy replacements and review usage logs rather than only editing configuration.
The investigation points to control-plane secrets
Northflank opened its security incident on October 30, 2026. Subsequent updates told customers to assume their environment variables were compromised and reported unauthorised use of AI API keys.
In its November 2 update at 11:09 UTC, the company says available evidence points to secrets held in its control plane. It says it has seen no sign of access to workloads or workload data, and that dedicated or forward-deployed control-plane customers are unaffected. That is the provider’s stated scope at that time, not a finding independently audited by SecuFocus.
Revoke credentials with the issuer, then reconnect their users
Northflank asks customers to rotate affected project and integration secrets. It prioritises AI and cloud provider keys, payment credentials, private keys, databases and other services. A lack of unexpected spending is not a reason to skip that review.
A copied key can remain valid after you replace the corresponding Northflank variable. Revoke it with the issuer, create a replacement with the required permissions and update the services that use it, checking that they recover correctly. Coordinate with the application owner so rotation does not unexpectedly remove access or stop a service.
The company says it revoked Northflank tokens and sessions, repository integrations and certain cloud identities where it could act on customers’ behalf. Customers are asked to sign in and reconnect integrations. This does not establish that every customer-supplied third-party key has been revoked.
Check provider logs and bills as well
Review usage records for the services whose credentials were stored on the platform. Unexpected OpenAI or Anthropic activity or spending should be raised with that provider and Northflank. The incident record says audit logs were made available to all customers, including free accounts.
Northflank says it quickly contained the initial attack vector and engaged independent forensic auditors. The investigation continues and a root-cause report is planned. Those statements do not establish attacker attribution, a total loss figure or automatic restoration of trust in every application.
Check and explore
Sources for this article
Numbers connect each reference to the passages that use it. Dates show when the documentation was consulted.
This article draws on the sources above. The exercises are for you to try on your devices; SecuFocus does not present them as tests carried out by its editorial team. Interfaces and features can change. Method and corrections.
Cite this article
Keep this reference with the article when you save or share it.