VirusTotal
19 / 92 engine detections
レポートを開く“imToken | Ethereum & Bitcoin Wallet”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 5 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Ethereumなりすまし: tokenimgo-cdn-pop-hk23.club — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 19/92 (alphaMountain.ai, BitDefender, CRDF, ESET, Emsisoft)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
19 / 92 engine detections
レポートを開くThreat flag recorded
レポートを開くDBL_SPAM
悪意あり
レポートを開くScan report
レポートを開く4 community references
レポートを開くScan report
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
tokenimgo-cdn-pop-hk23.club is an impersonation phishing page aimed at Ethereum users. It presents itself as the imToken mobile wallet. Its name strings together lookalike wallet branding with CDN-style words to appear technical and legitimate. PhishDestroy first saw it on 2026-10-14, and as of 2026-10-19 the site was still online and serving its phishing content.
The page carries the title "imToken | Ethereum & Bitcoin Wallet", copying the branding of a well-known self-custody wallet. We classified it as Ethereum impersonation, while the page title and urlscan.io's brand detection point to imToken. Fake wallet sites like this usually push visitors to download a tampered app, "restore" or "verify" a wallet by typing in their recovery phrase or private key, or connect a wallet and approve a transaction. Anyone who hands over a seed phrase loses control of the wallet completely. The attacker can then empty every Ethereum, Bitcoin and token balance it holds.
On 2026-10-18, VirusTotal showed 19 of 92 engines flagging the domain, including alphaMountain.ai, BitDefender, CRDF, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet and G-Data. Google Safe Browsing lists it under SOCIAL_ENGINEERING, and urlscan.io returned a malicious verdict with imToken detected as the targeted brand. Spamhaus DBL lists the domain as DBL_SPAM. It also appears in 4 AlienVault OTX pulses and on the PhishDestroy blocklist.
The domain was registered on 2026-10-12 through Dynadot Inc, two days before PhishDestroy flagged it. It resolves to 156.225.27.69 on the COGNETCLOUD-2 network operated by cognetcloud INC, with the server geolocated in Hong Kong. The site uses a TLS certificate from Let's Encrypt (YR1), so the padlock in the browser says nothing about whether the site is legitimate.
If you entered a recovery phrase or private key here, treat that wallet as compromised. Set up a new wallet on a trusted device, with a fresh phrase, and move any remaining funds to it right away. If you connected a wallet or signed a transaction, use a token approval checker to revoke permissions you do not recognize. If you installed an app from this site, delete it and get imToken only from official app stores. Security teams should block the domain and its IP at DNS and proxy level, add it to email and chat filtering, and report it to the registrar and hosting provider for takedown.
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.
bf165eb9c3da504433b04227a5dfbcf4e07babf7844bac16560e77cf2e3d1b0cSaved 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://tokenimgo-cdn-pop-hk23.club/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:49:46 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.
不明→live_content
content_served
不明→live_content
content_served
No flag recorded→Flag recorded
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
Threat flag recorded
View source19/92 engine detections
View source4 community references
View sourcePD-20261014-875E3D
tokenimgo-cdn-pop-hk23.club
View sourcePage captured
View source保存された類似ドメイン:52 件
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
tokenimgo-cdn-pop-hk23.club
PD-20261014-875E3D 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 ↗
tokenimgo-cdn-pop-hk23.club)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.