VirusTotal
11 / 89 engine detections
レポートを開く“Multichain - Cross-Chain Router Protocol”
暗号資産フィッシング: web-dmwrx.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 11/89 (alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker, Fortinet)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 89 engine detections
レポートを開く悪意あり
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
web-dmwrx.pages.dev was a phishing page posing as Multichain, presenting itself under the title "Multichain - Cross-Chain Router Protocol." It targeted people moving tokens between blockchains who expected the familiar bridge interface. PhishDestroy first flagged it on 2026-09-15. The site has been offline since 2026-09-23 after the hosting provider blocked its content, and it was still down when last checked on 2026-10-19.
Fake bridge pages copy the look of a real cross-chain router and ask visitors to connect a wallet so they can start a transfer. The connection step is the trap. The victim is prompted to sign a token approval or transaction that hands control of their funds to the attacker, or to send assets into a bridge that does not exist. Because bridging normally involves several unfamiliar signatures, users often approve without reading them. Anything approved or sent can be drained and is generally unrecoverable.
On 2026-09-21, 11 of 89 VirusTotal engines marked the site as malicious, including BitDefender, ESET, Kaspersky, Fortinet, Forcepoint ThreatSeeker, G-Data, Lionic and alphaMountain.ai. That is a minority of engines, but the vendors come from independent security companies. urlscan.io returned a malicious verdict and recognized generic crypto branding on the page. Beyond PhishDestroy, the domain is listed by MetaMask and SEAL, both of which focus on wallet-facing crypto threats.
The page ran as a free Cloudflare Pages project created on 2026-08-24, about three weeks before PhishDestroy detected it. Throwaway pages.dev subdomains let operators launch a polished clone in minutes with no domain to buy. The traffic was served through Cloudflare's network, geolocated to Canada. The TLS certificate from Google Trust Services was issued automatically by the platform, so the padlock said nothing about who ran the page.
If you connected a wallet to this page, review its token approvals and revoke any you do not recognize, especially recent ones granted around the time you visited. If you signed a transaction or sent funds, move the remaining assets to a new wallet whose seed phrase has never been entered or exposed. If you typed in a seed phrase or private key, treat that wallet as compromised and abandon it. To bridge tokens, reach any bridge only through its official channels, and check every signature request before you approve it. Defenders should block this hostname and watch for similar pages.dev subdomains that use Multichain or cross-chain router branding.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/anyswapStored page referenceIoC extraction recorded 2026-10-02 04:00:13 UTC
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
a50b80eb4379decf5abc941bb3466e9ac8d8044bb6085f58502872617fd0072dSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
web-dmwrx.pages.dev
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
到達可能
No threat flag
View source11/89 engine detections
View sourceweb-dmwrx.pages.dev
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
web-dmwrx.pages.dev)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.