Strategy

    Treat your AI key like a card number: lessons from the Railway breach

    Stolen AI keys ran up an estimated $740,000 after the Railway breach. Here are four calm checks for any business that uses AI through a tool or plugin.

    By Juno

    ·

    12 November 2026

    ·4 min read

    If your business uses AI through an automation or a chatbot on your website, it's worth asking whether there's an AI API key behind it. Often there is. That key is how the tool pays for the AI it uses, and the bill comes to you.

    A report published on 10 November 2026 by Railway shows why that matters.

    The short answer: Railway's 10 November 2026 report says an October attack targeted AI provider keys in customer projects. At most 1.85% of workspaces, about 100,000, could have had stored variables decrypted. Unauthorised spending on the stolen keys was estimated to reach about $740,000. Railway is working with providers on refunds and will cover costs where they won't.

    What happened in the Railway breach?

    Railway is a cloud hosting company used by developers. In October it was attacked, and on 10 November it published a full incident report.

    Railway says that, based on its forensic investigation, the attacker was specifically targeting AI provider credentials. Its report says the attacker queried variable names for AI provider keys. Variables here are the stored settings a project uses for things like passwords and keys. Railway says that, from the logging available to it, at most 1.85% of workspaces, about 100,000, could have had any of their environment variables decrypted. It describes that as an upper bound, not a confirmed count.

    The cost is the part that stands out. Railway says unauthorised spending on the stolen keys was estimated to reach about $740,000. It's working with the AI providers on refunds, and says it will cover the costs itself where a provider won't.

    On motive, Railway says it believes the attacker was targeting AI provider credentials "that they could sell to distributed transfer stations for use in distillation". It also says the later misuse is consistent with keys being passed through services that relay or resell access to AI providers, but that it hasn't established whether the original attacker ran those services or supplied keys to others.

    Railway says several other companies, including OpenCode and Warp, disclosed similar thefts in October. It describes its own incident as one of a series of attacks on platforms that hold AI keys.

    Why does this matter if you don't use Railway?

    You probably don't host anything on Railway. But in my view the lesson isn't about one company. A stolen AI key behaves a lot like a stolen card number: whoever has it can spend on your account until someone notices. Railway says the misuse it saw ranged from coding agents to AI training pipelines. If you want a plain explanation of where these keys tend to sit, I've covered what an AI agent actually does.

    What should you check this week?

    These four checks are my own advice, not Railway's recommendations, though the last one follows something Railway asked of its customers.

    Can you put a ceiling on the bill?

    Log into each AI provider you pay for and see whether it lets you set a monthly budget or usage limit. If it does, set one comfortably above your normal spend but well below a figure that would hurt. A limit won't stop a key being stolen, but it can cap the damage before you notice.

    Does each tool have its own key?

    If the same key is pasted into your website chatbot and every one of your automations, one leak exposes all of them, and you can't easily tell which one leaked. A separate key for each tool means you can switch one off without breaking everything else, and your usage records show which tool is spending what.

    Do you know how to switch a key off quickly?

    Find out now where your keys live and who can revoke them. If you had to switch one off tonight, would you know where to go? If a developer or agency set things up for you, ask them to show you or write it down. Railway asked AI providers to revoke potentially exposed keys during its incident, but the people best placed to act fast on your account are you and whoever looks after your setup.

    Are you looking at the bill?

    Railway asked customers to report any charges they didn't make. That only works if someone is reading the bill. Put a monthly reminder in your calendar to glance at your AI usage. A sudden jump could be the first sign something's wrong.

    What does this mean for your business?

    None of this needs technical skill or new software. It's mostly knowing where your keys are and who can switch them off.

    Keeping keys separate by tool is how I'd want any of my AI automations set up, so one problem doesn't take everything down. If you're not sure what's connected to your AI accounts, or who set it up, I'm happy to go through it with you. You can book a call with Tom.

    Sources

    Frequently asked questions

    What happened in the Railway breach?

    Railway is a cloud hosting company used by developers. It says it was attacked in October and published a full incident report on 10 November 2026. Railway says that, based on its investigation, the attacker was specifically targeting AI provider keys stored in customer projects.

    How many workspaces could have been affected?

    Railway says that at most 1.85% of workspaces, about 100,000, could have had any of their environment variables decrypted. It describes that as an upper bound, not a confirmed count.

    How much unauthorised spending did Railway estimate?

    Railway says unauthorised spending on the stolen keys was estimated to reach about $740,000. It says it's working with the AI providers on refunds, and will cover the costs itself where a provider won't.

    What else did Railway say about the attack?

    Railway says several other companies, including OpenCode and Warp, disclosed similar thefts in October. It describes its own incident as one of a series of attacks on platforms that hold AI keys. It also says the misuse it saw ranged from coding agents to AI training pipelines.

    What did Railway ask customers to do about charges?

    Railway asked customers to report charges they didn't make. During the incident it also asked AI providers to revoke potentially exposed keys.

    Now taking on new clients

    Ready to never lose another customer?

    Book a 15-minute call. No pitch. If it's a fit, you're live in 14 days.

    Book a free call