Railway disclosed a security breach last week that should get the attention of any team storing API keys in a deployment platform, and that means most teams building anything with AI today.
Between October 20 and 22, an attacker accessed Railway’s internal systems and targeted AI provider API keys stored in environment variables. Railway is a popular platform-as-a-service tool, used to deploy web applications and background services without managing servers directly. The attacker reached environment variables for approximately 100,000 workspaces, roughly 1.85% of all active Railway deployments. Railway has since revoked credentials with affected vendor partners and accelerated a rollout of single-tenant builder infrastructure.
The mechanism matters here. Environment variables are how most deployment platforms store secrets: API keys, database passwords, third-party service credentials. They’re an industry standard, not an unusual practice. When an attacker breaches the platform itself, rather than an individual app, all of those stored secrets become accessible in one move. It isn’t a flaw in how you managed your own system. It is a platform-level breach, and the exposure is yours regardless.
What makes this particularly relevant right now is the category of credentials that were targeted: AI provider API keys. OpenAI, Anthropic, and similar providers bill by usage, meaning a stolen key doesn’t just expose your data. It runs up your bill. Attackers who steal API keys often resell them or use them to run high-volume inference at your expense. A compromised key can generate thousands of dollars in charges before anyone notices.
The immediate action is straightforward. If your team uses Railway and hasn’t already rotated credentials, do it now. Check your AI provider dashboards for unexpected usage spikes in late October. Review which services have access to which keys and whether that access is still necessary. Railway’s recommendation to revoke and reissue is the right call, and doing it promptly limits the window of exposure.
The broader lesson is worth sitting with. The convenience of platform-based deployments comes with a shared-custody model for your secrets. You trust the platform to protect what it holds. That trust isn’t unconventional, but it requires treating secrets as rotatable assets rather than permanent credentials. Keys that never expire are a liability when any platform in the chain gets breached.
Automated key rotation and scoped API access, where each service gets the minimum permissions it needs, are the right safeguards for a world where platform breaches are a matter of when, not if.
Want to explore how a proper DevOps security baseline could protect your business? Let’s talk.