VirusTotal
4 / 89 engine detections
レポートを開く“Attention Required! | Cloudflare”
ブロックリスト掲載ドメイン: token-rush.xyz — コンテンツが利用できません. 証拠の概要: VirusTotal 4/89 (CRDF, Forcepoint ThreatSeeker, LevelBlue, VIPRE); 2 external blocklist matches…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 89 engine detections
レポートを開くchecked — no detections recorded
レポートを開く3 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
token-rush.xyz is an impersonation phishing page that copies Cloudflare's familiar "Attention Required!" interstitial, the screen people see before a protected site loads. The crypto-flavoured domain name and its listing by MetaMask and SEAL point to crypto users as the targets. PhishDestroy first saw it on 2026-09-17. The site went offline on 2026-09-18 and was still dead on 2026-10-19.
Fake Cloudflare checks work because almost everyone has clicked through a real one without thinking. The page shows the title "Attention Required! | Cloudflare" and asks the visitor to prove they are human. The real step behind that prompt is something else. In schemes of this type, the visitor may be told to paste a command into their computer, enter credentials, or connect and sign with a wallet. Doing so can hand over device access, account logins or wallet assets. That page title is identical to the one Cloudflare's genuine challenge pages use, and PhishDestroy classified the page as an impersonation of that check.
Four of 89 VirusTotal engines flagged the domain on 2026-09-17: CRDF, Forcepoint ThreatSeeker, LevelBlue and VIPRE. That is a low count, typical for a page caught within days of going live. Wallet-focused blocklists are the stronger signal here. MetaMask and SEAL both list the domain alongside PhishDestroy. It also appears in three AlienVault OTX threat pulses, so other researchers tracked it independently.
The domain was registered through NAMECHEAP INC on 2026-09-14, only three days before detection, and was offline a day after that. This short registered-to-dead lifespan is typical of throwaway phishing domains. Traffic resolved to Cloudflare, Inc. network space geolocated to Canada, so a fake Cloudflare page was itself served from behind Cloudflare.
If you ran any command this page told you to paste, treat the device as compromised. Disconnect it, scan it, and change passwords for email, exchanges and wallets from a different clean device. If you entered a login, reset that password and turn on app-based 2FA. If you connected a wallet or signed anything, revoke approvals granted around that time and move funds to a fresh wallet if you shared a seed phrase. Defenders should block the domain and alert users that a Cloudflare check never asks for commands, logins or wallet connections.
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 の評判はこのドメインに起因しません。
michael.ns.cloudflare.compam.ns.cloudflare.comLocation describes the IP network.
Saved 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 token-rush.xyz · checked Sep 17, 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.
token-rush.xyz
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能→利用不可
1→4
到達可能
No threat flag
View source3 community references
View source4/89 engine detections
View sourcePD-20260917-44CFED
token-rush.xyz
View sourcePage captured
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
PD-20260917-44CFED 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 ↗
token-rush.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.