Northflank environment-variable security incident

Urgent rotation guidance covers all keys, while the exact extent of compromise remains under investigation.

Last modified

Summary

  • Environment: Northflank hosting platform and customer environment variables
  • Operational impact: Control-plane secrets targeted; Northflank reports running workloads unaffected
  • Financial impact: No confirmed incident cost quantified
  • Record status: Developing record. Reviewed November 2, 2026; updated as evidence emerges.

What happened

Northflank investigated a security incident after a Wiz alert at 11:43 UTC on October 30, 2026. It patched network policies and warned customers to disable and rotate keys. [1]

Impact

Northflank told customers to assume environment variables had been decrypted. This precaution does not prove every secret was stolen. It subsequently relayed customer reports of unauthorized AI API-key use. Several platform components were marked with major outages on October 31; that status did not establish every workload was unavailable. [1]

On November 2, Northflank said running workloads were unaffected and it had found no signs of access to workloads or their data. Evidence pointed to control-plane secrets; it said forward-deployed and dedicated control-plane customers were unaffected. Intermittent platform degradation accompanied its own key rotation and hardening. [1]

Timeline

  1. Alert, patches and urgent rotation warning

    The status updates record the alert, network-policy patches and customer warnings.

    [1]
  2. Audit logs and more secret-rotation tools opened

    Northflank made audit logs available to all users and enabled MySQL and Redis password rotation after the previous day’s PostgreSQL and MongoDB changes. It added MinIO secret rotation at 22:32 UTC and RabbitMQ rotation at 23:31 UTC, both for all customers.

    [1]
  3. Containment and workload assessment updated

    At 11:09 UTC, the status update clarified scope while independent forensic review continued.

    [1]
  4. Briefing updated

    This briefing was last reviewed and updated on November 2, 2026.

Threat Group & Attack Vector

The precise entry path, actor and affected-user total remain unresolved. Similarities to indicators in other reporting do not establish a common attacker. [1]

Actors

  • No threat actor group has been identified in the reviewed public evidence.

TTPs

  • No specific MITRE ATT&CK technique is currently mapped for this case.

Response

Customers were advised to revoke keys with their issuers, replace secrets across workloads and secret groups, and review usage and billing. Northflank also recommended disabling public exposure of addons. Its late October 31 updates made MinIO and RabbitMQ secret rotation available to all customers and repeated the instruction to rotate all secrets. [1]

Northflank believes it contained the attack vector within an hour of the first alert and found no subsequent attacker presence. Independent review continues. Where possible, it revoked tokens, sessions and integrations on customers’ behalf; users must sign in again, reconnect integrations and rotate all project and integration secrets. [1]