railway

58,906 views
8 Discussing
WEB3韭菜小凯
·
--
Article
96 wallets drained in 70 minutes early this morning; suspicion again falls on RailwayEarly this morning, another batch of hot wallets was drained. Carlos, growth lead at on-chain trading platform Definitive, posted that one of his old hot wallets was emptied in the middle of the night. All the transfers were signed by his own wallet, indicating that the seed phrase or private key had been exposed. He counted 96 wallets drained using the same method in 70 minutes. The attacker used an address called noble.base.eth, and most of the funds were withdrawn via Relay, which subsequently froze the wallets involved. Suspicion has fallen on Railway. On October 21, Railway admitted that someone had gained unauthorized access to a system storing customers’ environment variables, and that some of them had been decrypted and taken in plain text. That same evening, people noticed that wallets whose private keys had been stored with Railway were starting to lose funds. Security researcher Taylor Monahan counted more than 200 addresses across 19 chains, with losses of about $371,000—a figure Railway itself has not confirmed. I wrote about that wave on October 22 and thought it was over once the keys had been changed. The 96 wallets drained early this morning show that those leaked keys are still being tried, one by one.

96 wallets drained in 70 minutes early this morning; suspicion again falls on Railway

Early this morning, another batch of hot wallets was drained. Carlos, growth lead at on-chain trading platform Definitive, posted that one of his old hot wallets was emptied in the middle of the night. All the transfers were signed by his own wallet, indicating that the seed phrase or private key had been exposed. He counted 96 wallets drained using the same method in 70 minutes. The attacker used an address called noble.base.eth, and most of the funds were withdrawn via Relay, which subsequently froze the wallets involved.
Suspicion has fallen on Railway. On October 21, Railway admitted that someone had gained unauthorized access to a system storing customers’ environment variables, and that some of them had been decrypted and taken in plain text. That same evening, people noticed that wallets whose private keys had been stored with Railway were starting to lose funds. Security researcher Taylor Monahan counted more than 200 addresses across 19 chains, with losses of about $371,000—a figure Railway itself has not confirmed. I wrote about that wave on October 22 and thought it was over once the keys had been changed. The 96 wallets drained early this morning show that those leaked keys are still being tried, one by one.
Yesterday’s biggest crypto hack story had absolutely nothing to do with an exchange. The victim was Railway, a cloud platform that helps developers deploy applications and claims to have 2 million developers using it. On the morning of October 21, Railway discovered an issue with the system that stores users’ environment variables, and soon after, paused builds and deployments across the entire platform. What are environment variables? Basically, they’re secret settings an app needs to run: API keys, database passwords, credentials for image registries—and, because it’s convenient, plenty of people put their private keys in there too. The company’s wording was measured: an unauthorized third party may have accessed encrypted environment variables, and some of them may have obtained the decrypted contents. You can read between the lines. The incident was really confirmed when security researcher Taylor Monahan got involved. She traced it to a hacker’s address, 0xd9773325282874d18cb83f1fe50f14c39750b2ee. The first theft transaction took place at 19:36 UTC on October 21. After that, more than 500 transactions swept across over 200 addresses on 19 EVM chains, using an off-the-shelf sweeper script. Estimated losses: $371,000. The timeline she shared is pretty telling: the platform paused builds in the morning, but the theft transactions didn’t show up until the evening. She called the silence in between “a lawyer’s nightmare.” First, let’s be clear about the data gap: $371,000 is her personal estimate based on on-chain data, and Railway hasn’t independently confirmed it. What does this have to do with us retail investors? First, losing your crypto doesn’t necessarily mean there was a smart contract bug or that you clicked a phishing link. Something can go wrong somewhere you weren’t even involved. Lots of people use cloud platforms to run trading bots or node monitors, with their private keys and exchange API keys sitting in environment variables. If the platform gets hacked, it’s as if your wallet got hacked. And if someone gets your exchange key, they can withdraw your funds directly. Does that mean you’re safe if you don’t run a bot? Not necessarily. The exchange API keys you’ve authorized copy-trading software, quant tools, or asset management apps to use are sitting on their platforms too. Same principle. Second, a cloud platform is not a safe. Once your private key is in the cloud, it becomes the platform’s private key—you can only hope the platform’s operations team doesn’t have a security incident. My personal takeaway is simple: if you’re running a bot, use a local machine or a server you manage yourself whenever possible. If you really have to use the cloud, disable withdrawal permissions on your exchange API key and leave trading permissions enabled. Railway also added a rather suggestive line, saying this incident may be part of a series of attacks targeting AI inference providers. With the AI boom, even hackers have their eyes on it. Have you ever authorized a third-party tool to use your exchange API? Be honest in the comments. #Railway #被黑事件 #私钥安全 #交易机器人 #web3 security —— Web3 Degenerate Xiaokai Disclaimer: These are personal opinions and do not constitute investment advice.
Yesterday’s biggest crypto hack story had absolutely nothing to do with an exchange. The victim was Railway, a cloud platform that helps developers deploy applications and claims to have 2 million developers using it.

