VirusTotal
7 / 92 engine detections
レポートを開く“imToken | Ethereum”
Ethereumなりすまし: tokenimnet-cdn-gw-hk27.cfd — コンテンツが利用できません. 証拠の概要: VirusTotal 7/92 (alphaMountain.ai, Emsisoft, Fortinet, Kaspersky, Netcraft); URLScan…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
7 / 92 engine detections
レポートを開く悪意あり
レポートを開くDBL_SPAM
悪意あり
レポートを開くScan report
レポートを開く4 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
tokenimnet-cdn-gw-hk27.cfd is an impersonation phishing page that used the title "imToken | Ethereum" to pass as the imToken mobile wallet's Ethereum service. PhishDestroy classifies it as Ethereum impersonation, while the page title also names imToken, the wallet brand urlscan.io detected on the page. It targets people who hold ETH or tokens in imToken. PhishDestroy first saw it on 2026-10-14, and it has been offline since 2026-10-17, with DNS no longer resolving as of 2026-10-19.
The domain name strings together "tokenim", "net", "cdn" and "gw" so it looks like official imToken delivery infrastructure at a glance. Pages of this type usually show a wallet login, "verify" or "sync" screen and ask for the recovery phrase, private key or wallet password, or they ask the visitor to connect a wallet and sign a transaction. Anyone who types a recovery phrase into such a page hands over full control of the wallet, and the attackers can empty it at any time from any device. A malicious signature can grant token allowances that let the attackers pull assets later.
Seven of 92 VirusTotal engines flagged the domain on 2026-10-14, the day PhishDestroy detected it. The flagging vendors were alphaMountain.ai, Emsisoft, Fortinet, Kaspersky, Netcraft, SOCRadar and Webroot. That count is modest, but it was reached within two days of registration. urlscan.io returned a malicious verdict and recognised imToken branding. Spamhaus lists the domain in its DBL as spam, four AlienVault OTX pulses reference it, and it is on the PhishDestroy blocklist.
The domain was registered through Dynadot Inc on 2026-10-12 and was being caught by scanners by 2026-10-14. That short gap fits a disposable domain stood up for a quick campaign. It sat on a cheap .cfd name and was served from the COGNETCLOUD-2 network (cognetcloud INC), with the IP located in Hong Kong. A free Let's Encrypt certificate gave it the padlock icon, which proves nothing about who runs the site.
If you entered a recovery phrase or private key on this site, treat the wallet as compromised. Create a new wallet on a clean device and move any remaining funds to it immediately. If you connected a wallet or signed anything, check token approvals with a revoke tool and cancel any you do not recognise. Only download imToken from the official app stores or its official website, and never type a recovery phrase into a web page. Defenders should block the domain and look for lookalike "tokenim" hostnames on new low-cost TLDs in DNS and proxy logs.
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.
ns1.dyna-ns.netns2.dyna-ns.netLocation describes the IP network.
c2e16254fb5ad7a8b17ed2058ba5c8ce9516e75af15aaa22aa1c4d82cecc46d7Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://tokenimnet-cdn-gw-hk27.cfd/Content-Type: text/html; charset=UTF-8Cache-Control: no-store, no-cache, must-revalidateContent-Encoding: gzipServer: nginxc73bd124a5ea2ff79862e7679be3a68536826e908179e2dd7928a9b610976463quic=":443"; h3=":443"; h3-29=":443"; h3-27=":443";h3-25=":443"; h3-T050=":443"; h3-Q050=":443";h3-Q049=":443";h3-Q048=":443"; h3-Q046=":443"; h3-Q043=":443"no-store, no-cache, must-revalidatekeep-alivegziptext/html; charset=UTF-8Wed, 14 Oct 2026 19:50:30 GMTThu, 19 Nov 1981 08:52:00 GMTno-cachenginxmax-age=31536000chunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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
到達可能→利用不可
live_content→dns_inactive
dns_nxdomain
不明→live_content
content_served
不明→live_content
content_served
到達可能
No threat flag
View source4 community references
View source7/92 engine detections
View sourcePD-20261014-E421E9
tokenimnet-cdn-gw-hk27.cfd
View sourcePage captured
View source保存された類似ドメイン:52 件
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
tokenimnet-cdn-gw-hk27.cfd
PD-20261014-E421E9 Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains 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 ↗
tokenimnet-cdn-gw-hk27.cfd)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.