23 days ago
Hello,
I would like to report that my Claude API key, which was set as a secret variable, was somehow leaked and was used by someone else. If anyone has faced the same issue could you please let me know how to report it or how to be sure if it is safe or not for future use?
Kind regards.
Harsh
2 Replies
Status changed to Awaiting Railway Response Railway • 23 days ago
23 days ago
We're sorry this happened to you, and for the uncertainty and extra work it causes. On October 21 we had a security incident. Keys stored in Railway before then, including AI provider keys like Anthropic's, should be treated as exposed. We can't say whether a particular key was accessed or used, so the safe step is the same either way: create a new key in the Anthropic Console and revoke the old one, then update the Railway variable and redeploy the services that use it. Check Anthropic's usage and activity logs to see whether the key was misused.
The attacker's access to our systems ended at 03:32 UTC on October 22, so it is safe to store the new key in Railway. You can read the timeline and details in our preliminary report.
16 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 16 days ago
Status changed to Awaiting User Response sam-a • 8 days ago
Status changed to Awaiting Railway Response Railway • 8 days ago
8 days ago
Hi Harsh,
Following up on the unauthorized use of your Claude API key you reported after the October 21 incident. Our full incident report is now published here: https://blog.railway.com/p/incident-report-october-security-incident
We can now reimburse documented charges from unauthorized use of your API keys in the October 21 incident that the provider hasn't credited or refunded. So that we can include your charges, please submit them through this form:
https://docs.google.com/forms/d/e/1FAIpQLScoZrMclYiCD0mGxQ0Gf8spo-Brqn8nT6Vu7Ye9mRwQrCTz_A/viewform
Estimates are fine, and it helps to include this thread's link and any case number from the provider. Please keep any secret keys out of what you send. We'll share the details of the process with all affected customers soon.
We're sorry for the cost and the time this has taken.
Status changed to Awaiting User Response sam-a • 8 days ago
21 hours ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 21 hours ago