Skip to content
MetaMask flags bouncer.up.railway.app as malicious — possible link to Railway incident QBCLHG1V
snepsid
OP

13 days ago

MetaMask flags bouncer.up.railway.app as malicious — possible link to Railway incident QBCLHG1V

We run Bouncer, a Discord wallet-ownership verifier hosted on Railway, and expect members to connect their wallets and sign an ownership-verification message. A member and the operator independently reproduced MetaMask classifying our website as malicious during both connection and signing, which interrupts verification and undermines users' trust. The warning was reported on November 7, 2026 and remains unresolved in our investigation; we have no confirmed successful retest after the reports. Please investigate whether our hostname or serving infrastructure is affected by the reputation problems in incident QBCLHG1V and advise on correction if related.

Resources and timing

  • Public application: https://bouncer.up.railway.app
  • Railway incident: https://status.railway.com/incident/QBCLHG1V
  • Warning reports and diagnostic checks: November 7, 2026 (America/Detroit; exact warning times were not recorded).
  • The incident page's latest observed update, November 5 at 18:51 UTC, remained “Identified” when checked November 7. Railway said it was contacting network operators, security vendors and abuse database providers.

Evidence and reproduction

The operator reported Google Chrome 155.0.8059.39 (Official Build), x86_64, with MetaMask 13.55.0 on Ethereum. The other reporting member's client versions were not supplied.

  1. Open a verification link issued by Bouncer through Discord.
  2. Select EVM and connect MetaMask.
  3. MetaMask labels bouncer.up.railway.app “Malicious—flagged as unsafe.”
  4. The operator also reported a malicious-site warning when requesting the ownership signature.

Exact warning text supplied by the operator:

Continue at your own risk

This site shows signs of phishing or wallet-draining activity. It may request transactions designed to steal your funds.

The supplied signature request was EIP-712 primary type Verification, with domain Bouncer, version 1, chain ID 1. The inspected verification path requests a typed-data signature and reads ownership; it does not request asset transfers, permits or token approvals. These observations describe the inspected flow and do not establish that the classification is erroneous.

Checks performed November 7:

  • MetaMask's official public domain checker returned “This domain is not blocked! No problem here.” The public static phishing configuration had no direct domain or parent-domain block match. A separate live classification or cached result is still possible.
  • MetaMask 13.55.0 source uses a hostname URL-scan result for the connection warning and for origin alerts during signature confirmation. This explains how one classification could affect both actions; it does not identify the underlying signal/provider.
  • Unauthenticated reads of MetaMask's live scan/feed endpoints returned HTTP 403, so the assistant could not inspect their classification reason.
  • The public site's two JavaScript entry files matched the expected existing local production artifacts. This was a limited comparison, not a complete security audit.
  • The user subsequently confirmed that a MetaMask support ticket was successfully created. No ticket number or review outcome was provided.

Why contact Railway?

The user first suggested contacting Railway to ask whether MetaMask was among those affected by the incident. The assistant agreed because Railway's incident notice described work with security vendors and reputation providers, while the investigation had not obtained MetaMask's classification reason.

Could you check whether this application's serving infrastructure falls within the affected reputation listings, whether MetaMask or its relevant classification providers are known to be affected, and whether our hostname can be included in an appropriate vendor review? Any incident-specific information we can share with MetaMask would help coordinate the two investigations.

Uncertainty and scope

A connection to the Railway incident is a hypothesis. Railway described IP-address blocks following traffic with forged Railway source IPs; MetaMask is flagging a hostname, and neither investigation has confirmed that the two are connected. The public MetaMask checker did not flag the hostname. Railway's incident notice also stated that the spoofed traffic was not evidence of compromised customer workloads.

The assistant's lack of access to MetaMask's live classification does not establish that only Railway can diagnose it. This is a request for diagnosis and guidance, not authorization to modify or delete resources.

Prepared with Railway's support template (v1).

Solved

6 Replies

Railway
BOT

13 days ago

