VirusTotal
6 / 92 engine detections
レポートを開く“myXRP — lock FXRP, hold the receipt”
Aptosなりすまし: myxrp.finance — コンテンツが利用できません (HTTP 410). 証拠の概要: VirusTotal 6/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 92 engine detections
レポートを開くSuspicious
レポートを開くScan report
レポートを開く4 community references
レポートを開く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
myxrp.finance is an impersonation phishing page that presented itself as "myXRP", a service for locking FXRP tokens and holding a receipt in return. It targeted XRP and FXRP holders looking for a place to lock or stake their tokens. PhishDestroy first flagged it on 2026-10-05. The site has been offline since 2026-10-18; by 2026-10-19 the domain no longer served any content at its root.
The page title, "myXRP — lock FXRP, hold the receipt", describes a familiar DeFi pattern: deposit a token into a vault and receive a receipt token that represents the locked position. Impersonation pages built on this pitch typically ask visitors to connect a wallet and approve or sign a "lock" transaction. That transaction actually hands the tokens, or permission to spend them, to the operator. No genuine receipt is ever issued, or the one issued is worthless. Victims lose the FXRP they tried to lock and anything else covered by the approvals they signed.
VirusTotal showed 6 of 92 engines flagging the domain on 2026-10-10: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That count is modest, so most scanners would still have let the page load. The flags do come from six unrelated vendors, which makes the verdict hard to dismiss. The domain also appears in 4 AlienVault OTX threat pulses. Among blocklists, only PhishDestroy's lists it.
The domain was registered through NameCheap, Inc. on 2026-09-09, just 26 days before PhishDestroy detected it. That short gap is typical of throwaway domains set up for a single campaign. Traffic ran through Cloudflare's network in the US, which hides the actual origin server behind a shared proxy address. The Let's Encrypt certificate gave the page a browser padlock, but it only means the connection was encrypted. It says nothing about whether the site was legitimate.
If you connected a wallet to myxrp.finance, review the token approvals granted from that address with a revocation tool and revoke any you do not recognise, especially those covering FXRP. If you signed a lock or deposit transaction, check the destination on a block explorer and move the remaining funds to a fresh wallet. If you ever typed a seed phrase into the site, treat that wallet as compromised. Find FXRP staking or locking services only through the official project's channels. Defenders should block the domain and check logs for wallet-connection traffic to it from before 2026-10-18.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x0c4f32c53d4b91a019c7c9d8da14af140295eef6Format validated · Domain analysis0x14b9dd90edaaff6527c1b168550b3faa15b9f6afFormat validated · Domain analysis0x1502FA4be69d526124D453619276FacCab275d3DFormat validated · Domain analysis0x2439D4bb753A0f3777d4C9011AFacc475ba6B951Format validated · Domain analysis0x34f90dfa0f1b2f691ee3a3a87954f8d282193c16Format validated · Domain analysis0x373D7d201C8134D4a2f7b5c63560da217e3dEA28Format validated · Domain analysis0x53184adabf312b490bf1ebcfdc896feff6019a14Format validated · Domain analysis0xAd552A648C74D49E10027AB8a618A3ad4901c5bEFormat validated · Domain analysisIoC extraction recorded 2026-10-06 04:00:05 UTC
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP の評判はこのドメインに起因しません。
angela.ns.cloudflare.comnick.ns.cloudflare.commail.myxrp.financepriority 10Location describes the IP network.
621867658ba8a85e67a1d068d4dd013f7170ffedb4cc216983e3e122b40dfa6cSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.myxrp.financeDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of myxrp.finance · checked Oct 5, 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.
dead_http: raw=http_410; http=410; via=https_proxy; server=cloudflare
myxrp.finance
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→inactive
http_no_content
live_content→inactive
http_no_content
到達可能→利用不可
不明→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
2→3
不明→live_content
content_served
到達可能
No threat flag
View source6/92 engine detections
View source4 community references
View sourcePD-20261005-85D4C2
Page captured
View sourcemyxrp.finance
View sourcePD-20261005-85D4C2 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
myxrp.finance)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.