Act this weekWhat happenedRailway found unusual activity in systems that store customers' environment variables and says an unauthorized party may have accessed them.
Who is affectedBusinesses and developers who host apps or websites on Railway, especially those who keep passwords or access keys in its settings.
What to do- 1Log in to Railway and read the company's security notice.
- 2List every password, key and token stored in your Railway settings.
- 3Replace each one with a new value, starting with the most sensitive.
- 4Check the accounts those keys unlock for activity you do not recognize.
Railway, a company that hosts apps and websites for other businesses, said on Wednesday that an unauthorized person may have gotten into the place where customers keep their private settings. Some of that data was scrambled to protect it. The company says that in some cases the intruder got the readable version.
What happened
Railway noticed what it called "anomalous activity" in systems that store customer environment variables. These are private settings an app needs to run, such as passwords, access keys for other services, and database logins. They are kept outside the app's code so they stay hidden. Railway says the impact is limited to a "subset of users" but has not said how many.
Why it matters
A stolen key works like a stolen house key. Whoever holds it can use the service it unlocks. Security researcher Taylor Monahan says the attackers have already drained cryptocurrency wallets whose private keys were stored on Railway. She says the first known theft happened at least two hours before Railway announced the problem.
Railway says the incident looks like part of a series of attacks on platform companies, with the end goal of compromising AI inference providers. Those are services that run AI models. Railway has told upstream providers to revoke keys so they cannot be abused.
Who is affected
The notice matters to businesses and developers who host on Railway, especially those who keep passwords or access keys in its settings. If you do not use Railway, this notice does not concern you directly. If you do, the company has not said how to tell whether you are in the affected group. Treating every stored secret as exposed is the safer assumption.
What to do
The alert box above lists the steps. The short version is to replace everything stored in Railway, most sensitive first, and then look at the accounts those keys unlock for anything unfamiliar. Railway has already rotated its own bucket credentials and canceled its API tokens, so customers still need to handle their own secrets.
What is still unknown
Railway has not said how many customers were hit or whether stolen AI keys were abused. Symantec's Dick O'Brien said his team found no evidence linking Railway to the AI key theft it has been tracking. He noted that such keys are valuable because anyone holding one can run AI work at the owner's expense.
Service is also still recovering. Builds work again for Pro and Enterprise workspaces. Railway is still working on Hobby, then Free and Trial. Some builds fail more often than usual, and many deployments are waiting in line.
The takeawayIf your app runs on Railway, replace every password and key stored there now, then check the connected accounts for activity you do not recognize.