VirusTotal
7 / 91 engine detections
レポートを開く“XRP DEX - Trade on the XRPL Decentralized Exchange | Live”
XRPなりすまし: xrpdex.us — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 7/91 (alphaMountain.ai, Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, Gridinsoft); 2…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
7 / 91 engine detections
レポートを開く4 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
xrpdex.us presents itself as a legitimate decentralized exchange built on the XRP Ledger, using the branding 'XRP DEX - Trade on the XRPL Decentralized Exchange' to attract XRP holders and DeFi traders. PhishDestroy first identified it on 2026-09-19, and as of 2026-10-18 the site remains fully live and actively serving malicious content. It is classified as a crypto wallet drainer, meaning its primary purpose is to silently empty connected wallets rather than facilitate any real trading.
Sites of this type mimic legitimate decentralized exchange interfaces, prompting visitors to connect their crypto wallets to 'trade' or 'access liquidity.' Once a wallet is connected, the underlying drainer kit requests broad token-spending approvals or triggers malicious transactions that transfer the victim's assets to attacker-controlled addresses, often within seconds and without further confirmation. The XRP Ledger framing is designed to attract holders of XRP and related tokens specifically, broadening the pool of potential victims beyond Ethereum-ecosystem users.
Seven of 91 engines on VirusTotal flagged xrpdex.us as malicious as of 2026-09-29, with detections from alphaMountain.ai, Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar, and VIPRE. The domain also appears across four threat-intelligence pulses on AlienVault OTX, indicating independent researcher tracking. It is actively blocked by PhishDestroy, MetaMask, and SEAL, meaning wallet software with those feeds will warn users before they can connect.
The domain was registered on 2026-04-11 through Namecheap Inc and was first flagged roughly five months later, suggesting a deliberate setup period. Hosting runs through Cloudflare's network on an IP geolocated to Canada, and the TLS certificate was issued by Google Trust Services under the WE1 intermediate, giving the site a padlock that conveys no safety guarantee.
If you visited the site but did not connect a wallet, no immediate action is required beyond avoiding any return visits. If you connected a wallet, immediately open a trusted revocation tool and revoke every approval granted to unfamiliar contracts, then transfer remaining assets to a fresh wallet address. Anyone who signed a transaction should assume those funds are lost and report the incident to their exchange and local cybercrime authorities. Security teams should add xrpdex.us to DNS and firewall blocklists and push the PhishDestroy, MetaMask, and SEAL feed updates to endpoint wallet software.
Last checked
Edge-IP の評判はこのドメインに起因しません。
dilbert.ns.cloudflare.comligia.ns.cloudflare.comLocation describes the IP network.
a838fd9c45fffc7662a6499b8aa7876805ec5a6e2b13cc81f20c4586da4a2b35Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of xrpdex.us · checked Sep 19, 2026
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.
xrpdex.us
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
4 community references
View sourceNo threat flag
View source7/91 engine detections
View sourcexrpdex.us
View sourcePage captured
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 ↗
xrpdex.us)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.