Your application is being served normally from our edge right now. The incident you linked is still in the Identified stage. It covers network providers and security services blocking Railway IP addresses after a third party sent scanning traffic with forged Railway source IPs, and the scanning traffic did not come from customer workloads.

The incident covers blocks on IP addresses. It does not mention hostname-level classifications in wallet extensions, and we can't confirm whether MetaMask or the providers it relies on are among the affected vendors. So a link between this incident and MetaMask's warning on your hostname is not established. The incident notice is the information we've published for sharing with vendors, and your MetaMask ticket is the place to get their classification reviewed.


Status changed to Awaiting User Response Railway • 13 days ago


Railway

Your application is being served normally from our edge right now. The incident you linked is still in the Identified stage. It covers network providers and security services blocking Railway IP addresses after a third party sent scanning traffic with forged Railway source IPs, and the scanning traffic did not come from customer workloads. The incident covers blocks on IP addresses. It does not mention hostname-level classifications in wallet extensions, and we can't confirm whether MetaMask or the providers it relies on are among the affected vendors. So a link between this incident and MetaMask's warning on your hostname is not established. The incident notice is the information we've published for sharing with vendors, and your MetaMask ticket is the place to get their classification reviewed.

snepsid
OP

13 days ago

Thanks. Per your check, Bouncer is being served normally. We understand that a connection between the Railway incident and MetaMask’s hostname classification has not been established.

We submitted a MetaMask support ticket. No classification-review outcome or successful fresh retest has been confirmed in the information available to us.

Could a Railway team member check whether Bouncer’s serving infrastructure is among the affected reputation listings? Is there any incident-specific information beyond the public notice that we can provide to MetaMask?

If no further platform-side check or information is available, please confirm. We’re requesting diagnosis and guidance only; no resource changes are requested.


Status changed to Awaiting Railway Response Railway • 13 days ago


Railway
BOT

13 days ago

We confirmed again that the app is reachable and being served from our edge with a valid certificate. We can't check which specific Railway IP addresses or hostnames appear in a given vendor's reputation listings, and we have no incident information to share beyond the public incident notice. That notice is still at the Identified stage. It covers IP-address blocks caused by scanning traffic that used forged Railway source IPs, and it is the material intended for vendors and network administrators reviewing those blocks.

Because MetaMask's warning applies to a hostname and their own domain checker doesn't list it, your MetaMask ticket is the route for getting that classification reviewed. You're welcome to include the incident notice with it.


Status changed to Awaiting User Response Railway • 13 days ago


Railway

We confirmed again that the app is reachable and being served from our edge with a valid certificate. We can't check which specific Railway IP addresses or hostnames appear in a given vendor's reputation listings, and we have no incident information to share beyond the [public incident notice](https://status.railway.com/incident/QBCLHG1V). That notice is still at the Identified stage. It covers IP-address blocks caused by scanning traffic that used forged Railway source IPs, and it is the material intended for vendors and network administrators reviewing those blocks. Because MetaMask's warning applies to a hostname and their own domain checker doesn't list it, your MetaMask ticket is the route for getting that classification reviewed. You're welcome to include the incident notice with it.

snepsid
OP

13 days ago

Thanks for checking and clarifying. We’ll include the public incident notice and your reachability/certificate findings in the MetaMask review. We understand that no connection between the incident and the hostname classification has been established.


Status changed to Awaiting Railway Response Railway • 13 days ago


Status changed to Awaiting User Response Railway • 13 days ago


snepsid
OP

13 days ago

What are you awaiting my response for?


Status changed to Awaiting Railway Response Railway • 13 days ago


Railway
BOT

13 days ago

Nothing, and we're sorry for the confusion. That status changes automatically whenever we post a reply, so it doesn't mean we need anything more from you.

As we said in our earlier reply, there's no further check we can run on vendor reputation listings and no incident information beyond the public notice. Your MetaMask ticket is the right place for the classification review.


Status changed to Awaiting User Response Railway • 13 days ago


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...