VirusTotal
13 / 89 engine detections
レポートを開く“imToken | Ethereum & Bitcoin Wallet”
Ethereumなりすまし: tokenim.fyi — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 13/89 (alphaMountain.ai, BitDefender, CRDF, ESET, Emsisoft); URLScan malicious…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
13 / 89 engine detections
レポートを開く悪意あり
レポートを開く悪意あり
レポートを開く3 community references
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
tokenim.fyi is an impersonation phishing page. Its domain is a scrambled spelling of imToken, and its page title reads "imToken | Ethereum & Bitcoin Wallet". It targets people looking for that mobile wallet to hold Ethereum and other assets. PhishDestroy first flagged it on 2026-09-23. The site has been offline since 2026-09-25 after its provider blocked the content, and it was still dead when last checked on 2026-10-19. We classify the impersonated brand as Ethereum, while the page title and urlscan.io's brand detection point specifically to imToken.
Fake wallet sites like this copy the look of the official imToken page so that a visitor searching for the app believes they have found the real one. The usual next step is a prompt to "restore", "import" or "verify" a wallet by typing in the 12- or 24-word recovery phrase or a private key, or to install a tampered app that does the same. Anyone who hands over that secret gives the attacker full control of the wallet. The attacker can then empty every Ethereum, Bitcoin and token balance it holds, and these transfers cannot be reversed.
Thirteen of 89 VirusTotal engines flagged the domain on 2026-09-23, PhishDestroy's first day of tracking it. The flagging vendors include alphaMountain.ai, BitDefender, CRDF, ESET, Emsisoft, Fortinet, G-Data and Gridinsoft. urlscan.io returned a malicious verdict and recognised imToken branding on the page. The domain also appears on the MetaMask and SEAL blocklists alongside PhishDestroy, and three AlienVault OTX threat pulses reference it.
The domain was registered on 2026-09-16 through Cloudflare, Inc, only seven days before PhishDestroy detected it. That short gap is typical of throwaway phishing domains set up for a single short campaign. The site was served through Cloudflare's network on an address geolocated to Canada, which hides the actual origin server. The site went dark two days after detection.
If you typed your recovery phrase or private key into this site, treat that wallet as compromised. Create a new wallet with a fresh phrase on a clean device, using the official imToken app from a verified app store, and move any remaining funds there immediately. If you installed anything the site offered, remove it and scan the device. If you connected a wallet, revoke any token approvals it granted. Security teams should block the domain and watch for similar imToken lookalike spellings on short-lived domains.
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 の評判はこのドメインに起因しません。
clarissa.ns.cloudflare.comkip.ns.cloudflare.comLocation describes the IP network.
a5b0649e135c49ff4e06b32da3402fdc45c4b9a3912f81c2ae898bba8d25830dSaved 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 tokenim.fyi · checked Sep 23, 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
tokenim.fyi
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
到達可能
No threat flag
View source3 community references
View source13/89 engine detections
View sourcetokenim.fyi
View sourcePage captured
View source保存された類似ドメイン:52 件
Listed 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 ↗
tokenim.fyi)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.