After Railway credential leak, Every used Codex to triage exposed keys
danshipper · x · 2026-11-01
Railway disclosed last week that hackers may have obtained decrypted API keys, database passwords, and other credentials customers stored on its platform. Every, a Railway customer, had to identify exposed credentials, figure out which apps depended on them, and coordinate replacements.
- A team member used Codex to build a shared list of every password and API key Every had stored on Railway, with a likely owner for each.
- The Every Agent reported hourly how many keys still needed investigation or replacement, turning a potentially chaotic incident into a trackable workflow.
- "This incident would have been insane for us without AI," the team member said.
A concrete example of AI agents applied to real-world security incident response.
Related event: Every Uses Codex to Rotate Credentials After Railway Breach(2 posts)→
More from coding & agent
- Agents playtested his game Slop Eisley, driving the 0.6.77 pathfinding fix — jasonkneen · 2026-11-02
- One line in your system prompt is silently killing your prompt cache hits — Arindam_1729 · 2026-11-02
- mitsuhiko on Python JIT: agents could crack it, the blocker is grind not humans — mitsuhiko · 2026-11-02
- 13 Claude agents replaced a $300K marketing department, driving 52.4M views — aryanXmahajan · 2026-11-02
- Engineer ports entire Python codebase to Go with AI in just days — dosco · 2026-11-02
- Databricks engineer's outsider take on Anthropic's Scion: 7 people, 5 months, borrowed ideas — ricklamers · 2026-11-02