VirusTotal
16 / 89 engine detections
レポートを開く“imToken | Ethereum & Bitcoin Wallet”
Ethereumなりすまし: mtoken.me.uk — コンテンツが利用できません. 証拠の概要: VirusTotal 16/89 (alphaMountain.ai, CRDF, Ermes, ESET, Emsisoft); URLScan malicious verdict; CF Radar…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
16 / 89 engine detections
レポートを開く悪意あり
レポートを開く悪意あり
レポートを開く4 community references
レポートを開く80/100
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
mtoken.me.uk is an impersonation phishing page. Its name drops a single letter from imToken, a popular self-custody wallet, and it targets Ethereum and Bitcoin holders who search for that wallet. PhishDestroy classified the brand as Ethereum, but the page title presented the site as "imToken | Ethereum & Bitcoin Wallet". PhishDestroy first flagged it on 2026-09-14. The site has been offline since 2026-09-18 and its DNS was still inactive when last checked on 2026-10-19.
Lookalike wallet sites copy the official branding so a visitor believes they have reached the real imToken page. They then push the victim to hand over control of their funds. Common methods are prompts to "restore" or "verify" a wallet by typing the recovery phrase, or a fake app download that leaks keys. Once an attacker holds the seed phrase, they can empty every Ethereum and Bitcoin address derived from it, and those transfers cannot be reversed.
On 2026-09-16, 16 of 89 VirusTotal engines flagged the domain. The flagging vendors included ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Emsisoft, alphaMountain.ai, CRDF and Ermes. That is a meaningful spread of independent security vendors for a domain only four days old. urlscan.io returned a malicious verdict and recognised imToken branding on the page. The domain also appears in four AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered on 2026-09-12 through Cloudflare, Inc., and PhishDestroy flagged it two days later. That short gap is typical of throwaway phishing domains that go live almost as soon as they are bought. The site sat behind Cloudflare's network, with the IP geolocated to Canada, so the true origin server is hidden. It went dark roughly six days after registration, a lifespan consistent with a short campaign rather than a lasting site.
If you typed a recovery phrase or private key into this site, treat that wallet as compromised. Create a new wallet with a fresh seed on a trusted device and move any remaining funds immediately. If you connected a wallet or signed anything, check token approvals with a revocation tool and cancel any you do not recognise. Remove any imToken app installed from a link rather than the official app store. Defenders should block the domain and look for similar one-letter imToken typosquats in DNS and proxy logs.
Edge-IP の評判はこのドメインに起因しません。
donald.ns.cloudflare.comvida.ns.cloudflare.comLocation describes the IP network.
677838ad3f090c3e5ee4c9657a367a534a78dd8f3cf8d32801698121a40237cfSaved 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 mtoken.me.uk · 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.
mtoken.me.uk
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
到達可能→利用不可
15→16
14→15
13→14
到達可能
No threat flag
View source4 community references
View source16/89 engine detections
View sourcemtoken.me.uk
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 ↗
mtoken.me.uk)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.