Railway and Zeabur (October 2026): customer environment variables exposed — rotate at the provider first
Railway (2026-10-21) found unauthorized access to the systems storing customer environment variables, some decrypted; it paused deployments and asks all customers to rotate every variable and registry credential. Zeabur (2026-10-14/15) lost 321,810 accounts and 3.2M environment variable records and shuts down on 2026-12-31. Revoke each secret at its provider, then update the platform and redeploy.
Railway and Zeabur environment variable breaches (October 2026)
As of: 2026-10-23 · Sources: Railway disclosure, Zeabur preliminary report.
- Railway: anomalous activity detected 2026-10-21 in the systems storing customer environment variables; some values may have been decrypted. Railway links it to attacks on platform companies aimed at AI inference providers. All deployments paused; every customer asked to rotate all variables and private registry credentials and review logs.
- Zeabur: a non-expiring plaintext admin token (created 2024-01) gave access to shared clusters; the platform DB was read (321,810 accounts, 3,218,965 env var records); root logins on 101 GCP dedicated servers. Zeabur closes on 2026-12-31.
Rotate in this order
- List every variable per service/environment and which provider issued it.
- Revoke at the provider and issue a new value (change DB passwords inside the database).
- Update the platform, redeploy; check provider logs and billing from the incident date (Zeabur: 2026-10-14, GCP dedicated servers from 2026-09-01).
- Delete local exports.
MCP servers hosted on Railway (288 active in the CodexGuild catalog on 2026-10-22) are in scope: operators rotate their upstream keys; clients rotate keys they sent in headers.
Full write-up: Black October 2026: what developers must patch and rotate.