VirusTotal
9 / 89 engine detections
レポートを開く“Multiplier”
MetaMaskなりすまし: tokensrave.xyz — コンテンツが利用できません. 証拠の概要: VirusTotal 9/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data); 2 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
9 / 89 engine detections
レポートを開くchecked — no detections recorded
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開く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
tokensrave.xyz was an impersonation phishing page that presented itself under the title "Multiplier" and was built to pull crypto users into trusting a service it did not represent. PhishDestroy first saw it on 2026-09-14, three days after the domain was registered. It was short-lived. The site has been offline since 2026-09-18, and as of 2026-10-19 its domain no longer resolves.
Impersonation pages borrow the look and language of a legitimate crypto service so visitors act as if they were on the real thing. They hand over wallet access, sign transactions or send funds. A title like "Multiplier" fits the familiar lure of returning more crypto than you put in, a promise used to get victims to deposit tokens or connect a wallet and approve a transaction that empties it. The page title shows a generic "Multiplier" label rather than a specific brand name, while we classified the site as impersonation.
Nine of 89 VirusTotal engines flagged the domain when it was checked on 2026-09-16. Vendors that marked it malicious include alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, LevelBlue and SOCRadar. That is a minority of engines, but it is typical for a site caught within days of launch. More telling for crypto users, the domain sits on the MetaMask and SEAL blocklists alongside PhishDestroy's own. Four AlienVault OTX threat pulses also reference it, so researchers outside our project tracked it independently.
The domain was registered on 2026-09-11 through OwnRegistrar, Inc. and was already serving phishing content when we spotted it on 2026-09-14. It ran behind Cloudflare, with the address geolocated to Canada, which masks where the real server sat. Its Let's Encrypt certificate gave the page a browser padlock at no cost, a reminder that HTTPS proves nothing about a site's honesty. The whole lifecycle from registration to going dark took about a week.
If you connected a wallet to tokensrave.xyz, open a token-approval checker for every chain you used and revoke any permissions you do not recognize. Then move remaining assets to a fresh wallet if you signed anything unusual or typed in a seed phrase. Do not send more crypto in hopes of recovering a "multiplied" payout, because no such payout exists. Defenders should block the domain and look in DNS and proxy logs for visits between 2026-09-11 and 2026-09-18 to identify exposed users.
Last checked
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 の評判はこのドメインに起因しません。
elle.ns.cloudflare.comgerald.ns.cloudflare.comLocation describes the IP network.
f4b03d8da443e37478d1f61e278a7a81e712d7af02fa17d972785fb46408a8b5Saved 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 tokensrave.xyz · checked Sep 14, 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.
tokensrave.xyz
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
到達可能→利用不可
到達可能
No threat flag
View source9/89 engine detections
View source4 community references
View sourcePD-20260914-4F69E4
tokensrave.xyz
View sourcePage captured
View source保存された類似ドメイン:79 件
PD-20260914-4F69E4 Recipient: abuse@ownregistrar.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
tokensrave.xyz)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.