On the morning of October 21, Railway discovered an issue with the system that stores users’ environment variables, and soon after, paused builds and deployments across the entire platform. What are environment variables? Basically, they’re secret settings an app needs to run: API keys, database passwords, credentials for image registries—and, because it’s convenient, plenty of people put their private keys in there too. The company’s wording was measured: an unauthorized third party may have accessed encrypted environment variables, and some of them may have obtained the decrypted contents. You can read between the lines.

The incident was really confirmed when security researcher Taylor Monahan got involved. She traced it to a hacker’s address, 0xd9773325282874d18cb83f1fe50f14c39750b2ee. The first theft transaction took place at 19:36 UTC on October 21. After that, more than 500 transactions swept across over 200 addresses on 19 EVM chains, using an off-the-shelf sweeper script. Estimated losses: $371,000. The timeline she shared is pretty telling: the platform paused builds in the morning, but the theft transactions didn’t show up until the evening. She called the silence in between “a lawyer’s nightmare.” First, let’s be clear about the data gap: $371,000 is her personal estimate based on on-chain data, and Railway hasn’t independently confirmed it.

What does this have to do with us retail investors? First, losing your crypto doesn’t necessarily mean there was a smart contract bug or that you clicked a phishing link. Something can go wrong somewhere you weren’t even involved. Lots of people use cloud platforms to run trading bots or node monitors, with their private keys and exchange API keys sitting in environment variables. If the platform gets hacked, it’s as if your wallet got hacked. And if someone gets your exchange key, they can withdraw your funds directly. Does that mean you’re safe if you don’t run a bot? Not necessarily. The exchange API keys you’ve authorized copy-trading software, quant tools, or asset management apps to use are sitting on their platforms too. Same principle. Second, a cloud platform is not a safe. Once your private key is in the cloud, it becomes the platform’s private key—you can only hope the platform’s operations team doesn’t have a security incident.

My personal takeaway is simple: if you’re running a bot, use a local machine or a server you manage yourself whenever possible. If you really have to use the cloud, disable withdrawal permissions on your exchange API key and leave trading permissions enabled. Railway also added a rather suggestive line, saying this incident may be part of a series of attacks targeting AI inference providers. With the AI boom, even hackers have their eyes on it.

Have you ever authorized a third-party tool to use your exchange API? Be honest in the comments.

#Railway #被黑事件 #私钥安全 #交易机器人 #web3 security

