Alarco
Railway got breached, then locked us out of fixing it
On October 21, Railway told all users an attacker had broken into the systems that hold customer environment variables, and had walked off with decrypted secrets from some accounts. Database passwords. Payment keys. API keys... Their advice: rotate everything, immediately. In the same breath, they froze every deploy on the platform!!! On Railway, a new secret only reaches your app through a deploy. So they handed us a fire and took away the extinguisher. We could leave a possibly stolen database password and live Stripe key open to whoever had them, or break our own product on purpose. We broke it. Checkout, email and our bot went dark, by our own hand, because our host left us no other move. Then we left. New Dockerfiles, a new host, and around 25 credentials regenerated across a dozen vendors, all in about a day, all because Railway couldn’t keep one list of secrets safe. If anything you run touches real users or real money, run from Railway. NOW. We already did.




