← Back to Tech · Security
a vast purple-lit cloud data center shaped like a grand train station, glowing light rails running between server racks, golden keys and locked vault boxes floating in the air, some boxes bursting open and spilling glowing characters, a distant hooded silhouette, no logos, no text

Railway tells every user to rotate their keys after hackers reached encrypted secrets

Railway, the cloud platform developers use to build and host apps, says an unauthorized third party “may have accessed encrypted environment variables and, for some of them, obtained the decrypted contents.” It’s telling all users to rotate their keys (Railway).

What happened

Railway says it spotted unusual activity on Oct 21 in systems that store customer environment variables, which often hold API keys and database and registry credentials. It believes the attack is part of a series targeting platform companies to compromise AI inference providers, and it has asked those upstream providers to revoke keys (Railway).

Railway says the impact may be limited to a subset of users and that it will email affected customers directly. It hasn’t said how many people were affected or what the root cause was, and it plans to publish a post-mortem (TechCrunch).

What Railway did

  • Paused builds and deployments while it investigated, then began restoring them (TechCrunch).
  • Reset the S3 credentials for every storage bucket and invalidated the GitHub tokens it held for accounts (Railway).

What to do if you use Railway

  • Rotate every environment variable stored in Railway, including API keys, database credentials and private registry credentials.
  • Check your service logs for unusual activity.
  • Redeploy services that use storage buckets so they pick up the new credentials, and reconnect GitHub yourself (Railway).

Koffee take: if you host a Discord bot, game server tool or side project on Railway, rotate those keys tonight.

Filed Oct 22, 2026 ~9 PM CT — Night pass. Sources: Railway Blog — Security Disclosure: Wednesday October 21st · Railway Blog — Redeploy Buckets and Reconnect GitHub After the Credential Reset (Oct 22, 2026) · Railway Status — incident updates · TechCrunch — Railway urges all users to revoke secret keys (Oct 22, 2026).