VirusTotal
4 / 89 engine detections
レポートを開く“xExchange”
GMXなりすまし: xexchanger.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 4/89 (Forcepoint ThreatSeeker, Gridinsoft, LevelBlue, VIPRE); 3 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 89 engine detections
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開く80/100
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
xexchanger.pages.dev is an impersonation phishing page that presented itself under the title "xExchange," borrowing the name of a decentralized exchange to lure crypto users into trusting it. The added "r" in the subdomain is a lookalike trick aimed at people searching for the real exchange or clicking shared links. PhishDestroy first flagged it on 2026-09-02. The site went offline on 2026-09-16, and the hosting provider has blocked its content, which remained the case as of 2026-10-19.
Pages that imitate a decentralized exchange copy the familiar swap interface, then ask visitors to connect a wallet to trade or claim something. The prompts that follow are the theft. A visitor may be asked to sign a transaction or token approval that hands spending rights to the attacker, or to type in a recovery phrase to "restore" or "verify" a wallet. Either way, the victim can lose whatever the wallet holds, often within minutes and with no way to reverse the transfers.
Four of 89 VirusTotal engines flagged the site on 2026-09-16: Forcepoint ThreatSeeker, Gridinsoft, LevelBlue and VIPRE. That is a low count, but the stronger signal comes from the crypto-focused community. MetaMask, ScamSniffer and the SEAL alliance all list the domain alongside PhishDestroy. MetaMask's listing means its users get a warning before the page loads.
The page ran as a free Cloudflare Pages project, with a creation date of 2024-11-20. That is nearly two years before PhishDestroy caught it, so the address may have sat idle or been repurposed. Traffic resolved to Cloudflare, Inc. infrastructure geolocated to Canada. The certificate from Google Trust Services is the standard one issued automatically to every pages.dev site, so the padlock said nothing about legitimacy.
If you connected a wallet to this page, check your token approvals with a revocation tool and revoke any you don't recognize. Move remaining funds to a fresh wallet if you signed anything you didn't understand. If you entered a recovery phrase, treat that wallet as compromised and transfer assets to a new wallet created with a new phrase immediately. Open exchanges only from bookmarks or the project's verified channels, never from ads or links in direct messages. Security teams should block this domain and watch for similar lookalike subdomains on free hosting platforms.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/xExchangeAppStored page referenceIoC extraction recorded 2026-09-21 04:01:19 UTC
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
db32ae364e2b9b104a78e7a5a70da9fb1142cbd3696d15ca4a8eb6afeff292e9Saved 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
xexchanger.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
到達可能→利用不可
到達可能
4/89 engine detections
View sourceNo threat flag
View sourcexexchanger.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 ↗
xexchanger.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.