VirusTotal
4 / 92
engines flag the domain · 1 suspicious
“Hyperliquid”
4 / 92
engines flag the domain · 1 suspicious
No threat flag
Not on Google threat lists at check time
No malicious flag
Browser scan with screenshot
0
threat pulses mention the domain
Online · HTTP 200
Vercel · 216.198.79.1 · TLS: Let's Encrypt
malicioussuspicious
Each check shows its own collection time. Zero detections do not guarantee safety.
冒充 Hyperliquid: hyperliquid.my.id — 内容不可用. 证据摘要: VirusTotal 5/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); Spamhaus DBL_PHISH…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
5 / 92 engine detections
打开报告DBL_PHISH
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
hyperliquid.my.id is a phishing page that posed as Hyperliquid, the on-chain perpetuals exchange, and showed nothing but the brand name "Hyperliquid" as its page title. It targeted Hyperliquid traders who might mistake a lookalike address for the real app. PhishDestroy first flagged it on 2026-10-11. The site went offline on 2026-10-19, when its DNS stopped resolving.
Hyperliquid users trade by connecting a self-custody wallet, so a convincing copy of the interface is a natural trap. Pages like this typically ask the visitor to connect a wallet and then request a signature, a token approval or a fake "verification" step. Some ask for the recovery phrase outright. Any of these hands the attacker control over funds, and the victim's assets can be moved out of the wallet with no way to reverse the transfers.
On 2026-10-16, five of 92 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That count is modest, but the crypto-specific defenses carry more weight here. MetaMask and the SEAL blocklist both list it alongside PhishDestroy, and Spamhaus places it in its DBL under the phishing category. Four AlienVault OTX pulses also reference the domain, which shows other researchers tracked it independently.
The domain was registered on 2026-09-12 through PT Web Media Technology Indonesia, 29 days before PhishDestroy detected it. That gap fits a site that was set up and then promoted to targets shortly afterward. It was hosted on Amazon network space in the US. Its Let's Encrypt certificate gave it a padlock icon, which proves only that the connection was encrypted, not that the site was genuine.
If you connected a wallet to this site, use a token-approval checker to revoke any permissions it may have obtained, and move remaining funds if you signed anything you did not understand. If you typed in a seed phrase, treat that wallet as compromised. Create a new wallet on a clean device and transfer everything to it immediately. In future, reach Hyperliquid only through a bookmarked official address. Defenders should block the domain at DNS and proxy level and keep watching for re-registration or sibling lookalikes.
Last checked
Edge-IP 声誉不属于此域。
Location describes the IP network.
61496b37d29cfa5aee5f6cd7ad61e30cc84b21fae9d6e4cc34a4b8c5c5fdf0ccSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.hyperliquid.my.idDomain recordThe original observation time is not recorded for these hostnames.
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
可访问→不可用
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
protected→redirected
http_redirect
未知→protected
http_access_restricted · access_restriction
未知→redirected
http_redirect
No threat flag
View source5/92 engine detections
View source4 community references
View sourcehyperliquid.my.id
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
hyperliquid.my.id
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 ↗
hyperliquid.my.id)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.