Railway Says Intruder May Have Accessed Customer Secrets, Urges Credential Rotation
Railway disclosed unauthorized access to customer environment variables, urging credential rotation.

Railway, a Platform-as-a-Service provider, reported that an unauthorized third party may have accessed customer environment variables, potentially exposing sensitive data like API keys and database credentials. The incident has prompted the company to recommend credential rotation as a precautionary measure.
Railway disclosed anomalous activity concerning systems that store customer environment variables, indicating that an unauthorized third party may have gained access to encrypted data. The company noted that the impact is confined to a subset of users, but did not specify how many customers are affected. This incident raises concerns about the security of sensitive data stored within platform environments.
The investigation revealed that attackers may have accessed decrypted contents of the environment variables, which are used to store sensitive information such as API keys and database credentials. Environment variables are user-defined key-value pairs that help manage sensitive data without hard-coding it directly into source code. This method is common in containerized applications and operating systems, allowing for more secure data management.
The attack on Railway appears to be part of a broader trend targeting platform companies, with the ultimate goal of compromising artificial intelligence (AI) inference providers. Security researcher Taylor Monahan noted that attackers may have drained cryptocurrency wallets whose private keys were stored on Railway. The first known theft transaction reportedly occurred two hours before the incident was disclosed, indicating a well-timed attack.
Railway has taken steps to mitigate the impact of the breach by rotating all bucket credentials and invalidating API tokens. The company has also restored builds for Pro and Enterprise workspaces, allowing affected customers to apply new credentials. However, builds for Hobby, Free, and Trial workspaces are still being worked on, with some deployments experiencing longer than usual wait times.
The incident underscores the growing trend of LLMjacking, where attackers gain unauthorized access to cloud environments to run AI models, shifting the computational costs to the legitimate owners. This method allows attackers to exploit resources without detection, as the AI workloads processed in compromised environments can remain hidden from the victim organization.
Railway has notified upstream providers to revoke compromised keys proactively and is continuing to communicate with impacted customers. New signups for the service have been temporarily paused to focus on existing users. The company has stated that it is working diligently to restore full service across all workspaces.
It remains unclear how many customers were affected by the breach and whether any of the stolen API keys have been abused.
What security teams should do
- Rotate all API keys and credentials immediately.
- Monitor for unauthorized access attempts using compromised credentials.
What it meansRailway reported unauthorized access to customer environment variables, which could expose sensitive data. This incident highlights the risks associated with credential management in cloud environments.
Ask your IT team this weekHow are we managing API keys and environment variables in our systems?What steps are in place to detect unauthorized access to our cloud environments?
DecisionThe IT team will review and rotate all API keys, and security will verify this is completed.