Railway says an attacker decrypted environment variables in up to 100,000 workspaces
Railway's October 22 preliminary report says an attacker pulled encrypted customer environment variables, obtained CI credentials to decrypt a subset, and hunted for AI provider keys. At most 1.85% of workspaces, about 100,000, may be affected; all Railway API tokens were revoked.
Platform-as-a-service provider Railway published a preliminary incident report on October 22, a day after disclosing anomalous activity around the systems that store customer environment variables. Railway says the attack window opened on October 20 at 13:58 UTC with an attempted privilege escalation in build infrastructure. Between 04:24 and 05:27 UTC on October 21, the attacker queried encrypted environment variables, obtained CI credentials, and decrypted artifacts holding further API access. Logs show the attacker searching for named AI provider API keys. Railway estimates that at most 1.85% of workspaces, about 100,000, had variables potentially exposed, and it sent broader key lists to upstream vendors as a precaution. It revoked all Railway API tokens, rotated bucket credentials, and confirmed on October 22 that the attacker no longer had internal access. The entry point has not been disclosed.
Why it matters
Encryption at rest did not help once the attacker reached the CI identity that could decrypt. Railway believes it is one of a series of attacks on platform companies aimed at AI inference keys, the same target as the Zeabur and OpenCode incidents. Static API keys stored by a third party are only as safe as that party's least-protected credential.
Rotate every variable set on Railway before October 21, especially AI provider keys and private registry credentials, and recreate CLI and CI tokens. Remove public network access to databases. Review GitHub audit logs, installed apps and registry logs such as Docker Hub. Railway says it cannot refund AI spend made with stolen keys, so set spend caps with providers. Where providers support it, move to short-lived tokens through workload identity federation.
Source: Railway
Related on Start with Identity
- BlogTrigger.dev says an attacker read environment variables for a subset of customer organizations
AI workflow platform Trigger.dev disclosed on November 1 that an attacker gained unauthorized access to environment variables for a subset of organizations. It
- BlogNorthflank tells customers to assume every environment variable was decrypted after AI keys are abused
After a Wiz alert on October 30, cloud platform Northflank told customers to assume all environment variables were decrypted and rotate every key. Customers the
- BlogOne actor signed in as Entra ID apps with stolen secrets and reached 27 organizations, Todyl says
Todyl is tracking an ongoing campaign in which one operator uses stolen client secrets to sign in to Microsoft Entra ID as app registrations, reaching 27 organi
- CVEtj-actions/changed-files tags repointed to dump CI secrets into logs
An attacker repointed tj-actions/changed-files version tags to a commit that read the GitHub Actions runner's memory and printed its secrets into workflow logs.
- CVETrivy release and GitHub Action tags hijacked to steal CI secrets
With credentials left valid by a non-atomic rotation, an attacker shipped a malicious Trivy v0.69.4 and repointed 76 of 77 trivy-action tags to code that dumped
- CVEOver-scoped CodeBuild GitHub token let an attacker ship code in Amazon Q Developer 1.84.0
An inappropriately scoped GitHub token in the CodeBuild configuration for the Amazon Q Developer VS Code extension let an attacker commit code that shipped auto