Northflank urges immediate secret rotation after AI key compromise

Northflank, a platform-as-a-service provider, has confirmed a critical security incident involving the compromise of user-supplied secrets. On October 30, 2026, the company issued urgent guidance for all users to rotate their environment variables and API keys immediately following reports of unauthorized activity.

What happened

The incident centers on the unauthorized use of AI API keys that users had stored within the Northflank platform. Users began reporting suspicious activity linked to these credentials, prompting an internal investigation by Northflank’s security team. The company stated that these reports align with a broader pattern of attacks specifically targeting AI credentials across the industry.

In response, Northflank advised that all environment variables should be considered compromised. This includes secrets stored in individual workloads, secret groups, and global secrets. The company emphasized that this is not limited to AI keys but extends to any credential managed through their interface. Users were instructed to revoke existing credentials with their issuing providers, generate new ones, and update their configurations in Northflank without delay.

As part of the mitigation effort, Northflank enabled automatic secret rotation for Postgres and MongoDB addons for all users. They also recommended disabling public access to addons where it had been previously enabled. The investigation remains ongoing, with the company promising further updates as more details are confirmed.

Key details

• Incident date: October 30, 2026.
• Affected assets: User-supplied secrets, including AI API keys, environment variables, and addon credentials.
• Required action: Immediate rotation of all secrets and credentials; revocation of old keys with external providers.
• Platform response: Automatic secret rotation enabled for Postgres and MongoDB; recommendation to disable public addon exposure.
• Context: The attack pattern matches IP addresses identified in Wiz’s “Black October” report.
• Status: Investigation is ongoing; no further confirmed findings were shared as of the latest update.

Background

Environment variables are a common method for injecting configuration data and secrets into software applications. In cloud platforms like Northflank, these variables often hold sensitive information such as database passwords, third-party API keys, and encryption tokens. When a platform manages these secrets, it typically encrypts them at rest and decrypts them when injecting them into running containers or services.

A compromise of these variables means that an attacker may have gained access to the decrypted values. This allows them to impersonate the application or service associated with those keys. In this case, the focus is on AI API keys, which can be expensive to misuse due to high computational costs. The reference to Wiz’s “Black October” report suggests this incident is part of a coordinated campaign targeting cloud infrastructure and credential stores rather than an isolated bug.

Why it matters

For teams that self-host or manage their own infrastructure, this incident highlights the risks inherent in trusting third-party platforms with sensitive credentials. Even if your own servers are secure, the tools you use to deploy and manage them can become attack vectors. The advice to assume all environment variables are compromised is a severe warning. It implies that the breach may not be limited to a single vector or a specific subset of users.

The financial impact of compromised AI keys can be significant. Unlike static passwords, API keys often grant access to pay-per-use services. Unauthorized usage can lead to unexpected bills before the abuse is detected. Furthermore, the need to rotate every secret disrupts development workflows. Teams must coordinate to update configurations across multiple environments, test for regressions, and ensure that no legacy systems rely on the revoked keys.

This event also underscores the importance of monitoring. Without reviewing billing logs and usage metrics from external providers, teams might not realize their keys have been stolen until they receive a large invoice. Proactive detection is difficult when the attack surface extends beyond your own network perimeter.

What you can do

• Rotate all environment variables and secrets stored in Northflank immediately, including global and group secrets.
• Revoke the compromised keys with their original providers, such as AI services, database hosts, or payment gateways.
• Review billing and usage logs from all third-party providers for unusual spikes or unknown activity.
• Disable public access to any database or cache addons in your Northflank dashboard.
• Update your local development environments and CI/CD pipelines to use the new credentials.
• Monitor Northflank’s status page for further updates regarding the scope of the investigation.