Skip to main content
Railway urges credential resets as investigator alleges $371,000 crypto theft

Railway urges credential resets as investigator alleges $371,000 crypto theft

CryptoSlate
Oct 22, 2026, 08:35 PMCryptoslate
Oryginał
2 min read

Railway warned customer environment variables may have been decrypted and urged every user to replace stored secrets after an on-chain investigator alleged roughly $371,000 in stolen crypto across at least 19 EVM chains.

Railway, a cloud deployment platform, has urged every user to replace stored secrets after disclosing on Oct. 21 that an attacker may have accessed encrypted customer environment variables and read some of their contents. The company said those variables may contain API keys, database credentials and private registry credentials.

Although its initial analysis suggested the impact might be limited to a subset of users, Railway's security disclosure urged all customers to replace stored variables and credentials immediately and review service logs for unusual activity.

Crypto theft allegation

On-chain investigator @tayvano_ separately alleged cryptocurrency theft involving keys stored in Railway. The investigator estimated losses of roughly $371,000 across at least 19 EVM chains and identified an address as belonging to the attacker.

roughly $371,000 drained across at least 19 EVM chains

@tayvano_, on-chain investigator

Railway has not confirmed the alleged theft, its connection to the incident or the $371,000 estimate. The company believes the incident is part of a series of attacks against platform companies aimed at compromising AI inference providers.

Platform response

Railway invalidated its API tokens and restored builds for Pro and Enterprise customers, while lower tiers awaited access. The company initially paused all deployments while investigating, preventing customers from rolling out new versions of their applications.

At 04:17 UTC on Oct. 22, Railway said it had invalidated all Railway API tokens. Customers using those tokens to integrate with its public API were told to create replacements. By 12:30 UTC, deployment wait times were improving and most queued deployments were starting sooner.

Railway said it would email affected customers as accounts were confirmed. For crypto teams running applications on Railway, the practical response is to review which credentials those applications stored on the platform and the services those credentials can access.

Z.ai
Article written by AI
Z.ai GLM-4.5-FlashFree
Free AI articles150 of 150
No limit after signing in with Telegram