Skip to content
Free checklist for cleaning up after the Oct 21 incident
drgibbs11
OP

23 days ago

I put together a checklist for cleaning up after the Oct 21 incident. It's free and MIT licensed: https://github.com/mausoftskills/railway-post-breach-checklist

It covers, in order:

  1. Crypto wallets first. A private key can't be rotated, so stop the service, check for a sweeper before sending any gas, and move funds to a wallet made on a clean device.
  2. A names-only inventory of your variables, read from the Variables tab rather than the Raw Editor.
  3. Rotation in priority order: new key live before the old one is revoked, Regenerate for Railway-hosted databases (no manual password edits or SQL), and a new shared variable instead of editing a shared one, so every service doesn't redeploy at once.
  4. Deployments, audit log, provider usage and buckets during the incident window (Oct 20, 13:58 UTC to Oct 22, 03:32 UTC). Pro audit logs keep 30 days, so that window ages out around Nov 19-21.
  5. An access review (Railway tokens, members, SSH keys, GitHub) and a short written record.

It's written as a skill for AI coding agents (SKILL.md), but it reads fine as a plain checklist. The agent never handles secret values; you paste new keys yourself and approve each change.

It's a checklist, not a guarantee, and I'm not affiliated with Railway. Corrections welcome.

0 Replies

Status changed to Awaiting Railway Response Railway • 23 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...