Northflank warns all customers to rotate secrets after AI keys were abused in October breach

On October 30, 2026, Northflank disclosed a security incident and told users to assume all environment variables had been decrypted. Its status timeline reports a Wiz threat alert at 11:43 UTC, a network-policy patch at 12:02, and additional patches at 12:50 and 13:05. By 15:12 UTC the platform had enabled Postgres and MongoDB secret rotation. Northflank subsequently said multiple customers reported unauthorised use of AI API keys stored on the platform. On October 31 it made audit logs available to all customers, including free users, and enabled MySQL and Redis secret rotation. The incident remained under investigation at the last checked status.

A PaaS environment variable may hold production AI-provider credentials, payment keys, database passwords, signing keys and registry tokens. If stolen, these keys can be used outside the hosting platform without modifying deployed code. The immediate work is to revoke keys at their issuers, issue scoped replacements, update workloads, inspect usage and billing, and validate service recovery. This is an active operational incident, not just a theoretical platform-security concern.

The primary status page explicitly tells all users to assume environment variables are decrypted, including workload secrets, secret groups and global secrets. It reports multiple customer confirmations of AI key misuse and later says users reported unauthorised AI API calls. These are customer reports acknowledged by the vendor, not a verified total of compromised accounts or the full root cause. Northflank recommends disabling public exposure of addons where configured.

Northflank says Wiz alerted it on October 30 at 11:43 UTC, engineers reviewed the alert a minute later, and network patches began within 19 minutes. Database secret-rotation features were progressively enabled: Postgres/MongoDB on October 30, MySQL/Redis on October 31. Audit logs became available to all tiers October 31. These changes do not automatically revoke third-party provider credentials.

Inventory every key and password stored on Northflank. Revoke each at its original provider, generate a new secret with the minimum needed privileges and a sensible spend ceiling, update Northflank configuration, then verify the live workload uses the replacement. Review provider-side access logs and AI inference invoices for unfamiliar calls or sudden usage. Check addon public exposure and Northflank audit logs. Rotate signing and encryption keys and consider downstream session invalidation where their compromise could permit impersonation.

Wiz's October 30 investigation counts at least nine AI developer-platform incidents, including Northflank. Wiz found evidence of downstream abuse of stolen inference credentials and active key-resale markets, but explicitly does not prove that the same attacker conducted every incident. Northflank reports similar IP indicators and refers users to Wiz's analysis; this is corroborating context, not a conclusive attribution.

Northflank has not published a final forensic root-cause report, definitive affected-user count or precise exfiltration scope. The provider's all-user rotation instruction is precautionary and should not be rewritten as proof that every secret was actually stolen. Status and remediation availability may change after this snapshot.