The urgent story in cybersecurity news today is a break-in at Railway, the platform many teams use to host apps and databases. Railway published a preliminary report on October 22, 2026, written by Jacob Cooper and Angelo Saraceno. It says an attacker was inside Railway's internal systems from October 20 to October 22, 2026, hunting AI provider API keys, and decrypted a subset of the environment variables customers store on the platform. At most 1.85% of all workspaces, about 100,000 workspaces, had some variables potentially compromised. If you signed up for Railway before October 21 and stored keys there, Railway's advice is plain: rotate them. The checker below scores your rotation risk using Railway's own risk buckets.
The scale needs care. Railway says at most 1.85% of all workspaces had some environment variables potentially compromised, which it puts at about 100,000 workspaces. It also says the number of users touched by vendor revocation requests is larger than 100,000, because out of caution it handed some vendors all of the keys stored on the platform. Railway names two high-risk buckets it is contacting proactively: workspaces with a very large number of environment variables, and environments with a high amount of AI keys from vendors. If your workspace sits in either bucket, treat this as a rotate-today item even if no email has arrived.
Most breach advice starts with passwords. This one does not, because the attacker never needed yours. Railway states plainly that the attacker did not access Railway user accounts and that individual accounts were not logged into. The break-in hit internal systems, and the prize was the secrets layer underneath the accounts: the API keys, database credentials and registry credentials that apps store as environment variables so they can run unattended. Whoever holds those keys can call the provider as your app, spend against your account, and read what your app can read, all without touching your login.
That is also why the vendor list matters. On October 21 at 09:25 UTC, Railway proactively notified vendors and asked them to revoke keys. The report names GitHub, GitLab, Anthropic, OpenAI, OpenRouter, Stripe, and Google among them. If you received a revocation notice from one of those vendors this week, this incident is the likely reason. Railway's own response went further than notifications: it rolled all of its internal keys, then rolled them again after confirming the attacker was out; it rolled credentials for all storage buckets on the platform; it rebuilt its internal tooling from validated source; it accelerated a move to fourth-generation single-tenant builder infrastructure; it engaged external incident response experts and the authorities; and it added a way to mass-revoke Railway application permissions whenever suspicious activity is suspected.
Five answers, scored in your browser against the risk buckets Railway names in its report. Nothing is sent anywhere.
Agent Auth Gateway, Ingenious AI's control point for AI agent credentials, is built for the problem this breach exposes: valuable keys sitting in one store, reachable in bulk, with no per-key limit on what they can do once copied. The Gateway puts budget caps, allowlists and a kill switch in front of the keys your agents use, so a single stolen key cannot spend or roam without limit. See how Agent Auth Gateway works.
1. What was the attacker hunting for inside Railway?
2. How many workspaces had environment variables potentially compromised, at most?
3. Did the attacker log into Railway user accounts?
4. A vendor emailed you that a key was revoked. What does that prove?
5. What is the safe order for rotating a stored key?
The Railway breach is a break-in at Railway, the app hosting platform, in which an attacker got into internal systems between October 20 and October 22, 2026 and decrypted a subset of the environment variables customers stored there. Railway published the details in a preliminary report on October 22, 2026. The attacker was hunting AI provider API keys. User accounts were not accessed.
Railway says at most 1.85% of all workspaces had some environment variables potentially compromised, about 100,000 workspaces. Because the keys were envelope encrypted, Railway cannot tell which specific variables in a project were decrypted. Railway is contacting customers it counts as definitely affected or high risk, including workspaces holding very many variables or many AI keys.
The attacker's goal, per Railway's report, was AI provider API keys, taken to perform distillation attacks. Railway says the attacker had access to abliterated models and substantial compute and used sophisticated exploits against its build infrastructure. Railway has not published the exploit details or indicators of compromise, and says forensic work is still running, with a final report to come.
No. On October 21, 2026, Railway asked vendors including GitHub, GitLab, Anthropic, OpenAI, OpenRouter, Stripe and Google to revoke keys, and out of caution it gave some vendors every key stored on the platform. More users got revocation notices than were impacted, Railway says. Treat the email as a prompt to rotate, not as proof your workspace was compromised.
Rotate them. Railway recommends that everyone who signed up prior to October 21, 2026 rotate the keys stored on Railway, out of caution. Create the new key at the provider, update it in Railway, redeploy, then revoke the old key at the provider. Also remove public network access to databases, check GitHub audit logs and app access, and check Docker Hub registry audit logs.
Sources: Railway, "Preliminary Report: Oct 21st Security Incident", by Jacob Cooper and Angelo Saraceno, Railway blog, October 22, 2026, updated October 23, 2026 (attack window, privilege escalation in build infrastructure, CI credential access, decrypted subset of environment variables, the 1.85% and about 100,000 workspace figures, the high-risk buckets, the October 21 vendor notifications, and the customer rotation guidance) · Safeguard, "Railway Preliminary Incident Report: CI Credentials and AI Key Theft" (independent summary of the same report) · Claroc, "Railway security incident" (rotation guidance for database credentials and the sealed-variables open question) · Pandromeda, "Railway Security Breach: What to Rotate Right Now" (status page timeline, token and session invalidation times).
Questions about this check: message Ingenious AI on WhatsApp.