<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/the-pulse-what-can-we-learn-from-the-railway-hack--fmvq2vwa0" -->

---
title: The Pulse: What can we learn from the Railway hack?
description: Railway published a detailed postmortem of a hack in which an attacker, likely using an abliterated AI model with no safety restrictions, escalated from a...
canonical: https://daily.dev/posts/the-pulse-what-can-we-learn-from-the-railway-hack--fmvq2vwa0
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: The Pulse: What can we learn from the Railway hack? | daily.dev
og:description: Railway published a detailed postmortem of a hack in which an attacker, likely using an abliterated AI model with no safety restrictions, escalated from a...
og:url: https://daily.dev/posts/the-pulse-what-can-we-learn-from-the-railway-hack--fmvq2vwa0
og:image: https://api.daily.dev/og/posts/FMVq2VWa0.png
og:image:alt: The Pulse: What can we learn from the Railway hack?
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# The Pulse: What can we learn from the Railway hack?

**[The Pragmatic Engineer](https://daily.dev/sources/pragmaticengineer)** · 12 min read · 0 upvotes · 0 comments

## Summary

Railway published a detailed postmortem of a hack in which an attacker, likely using an abliterated AI model with no safety restrictions, escalated from a build-system vulnerability to stealing customer AI provider keys in under 24 hours. The attacker moved through four phases: failed exploit attempts, stealing the monorepo via a Temporal cluster in 11 hours, gaining SSH access by exploiting a misconfigured OpenID Connect binding in 10 hours, then decrypting customer AI keys in 3 hours. Railway revoked stolen credentials within a minute of detecting misuse and sent key hashes to AI providers so they could be revoked without exposing secrets. Railway rebuilt its build system to use per-build throwaway VMs and added fine-grained access control. Nine days later, competitor Northflank, which had published a post urging customers to migrate off Railway after the breach, suffered a near-identical hack but took 9 hours to detect it and 11 hours to notify customers.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blog.pragmaticengineer.com/the-pulse-what-can-we-learn-from-the-railway-hack>

## Questions this post answers

### How did the attacker in the Railway hack gain access to customer AI provider keys?

The attacker first exploited a vulnerability to read files on Railway's build system and stole build credentials, then used those to access a Temporal cluster storing build histories and downloaded Railway's monorepo. From there they exploited a misconfigured OpenID Connect binding in the deploy pipeline to get a cloud credential, pulled a long-lived credential and SSH key, then queried the production database and called Railway's key management service to decrypt customer AI provider keys stored as encrypted environment variables.

_Teams hardening build pipelines against credential theft can follow breakdowns like this on daily.dev._

### Why are AI model keys a popular target for hackers attacking infrastructure providers?

Attackers, reportedly using abliterated AI models with no safety restrictions, specifically target AI provider keys because compromising an infra company can expose thousands of keys at once, which can then be sold at discounted rates. These offensive models work relentlessly and far faster than a human attacker, reportedly going from stolen source code to a working exploitation plan within about six hours.

_Anyone weighing how to protect AI provider keys in their stack can track incidents like this on daily.dev._

### What did Railway change about its build system after its security incident?

Railway moved every customer to a new, previously unreleased build system rather than patching the compromised one, giving each build its own throwaway virtual machine instead of a shared machine with a sandbox boundary. It also added fine-grained access control requiring 2FA and biometrics for sensitive credentials, and decommissioned old unused systems that the attacker had probed.

_Engineers redesigning build infrastructure for stronger isolation can follow cases like this on daily.dev._

## Similar posts on daily.dev

- [Preliminary Report: Oct 21st Security Incident](https://daily.dev/posts/preliminary-report-oct-21st-security-incident-9lrevx8xo) · Railway Blog · 0 upvotes · 0 comments
- [The Pulse: Time to rethink software security because of AI?](https://daily.dev/posts/the-pulse-time-to-rethink-software-security-because-of-ai--gu0kj0fef) · The Pragmatic Engineer · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#cyber](https://daily.dev/tags/cyber), [#ai-security](https://daily.dev/tags/ai-security)

[View this post on daily.dev](https://daily.dev/posts/the-pulse-what-can-we-learn-from-the-railway-hack--fmvq2vwa0)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"The Pulse: What can we learn from the Railway hack?","url":"https://daily.dev/posts/the-pulse-what-can-we-learn-from-the-railway-hack--fmvq2vwa0","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-pulse-what-can-we-learn-from-the-railway-hack--fmvq2vwa0"},"datePublished":"2026-11-19T18:58:52.653Z","dateModified":"2026-11-19T19:07:52.544Z","description":"Railway published a detailed postmortem of a hack in which an attacker, likely using an abliterated AI model with no safety restrictions, escalated from a...","image":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","thumbnailUrl":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","isAccessibleForFree":true,"articleSection":"The Pragmatic Engineer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"The Pragmatic Engineer","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/b3ccb8a149434269bda040722d941474","url":"https://daily.dev/sources/pragmaticengineer"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-pulse-what-can-we-learn-from-the-railway-hack--fmvq2vwa0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,cyber,ai-security","timeRequired":"PT12M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"The Pragmatic Engineer","item":"https://daily.dev/sources/pragmaticengineer"},{"@type":"ListItem","position":3,"name":"The Pulse: What can we learn from the Railway hack?"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-pulse-what-can-we-learn-from-the-railway-hack--fmvq2vwa0#faq","mainEntity":[{"@type":"Question","name":"How did the attacker in the Railway hack gain access to customer AI provider keys?","acceptedAnswer":{"@type":"Answer","text":"The attacker first exploited a vulnerability to read files on Railway's build system and stole build credentials, then used those to access a Temporal cluster storing build histories and downloaded Railway's monorepo. From there they exploited a misconfigured OpenID Connect binding in the deploy pipeline to get a cloud credential, pulled a long-lived credential and SSH key, then queried the production database and called Railway's key management service to decrypt customer AI provider keys stored as encrypted environment variables. Teams hardening build pipelines against credential theft can follow breakdowns like this on daily.dev."}},{"@type":"Question","name":"Why are AI model keys a popular target for hackers attacking infrastructure providers?","acceptedAnswer":{"@type":"Answer","text":"Attackers, reportedly using abliterated AI models with no safety restrictions, specifically target AI provider keys because compromising an infra company can expose thousands of keys at once, which can then be sold at discounted rates. These offensive models work relentlessly and far faster than a human attacker, reportedly going from stolen source code to a working exploitation plan within about six hours. Anyone weighing how to protect AI provider keys in their stack can track incidents like this on daily.dev."}},{"@type":"Question","name":"What did Railway change about its build system after its security incident?","acceptedAnswer":{"@type":"Answer","text":"Railway moved every customer to a new, previously unreleased build system rather than patching the compromised one, giving each build its own throwaway virtual machine instead of a shared machine with a sandbox boundary. It also added fine-grained access control requiring 2FA and biometrics for sensitive credentials, and decommissioned old unused systems that the attacker had probed. Engineers redesigning build infrastructure for stronger isolation can follow cases like this on daily.dev."}}]}
```

