VirusTotal
9 / 89 engine detections
打开报告“Multiplier”
冒充 MetaMask: tokensrave.xyz — 内容不可用. 证据摘要: VirusTotal 9/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data); 2 external blocklist matches…
为保留原始取证记录,下方的 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
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.