—— Web3 Degenerate Xiaokai
Disclaimer: These are personal opinions and do not constitute investment advice.
【Market Flash】$370,000 is gone—the Railway key leak is no longer just a warning. A developer says keys stored on Railway were exploited, resulting in $370,000 being stolen. On-chain records show a large transfer to an address flagged by investigators. The platform restored Enterprise builds Wednesday night, but customers on other plans are still waiting to redeploy with replacement credentials. Entrusting a platform with your keys concentrates the risk on that platform. Would you keep using hosted key management or move back to self-custody? Share your thoughts in the comments. $BTC $ETH $SOL #Railway #网络安全 #KeySecurity (Source: The Defiant) ⚠️Risk warning: The above is shared for market information only and does not constitute investment advice. Investing involves risks; please proceed with caution.
【Market Flash】$370,000 is gone—the Railway key leak is no longer just a warning. A developer says keys stored on Railway were exploited, resulting in $370,000 being stolen. On-chain records show a large transfer to an address flagged by investigators. The platform restored Enterprise builds Wednesday night, but customers on other plans are still waiting to redeploy with replacement credentials. Entrusting a platform with your keys concentrates the risk on that platform. Would you keep using hosted key management or move back to self-custody? Share your thoughts in the comments.
$BTC $ETH $SOL
#Railway #网络安全 #KeySecurity
(Source: The Defiant)
⚠️Risk warning: The above is shared for market information only and does not constitute investment advice. Investing involves risks; please proceed with caution.
Another theft. In about 70 minutes, 96 wallets were drained one after another. Even stranger, the transfers didn’t exploit an authorization vulnerability—the victims’ “own wallets” signed them. Carlos, Head of Growth at Definitive, said his old hot wallet was drained early this morning. The attack may have come from “noble.base.eth,” and the targeted wallets all followed the exact same pattern. He believes the private keys or seed phrases themselves were leaked. He suspects the keys leaked from Railway. On 10/21, the cloud deployment platform announced that someone may have accessed customers’ encrypted environment variables. Some people, for convenience, may have put their private keys directly in them. Taylor Monahan traced the first theft to 10/21 at 19:36 UTC—earlier than Railway’s public notice. An estimated $371,000 was swept away across at least 19 EVM chains. To be clear, the link to Railway is only Carlos’s suspicion; Railway has not confirmed it, and the $371,000 figure is also unconfirmed. If your private key or seed phrase has ever been stored on a cloud platform, in a .env file, or in a bot configuration, don’t wait for an official conclusion. Create a new wallet and move your assets now. When was the last time you checked your old hot wallet? #Railway #Definitive #私钥泄露 #热钱包 #OnchainSecurity
Another theft. In about 70 minutes, 96 wallets were drained one after another.

Even stranger, the transfers didn’t exploit an authorization vulnerability—the victims’ “own wallets” signed them. Carlos, Head of Growth at Definitive, said his old hot wallet was drained early this morning. The attack may have come from “noble.base.eth,” and the targeted wallets all followed the exact same pattern. He believes the private keys or seed phrases themselves were leaked.

He suspects the keys leaked from Railway. On 10/21, the cloud deployment platform announced that someone may have accessed customers’ encrypted environment variables. Some people, for convenience, may have put their private keys directly in them.

Taylor Monahan traced the first theft to 10/21 at 19:36 UTC—earlier than Railway’s public notice. An estimated $371,000 was swept away across at least 19 EVM chains.

To be clear, the link to Railway is only Carlos’s suspicion; Railway has not confirmed it, and the $371,000 figure is also unconfirmed.

If your private key or seed phrase has ever been stored on a cloud platform, in a .env file, or in a bot configuration, don’t wait for an official conclusion. Create a new wallet and move your assets now.

When was the last time you checked your old hot wallet?

#Railway #Definitive #私钥泄露 #热钱包 #OnchainSecurity
🚄 BREAKING: CHINA-LAOS RAILWAY SURPASSES 80 MILLION PASSENGERS! 🌏 The China-Laos Railway has recorded over 80 million passenger journeys in nearly five years of full-line operation, according to Jin10. 📈 Daily passenger trains on the Chinese section have increased from 8 to a peak of 86, while the Laos section has grown from 4 to 18. 🌏 This milestone highlights rising travel demand, stronger cross-border connectivity, and growing opportunities for tourism and economic cooperation between China and Laos. 🔥 A major achievement for regional infrastructure and Southeast Asian connectivity! #China #Laos #Railway #Infrastructure #Tourism
🚄 BREAKING: CHINA-LAOS RAILWAY SURPASSES 80 MILLION PASSENGERS! 🌏

The China-Laos Railway has recorded over 80 million passenger journeys in nearly five years of full-line operation, according to Jin10.

📈 Daily passenger trains on the Chinese section have increased from 8 to a peak of 86, while the Laos section has grown from 4 to 18.

🌏 This milestone highlights rising travel demand, stronger cross-border connectivity, and growing opportunities for tourism and economic cooperation between China and Laos.

🔥 A major achievement for regional infrastructure and Southeast Asian connectivity!

#China #Laos #Railway #Infrastructure #Tourism
Log in to explore more content
Join global crypto users on Binance Square
⚡️ Get latest and useful information about crypto.
💬 Trusted by the world’s largest crypto exchange.
👍 Discover real insights from verified creators.
Email / Phone number