Northflank was breached today. If your apps run on the platform, every environment variable you ever stored there — database passwords, AI API keys, Stripe credentials, Twilio tokens — should be treated as compromised right now. Multiple users have already confirmed their AI keys are being actively drained. This is not a “potential exposure” advisory. The secrets are gone. Go rotate before finishing this paragraph.
What Happened
At 11:43 UTC on October 30, Wiz’s threat detection fired on anomalous activity inside Northflank’s infrastructure. By 1:58 PM UTC, Northflank’s incident page confirmed the worst: all environment variables on the platform have been decrypted. That includes secrets stored in workloads, secret groups, and global secrets. By 3:12 PM, Northflank noted that multiple customers had reported their AI API keys were already being used by unauthorized parties. The investigation remains ongoing as of 7:28 PM UTC.
The attacker knew exactly what they were after. AI inference keys are not just credentials — they are cash. A single stolen API key can generate tens of thousands of dollars in compute charges in under 48 hours before anyone notices.
Rotate These Right Now
Do not wait for Northflank’s post-mortem. If you use the platform, work through this list immediately:
- Northflank dashboard: Rotate everything — workload secrets, secret groups, and global secrets. Northflank has enabled automatic rotation for Postgres and MongoDB connections.
- AI API keys: OpenAI, Anthropic, Google, Mistral — revoke and reissue. Check your usage dashboards for billing spikes you did not authorize.
- Payment credentials: Stripe, Braintree, any payment processor key stored in Northflank env vars.
- Communication services: Twilio, SendGrid, Postmark tokens.
- Database connection strings: Change passwords even if Northflank’s auto-rotation handles it — do it manually to confirm.
- Your own repos: Search GitHub or GitLab for any secrets that may have been committed alongside the ones Northflank held.
This Is the Third PaaS Breach in Eight Days
Northflank is not an isolated incident. Railway was breached eight days ago, exposing encrypted environment variables for up to 100,000 workspaces. Zeabur was hit in the same wave. Three mid-market PaaS platforms in eight days, all with the same target: AI inference credentials.
Nevo David, who had migrated to Northflank specifically after the Railway breach, wrote on X: “Now Northflank is breached. They asked me to migrate to them after the Railway breach. I think it’s so bad to be a PaaS company in 2027. Move to the big ones.”
That reaction is understandable, but the root cause is not specific to Northflank or Railway. It is structural.
The Architecture Problem PaaS Cannot Fix
Every PaaS platform that injects secrets into running containers must store those secrets somewhere. If the management plane is compromised, an attacker can call the same decryption APIs the platform itself uses. There is no version of managed secret injection where this risk disappears entirely. The Hacker News thread on the breach put it bluntly: “If your management/API web server is compromised, users’ secrets can be obtained.”
What makes this wave different is the attacker’s economic model. Cloud Security Alliance research on LLMjacking found AI-targeted credential theft up 376% from Q4 2025 to Q1 2026. A single stolen API key generated an $82,000 bill in 48 hours in one documented case. PaaS platforms are not targets because they are poorly secured — they are targets because breaching one platform yields thousands of AI keys at once. It is a numbers game, and mid-market PaaS providers just lost it.
The Fix: Stop Storing Secrets on the Platform Running Your Code
The architectural lesson from three breaches in eight days is simple: your secrets and your runtime should not live in the same trust domain. An external secrets manager — AWS Secrets Manager, HashiCorp Vault, or Doppler — holds your credentials separately from the platform executing your containers. Even if your PaaS is breached, the attacker gets your code environment but not the keys to everything it touches.
This is not a novel concept. It is just one most developers have deferred because environment variables are convenient. Three breaches in eight days is the universe’s way of saying the convenience is not worth it anymore.
Rotate your secrets now. Then move them somewhere the platform cannot reach.

