Data Breach · Security Incident HOT

Railway Hack: Cloud Platform Says Attackers May Have Decrypted Customers’ API Keys and Passwords

Published October 22, 2026

Developers and companies that host apps on Railway, a cloud platform that says it serves more than 2 million developers, were told on October 21, 2026 that attackers may have decrypted the passwords and secret keys their apps run on, including keys to paid AI services. Railway has not said how many accounts were affected, and there is no lawsuit or settlement.

Data breach illustration — Railway cloud platform security incident, October 2026

What Happened

On October 21, 2026, Railway disclosed that it had detected “anomalous activity involving systems that store customer environment variables.” According to the company, an unauthorized third party may have accessed those encrypted variables and, “for some of them, obtained the decrypted contents.” Railway CEO Jake Cooper wrote on X that the company had been alerted to “malicious activity that compromised Railway’s servers.”

Railway said its initial analysis suggests the impact “may be limited to a subset of users,” but it told every customer to replace all of the secrets stored on its platform and to check their logs for unusual activity. It paused all deployments, revoked and reissued storage credentials, signed some users out, and said it would email the customers it confirms were affected. Railway has not said how many accounts were affected or how the attacker got in, and a Railway employee said on Hacker News that a formal postmortem will follow once service is restored.

Status Under investigation disclosed October 21, 2026 · deployments paused
What Was Exposed API keys · database passwords · registry credentials secrets stored as “environment variables” by Railway’s customers
Can I Claim? No — no lawsuit or settlement

What Railway Is, and Why This Is a Big Deal

Railway is a cloud platform: instead of renting and managing their own servers, developers hand their code to Railway, and it runs their websites, apps and databases. When it announced a $100 million Series B funding round on January 22, 2026, Railway said more than 2 million developers and “tens of thousands of companies,” from small shops to Fortune 500 firms, build on it.

To work, almost every app needs secrets: the password to its database, the key that lets it charge customers through a payment processor, the key to an AI service. Railway, like most hosting platforms, stores those as “environment variables” — think of them as the keys on an app’s key ring. Railway said they were encrypted. What makes this incident unusual is that the company said the attacker may have obtained the decrypted contents for some of them, which means the keys themselves, not scrambled copies.

The fallout was visible within hours. Nevo David, founder of the social media scheduling service Postiz, posted on X that he was shutting Postiz down for all customers after receiving emails from Anthropic and Stripe that his company’s keys had been compromised. Other developers on X and Hacker News reported their AI keys being drained in real time. Those are individual reports, not findings from Railway.

What “Attacks on AI Inference Providers” Means

Railway said it believes the incident is “part of a series of attacks recently targeting platform companies with the aim of compromising AI inference providers,” and that it asked those providers to revoke keys.

AI inference providers are the companies that run AI models and bill by usage — OpenAI, Anthropic, xAI’s Grok and OpenRouter among them. Each customer gets an API key, and every request made with that key is charged to the customer’s account. A stolen key is, in effect, a stolen credit card for AI computing: an attacker can run expensive models and stick the owner with the bill, or resell access. Security researchers call this “LLMjacking.” Railway’s own follow-up guides tell customers to check for unexpected usage on OpenAI, Anthropic, Grok, OpenRouter and Stripe accounts.

A Railway employee wrote on Hacker News that preliminary forensics indicate AI credentials were the attacker’s “primary goal,” and called it the work of “a highly motivated attacker.” Railway has not named who was behind it, and nothing public shows whether the “series of attacks” is one coordinated group or several. Days earlier, the AI coding tool OpenCode disclosed that attackers had reached a legacy system on October 16 that stored customers’ OpenAI, Anthropic and Google keys, affecting 1.4% of its console users, according to The National CIO Review. OpenCode tied that incident to a suspected large-scale AI “distillation” effort — using stolen access to copy what a model knows — but has not explained the connection.

The Same Week: PHP and Node.js Rush Out Critical Fixes

The Railway incident landed on the same day as emergency security releases for two of the building blocks of the web. They are separate events with no reported connection to Railway, but together they made October 21 a bad day for the software most websites run on.

PHP2Shell

PHP is the programming language behind about 69% of websites whose server-side language is known, according to W3Techs, including sites built on WordPress, Drupal, Joomla and Magento. On October 20, details of two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, nicknamed “PHP2Shell,” leaked in a Hacker News post before patches were ready, Infosecurity Magazine reported. The PHP team rated them 9.2 out of 10 and shipped fixes on October 21, a day ahead of schedule: versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

