VirusTotal
10 / 89 engine detections
打开报告“78.899 | HYPE | Hyperliquid”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@tonic.to.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
冒充 Hyperliquid: hyperiiquid.to — 最后已知的活跃状态 (HTTP 301). 证据摘要: VirusTotal 10/89 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet)…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
10 / 89 engine detections
打开报告DBL_PHISH
checked — no detections recorded
打开报告4 community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
hyperiiquid.to is a phishing page impersonating Hyperliquid, the on-chain perpetuals exchange. The domain swaps the letter "l" for a doubled "i", a substitution that is easy to miss in a browser bar or a search result. It targets HYPE holders and Hyperliquid traders. PhishDestroy first flagged it on 2026-09-15, and as of 2026-10-19 the site is still online and redirecting visitors.
The page title, "78.899 | HYPE | Hyperliquid", copies the format of a live trading page by putting a HYPE price ticker in front of the brand name. That makes a browser tab or a shared link look like the genuine market view. Pages of this kind steer visitors toward connecting a wallet or signing what looks like a routine login or trade request. If the victim connects or signs, the operator can obtain transfer permissions over funds or collateral that a real exchange would never request.
Ten of 89 VirusTotal engines flagged the domain as of 2026-09-24. Those engines include BitDefender, Kaspersky, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, CRDF and alphaMountain.ai. MetaMask and SEAL both list it alongside PhishDestroy, so wallet users with those protections should see a warning before the page loads. Spamhaus classifies it as DBL_PHISH, and four AlienVault OTX threat pulses reference it.
The domain was registered on 2026-08-14, about a month before PhishDestroy detected it. It sits under Tonga's .to country-code TLD rather than the brand's own domain. Traffic passes through Cloudflare, with the edge address geolocated to Canada, which keeps the origin server out of view. Its Google Trust Services certificate only means the connection is encrypted, so the padlock says nothing about whether the site is legitimate.
If you connected a wallet or signed anything on this site, move remaining funds to a fresh wallet and revoke any token approvals or delegated permissions granted during that session. If you typed a seed phrase, treat that wallet as fully compromised and abandon it. Reach Hyperliquid only through a bookmark you saved yourself, and check every letter of the domain. Defenders should block hyperiiquid.to at DNS and proxy level, report it to Cloudflare and the .to registry, and watch for further lookalike Hyperliquid domains.
Last checked
Edge-IP 声誉不属于此域。
evelyn.ns.cloudflare.comzahir.ns.cloudflare.comLocation describes the IP network.
b96db4f2a0653997a9cf160ae858d8d49ec8a76b79498278413ca0232eb74c74hyperiiquid.to*.hyperiiquid.toSaved 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 hyperiiquid.to · checked Sep 15, 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.
redirect: raw=redirect_301; http=301; via=http_proxy; location=https://hyperiiquid.to/; server=cloudflare
hyperiiquid.to
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
7→9
可访问
4 community references
View sourceNo threat flag
View source10/89 engine detections
View sourcePD-20260915-9F1E20
hyperiiquid.to
View sourcePage captured
View sourcePD-20260915-9F1E20 Recipient: abuse@tonic.to 如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
hyperiiquid.to)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.