Railway urges credential resets as investigator alleges $371,000 crypto theft

Railway, a cloud deployment platform, has urged every user to replace stored secrets after disclosing on Oct. 21 that an attacker may have accessed encrypted customer environment variables and read some of their contents.

Railway said those variables may contain API keys, database credentials and private registry credentials. Although its initial analysis suggested the impact might be limited to a subset of users, its security disclosure urged all customers to replace stored variables and credentials immediately and review service logs for unusual activity.

The company believes the incident is part of a series of attacks against platform companies aimed at compromising AI inference providers. It said it had notified upstream providers to revoke keys proactively. It has not disclosed a root cause or an affected-customer count.

On-chain investigator @tayvano_ separately alleged cryptocurrency theft involving keys stored in Railway. The investigator estimated losses of roughly $371,000 across at least 19 EVM chains and identified an address as belonging to the attacker.

Railway has not confirmed the alleged theft, its connection to the incident or the $371,000 estimate.

For crypto teams running applications on Railway, the practical response is to review which credentials those applications stored on the platform and the services those credentials can access. Railway's recommendation covers all environment variables and API keys stored there, as well as private registry credentials.

Credential resets and the partial return of builds

Railway initially paused all deployments while investigating, preventing customers from rolling out new versions of their applications. That created an obstacle to deploying replacement credentials, alongside the separate task of revoking potentially exposed credentials at the services that issued them.

Railway also reset credentials for access to its own platform. At 04:17 UTC on Oct. 22, it said it had invalidated all Railway API tokens. Customers using those tokens to integrate with its public API were told to create replacements.

At 12:30 UTC on Oct. 22, Railway said deployment wait times were improving and most queued deployments were starting sooner. Builds were available for Pro and Enterprise workspaces, while Railway continued working to restore access for Hobby, Free and Trial. Some deployments still faced delays.

Railway's Oct. 22 AWS guidance calls for deactivating potentially exposed access keys, deploying replacements and checking CloudTrail and billing for activity the customer did not generate. Its Google Cloud guide similarly recommends disabling potentially exposed service-account keys, replacing them, and reviewing Cloud Audit Logs and billing.

The Google Cloud guide adds a timing caveat: short-lived tokens already issued from a disabled key can remain valid for up to an hour.

Railway said it would email affected customers as accounts were confirmed.