In plain terms, the flaws can let an attacker take over a web server by sending it a specially crafted request. Security firm Huntress said PHP considers all installations that serve web requests at risk, and that researchers at Wiz reported both a way to take over WordPress, Drupal and Joomla sites without logging in and a separate flaw that could expose passwords, tokens and API keys from server memory. Older, unsupported PHP versions are unlikely to get official patches. Huntress said it had not seen attacks on its own customers’ systems as of the afternoon of October 21, while noting other researchers’ reports of attacks emerging. The UK’s National Cyber Security Centre and CERT-EU issued emergency advisories.

Node.js

Node.js, the system that runs JavaScript on servers for a huge share of modern web apps, also issued security releases on October 21 fixing 10 vulnerabilities, four of them rated high. The most serious, CVE-2026-111497, is a flaw in how Node.js decompresses data that the project said can permit remote code execution. The update also blocks certificates from eMudhra, a certificate authority that suffered an intermediate-certificate compromise, so that Node.js apps stop trusting them. Fixed versions are 22.23.4, 24.22.1 and 26.12.1.

What This Means for Regular Internet Users

Railway’s customers are developers and businesses, not the general public, and Railway has not said that consumers’ personal information was taken. But many of the apps people use every day run on platforms like Railway, and the exposed secrets included database passwords. Whether an app’s own users are affected depends on whether an attacker used those passwords to reach an app’s data, which neither Railway nor its customers had publicly reported as of October 22, 2026.

The more direct pattern is financial. Stolen AI and payment-processor keys are charged to the businesses that own them, and some of those businesses — like Postiz — took their services offline while they replaced their keys. If an app or service someone uses goes down unexpectedly or sends a security notice in the coming days, this incident may be the reason.

A data breach notice from a specific app would be the point at which consumers’ own data is confirmed to be involved. If that happens, OCA will update this page.

What Happens Next

Railway said it will contact affected customers directly by email, post updates on its status page, and publish a formal postmortem after it restores service and completes its investigation. As of its latest status update on October 22, 2026, builds were still paused. Railway has also published step-by-step guides for customers on replacing database credentials and checking AI, cloud, GitHub and Stripe accounts for misuse. OCA had not found any lawsuit over the incident as of October 22, 2026, and there is nothing to claim.

Questions

What is Railway?

Railway is a cloud platform that lets software developers put websites, apps and databases online without managing their own servers. In January 2026, when it announced a $100 million Series B funding round, Railway said more than 2 million developers and tens of thousands of companies, from small shops to Fortune 500 firms, build on it.

What was exposed in the Railway hack?

Railway said an unauthorized third party may have accessed encrypted environment variables, the settings where apps keep their passwords and secret keys, and for some of them obtained the decrypted contents. Those can include API keys, database credentials and private registry credentials. Railway said the impact may be limited to a subset of users and has not said how many accounts were affected.

What does Railway mean by attacks on AI inference providers?

AI inference providers are companies such as OpenAI, Anthropic and OpenRouter that run AI models and bill by usage through API keys. Railway said it believes the incident is part of a series of attacks on platform companies aimed at compromising those providers, and a Railway employee said publicly that stealing AI credentials appeared to be the attacker’s primary goal. A stolen AI key lets an attacker run expensive AI requests that are billed to the key’s owner.

Was my personal information exposed in the Railway breach?

Railway has not said that consumers’ personal information was taken. The exposed data was secrets belonging to Railway’s customers, the developers and companies that run apps on it. Because some of those secrets were database passwords, the risk to an app’s own users depends on whether an attacker used them, which Railway and its customers had not publicly reported as of October 22, 2026.

Is there a Railway class action lawsuit?

OpenClassActions.com had not found a lawsuit over the Railway incident as of October 22, 2026, and there is no settlement or claim form. Railway has said it will publish a formal postmortem after its investigation.



Sources

• Railway — Security Disclosure: Wednesday October 21st (October 21, 2026)
• Railway status page — platform incident updates (October 21–22, 2026)
• Jake Cooper, Railway CEO — post on X (October 21, 2026)
• Hacker News — discussion thread, including comments from a Railway employee (October 21–22, 2026)
• Nevo David, Postiz — post on X (October 21, 2026)
• Railway — Series B announcement (January 22, 2026)
• The National CIO Review — OpenCode Breach Puts Customer AI API Keys at Risk (October 19, 2026)
• Infosecurity Magazine — Critical PHP Vulnerabilities Leaked Ahead of Scheduled Security Patch (October 21, 2026)
• Huntress — Rapid Response: php2shell (October 21, 2026)
• W3Techs — Usage statistics of PHP for websites (accessed October 22, 2026)
• Node.js — Wednesday, October 21, 2026 Security Releases

For more class actions keep scrolling below.
Status Under investigation — no lawsuit or settlement
Company Railway Corp.
Disclosed October 21, 2026
Data Involved Customer environment variables (API keys, database and registry credentials)
Accounts Affected Not disclosed
Official Website Railway Security Disclosure

More Data Breach Coverage