VirusTotal
21 / 92 engine detections
打开报告“imToken | Ethereum & Bitcoin Wallet”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@godaddy.com.
The latest stored availability evidence still shows the domain reachable; 3 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: rripphiobkbcwrv6.hg039.cc — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 21/92 (alphaMountain.ai, BitDefender, CRDF, Ermes, ESET); URLScan malicious…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
21 / 92 engine detections
打开报告恶意
打开报告Threat flag recorded
打开报告恶意
打开报告Scan report
打开报告no community references
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
rripphiobkbcwrv6.hg039.cc is an impersonation phishing page that targets Ethereum users. It presents itself under the title "imToken | Ethereum & Bitcoin Wallet", and urlscan.io identified the imToken brand on it. PhishDestroy first saw the site on 2026-10-17. As of 2026-10-19 it was still online and serving live content. The page title shows the imToken wallet brand, while our classification lists Ethereum as the impersonated brand.
Fake wallet sites like this copy the look of a well-known wallet so visitors believe they are on an official download or login page. The victim is then pushed to restore or import a wallet by typing a recovery phrase or private key, or to connect an existing wallet and approve a request. A recovery phrase entered on such a page gives the operator full control of the wallet, and they can move every asset in it to their own addresses. Signed approvals can also let the operator spend tokens later without asking again.
urlscan.io returned a malicious verdict for the site and detected the imToken brand. On VirusTotal, 2 of 92 engines flagged it as of 2026-10-17: CRDF and DNS8. That detection rate is low, so most security tools may not warn visitors yet. The domain is listed on the PhishDestroy blocklist.
The parent domain hg039.cc was registered on 2026-05-06 through GoDaddy.com, LLC. The long random-looking subdomain sits on that registration. The site resolves to 52.128.227.253, which is on the NETSEC-HK network operated by Netsec Limited in Hong Kong.
If you typed a recovery phrase or private key on this site, treat that wallet as compromised. Create a new wallet from a fresh phrase on a trusted device and move any remaining funds to it immediately. If you connected a wallet or signed a transaction, revoke token approvals with a reputable allowance checker and watch the wallet for unexpected transfers. Only download imToken from its official website or verified app store listings. Security teams should block the domain and the IP 52.128.227.253, add the indicators to mail and web filters, and report the site to the registrar and hosting provider.
ns21.domaincontrol.comns22.domaincontrol.comLocation describes the IP network.
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://rripphiobkbcwrv6.hg039.cc/Server: nginx/1.24.0 (Ubuntu)Content-Type: text/htmlContent-Encoding: gzipkeep-alivegziptext/htmlSat, 17 Oct 2026 00:16:09 GMTW/"6a5f146b-211"Tue, 21 Jul 2026 06:40:43 GMTnginx/1.24.0 (Ubuntu)chunkedValues 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.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=http_proxy; server=nginx/1.24.0 (Ubuntu)
rripphiobkbcwrv6.hg039.cc
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
No flag recorded→Flag recorded
未知→live_content
content_served
未知→live_content
content_served
可访问
21/92 engine detections
View sourceThreat flag recorded
View sourcePD-20261017-6AE66A
rripphiobkbcwrv6.hg039.cc
View sourcePage captured
View source已存储 52 个仿冒域名
PD-20261017-6AE66A Recipient: abuse@godaddy.com 如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
rripphiobkbcwrv6.hg039.cc)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.