The domain app-hyperliquid.exchange was observed hosting a page titled "37.323 | HYPE/USDC | Hyperliquid". Although the page title references the Hyperliquid platform, threat intelligence attributes the site to a brand‑impersonation campaign targeting the monad brand. The site is registered through Cloudflare, Inc. and uses the Cloudflare name servers angela.ns.cloudflare.com and rory.ns.cloudflare.com. DNS resolution points to the IP address 104.21.21.114, which belongs to AS13335 Cloudflare, Inc. and is geolocated in the United States.
No TLS certificate is presented, indicating the site is served without HTTPS. VirusTotal scans show that three out of ninety‑five security vendors flagged the domain as malicious, and the domain appears on one external blocklist. PhishDestroy has also listed the domain as blocked. The current HTTP status is offline, and the domain is no longer reachable.
The combination of a crypto‑related page title, the lack of TLS, Cloudflare‑based hosting, and the presence on multiple security blocklists aligns with a crypto‑scam impersonation of monad. Defenders should add 104.21.21.114 to network‑level deny lists, enforce DNS sinkholing for the domain, and monitor for any future re‑registration of the same second‑level domain. Continuous observation of Cloudflare name‑server activity and rapid re‑deployment of blocklist entries is recommended, as threat actors often reuse the same infrastructure for new impersonation campaigns.
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.
Accreditation is a contract, not a safety certification.
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.
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
Chong Lua Dao
Fortinet
Gridinsoft
Registration & observation details1
Availability observations
Last reachable observation
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='app-hyperliquid.exchange', port=80): Max retries exceeded with url: / (Caused by ConnectTi
app-hyperliquid.exchange
已保存的结果
无法访问
Stored observation history1
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(US)
