Security notice: Railway incident, 21 October 2026
Antifield's hosting provider, Railway, has disclosed unauthorised access to the systems that store app configuration. What that means for skowt.cc, Etcht and Antifield's other services, and what's being done about it.
Last updated: 22 October 2026, 17:50 BST. I’ll update this post as I learn more.
Earlier today Railway, the hosting provider that runs skowt.cc, Etcht and a few smaller Antifield services, disclosed a security incident. An unauthorised third party accessed the systems where Railway stores its customers’ environment variables, and for some customers obtained their decrypted contents.
Environment variables are the settings an app is started with. For Antifield’s apps, they include things like API keys for other services and the credentials the apps use to reach their own databases. They don’t contain your personal data.
This was a breach at Railway, not in my own code, and it hit many companies that host with them. In the four years I’ve run skowt.cc, this is the first time anything like it has happened. If you’ve just found skowt.cc, I’m sorry this is your first impression.
Is it safe to use skowt.cc?
Yes. As far as I can tell, skowt.cc is safe to use, and so is your account.
- No passwords: you sign in to skowt.cc with Discord, so I’ve never stored a password for you.
- Discord tokens are encrypted: the tokens Discord gives skowt.cc when you sign in are encrypted.
- They can’t be used to take over your Discord: they only ever allowed skowt.cc to read your Discord name, avatar and email address, which is all it asks for. They can’t be used to log in to your Discord, read your messages, join servers or act as you.
What I know
- What was exposed: Railway has confirmed that environment variables were accessed, and says the impact may be limited to a subset of its customers. It has not said that customer databases or files were accessed.
- Whether Antifield is affected: Railway has emailed all customers asking them to rotate their credentials, but hasn’t confirmed whether Antifield’s services were in the affected subset. I’m treating its keys as exposed, because that’s the only safe assumption. From my own checks so far, none of Antifield’s services or data were accessed.
- The sites: skowt.cc and Etcht are up and working normally. Railway has restored deployments, so I have full access to Antifield’s production services again.
- Your data: as far as I can tell, all user data is safe. I’ve seen no signs of anyone accessing skowt.cc’s production systems, and I’m monitoring them continuously. I’ve finished scanning skowt.cc’s network logs from 18 October up to when I removed public access. Apart from my own backup, nothing outside Railway connected to skowt.cc’s database or Redis instance during the breach window, and I’ve found no evidence that anyone accessed user data.
- Files: skowt.cc’s files are stored with Cloudflare, not Railway. Only the key to reach them was on Railway, and I’ve confirmed it could only reach skowt.cc’s own files, nothing else. The files are locked, and I’m taking a full offline backup of them.
- Code: I’ve reviewed Antifield’s GitHub audit logs, going back a year, and my own account’s, going back six months. There’s nothing out of the ordinary. The last time Railway downloaded any of Antifield’s code was for a routine build on 14 October, a week before the breach, and there’s been no unexpected activity since.
What I’m doing
- Revoking keys: I’ve revoked the keys for paid compute services, which Railway says the attackers were after. Some background features may pause until Railway lets me deploy again.
- Pausing uploads: I’ve asked skowt.cc contributors not to upload anything until every key has been rotated.
- Moved skowt.cc’s files to new storage in the EU, with a new key, as a precaution. The old storage key has been revoked, and links to skowt.cc’s files haven’t changed.
- Redeploying skowt.cc’s systems one at a time, so there’s as little downtime as possible. So far there’s been none. I’m monitoring everything as I go.
- Rotating every key as a precaution, now that deployments have resumed. This includes the keys that sign skowt.cc logins, so every skowt.cc user will be signed out soon and will need to log in again.
- Reviewing logs and taking backups outside Railway.
Timeline
All times are UK time (BST).
21 October 2026
- 08:24: Railway started investigating problems with its dashboard, API and builds. Deployments were paused across the platform.
- 22:20: Saw reports that Railway was telling some customers to rotate their credentials.
- 23:10: Railway published its security disclosure.
- 23:15: Published this notice.
- 23:33: Told skowt.cc users on Discord.
- 23:45: Took a full backup of the skowt.cc database and stored it outside Railway.
- 23:55: Removed public proxy access to the skowt.cc database and Redis instance.
22 October 2026
- 00:10: Sent Railway a formal request for details of the incident and its scope.
- 00:20: Suspended Railway’s access to Antifield’s code repositories.
- 00:24: Railway emailed all customers asking them to rotate their credentials.
- 01:07: Reported the incident to the ICO, the UK’s data protection regulator.
- 01:20: Locked skowt.cc’s file storage so no files can be deleted or overwritten.
- 03:25: Started a full offline backup of skowt.cc’s files.
- 03:30: Revoked the keys for paid compute services.
- 03:35: Confirmed the exposed storage keys could each only reach their own app’s files.
- 03:40: Asked skowt.cc contributors to pause uploads.
- 04:05: Reviewed and saved Antifield’s and my personal GitHub audit logs. Neither shows any sign of unauthorised access.
- 06:43: Regained access to production after Railway restored deployments.
- 06:55: Started scanning skowt.cc’s network logs for any unauthorised access to its database and Redis instance.
- 07:05: Finished the scan. No unauthorised connections to skowt.cc’s database or Redis instance.
- 07:25: Started rotating skowt.cc’s keys and moving its files to a new storage bucket.
- 17:30: Switched skowt.cc to its new storage key and revoked the old one, with no downtime.
- 17:45: Finished moving skowt.cc’s files to new storage in the EU.
What you need to do
Right now, nothing. I’ll be rotating the keys that sign login sessions whether or not Antifield turns out to be affected, so you’ll be signed out and will need to log in again. If you’re in Etcht’s Research Preview, I’ll contact you privately.
I’m awake and on this, and I’ll keep this post updated as things change. If you have any questions, email me at marcel@antifield.com.
- Marcel