Suspected Account Compromise and Unauthorized Database Access
heytaxx
HOBBYOP

21 days ago

Hello Railway Support Team,

I am writing to report a critical security incident regarding my Railway account and my deployed project. My database (MongoDB) was recently breached and I have lost access to it.

Importantly, the "Public Networking" feature for the database was strictly disabled. Since the database was not exposed to the public internet, I strongly suspect that the attacker either gained unauthorized access to my Railway account itself, or exploited a vulnerability to access the internal network.

Could you please investigate this incident? Specifically, I would need help with:

Checking if there were any unauthorized logins to my Railway account recently (IP logs).

Checking if the database was exported, modified, or deleted directly via the Railway Dashboard.

Ensuring my account is fully secured against further unauthorized access.

Thank you for your urgent assistance in this matter.

Solved

1 Replies

Railway
BOT

21 days ago

Your MongoDB service has no public domains or TCP proxy configured, confirming it is only reachable over the private network. Your workspace audit logs record actions performed within the workspace (changes to projects, services, deployments, variables, and settings) with timestamps and actor information, though on the Hobby plan the retention window is 48 hours. As an immediate step, we recommend a full security sweep: review and revoke any unrecognized sessions at Account Security, revoke unfamiliar apps at Authorized Applications, delete and recreate any API tokens at Account Tokens, and ensure 2FA is enabled on the security page. MongoDB on Railway is an unmanaged template, so database-level access control and security configuration (authentication, user roles, network restrictions within Mongo itself) are yours to manage per the MongoDB docs.


Status changed to Awaiting User Response Railway • 21 days ago


Railway
BOT

14 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 • 14 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...