PhishDestroy’s automated assessment classified hyperliquid-btc.com as an impersonation phishing page targeting the Hyperliquid brand. The recorded page title reads “Hyperliquid | Exchange Platform” and the domain was first seen by PhishDestroy on 2026-10-21, two days after its registration on 2026-10-19, with an HTTP 200 response recorded on that date.
How the scam works
Impersonation phishing sites copy the visual design, branding and naming of a legitimate service to lure users into entering login credentials, private keys, or approving wallet transactions. Victims who trust the familiar brand may inadvertently disclose sensitive information that can be harvested for unauthorized account access or fund transfers.
Evidence
VirusTotal scanned the domain on 2026-10-21 and reported four detections across 92 engines, including one malicious label and three suspicious labels from alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet and SOCRadar. Google Safe Browsing checked the domain on the same day and did not flag it. External blocklists MetaMask and SEAL listed the domain, Spamhaus DBL marked it as spam, and OTX recorded four pulses referencing it, all on 2026-10-21. URLScan captured the site on 2026-10-21; its engine verdict marked it malicious with a score of 99, while the overall score was reported as 0.
Infrastructure
The domain was registered with Hosting Concepts B.V. d/b/a Registrar.eu on 2026-10-19 and set to expire on 2027-10-19. It resolved to the recorded IP 130.12.180.154, which was listed under the network Omegatech LTD in the Netherlands. A Let’s Encrypt TLS certificate for hyperliquid-btc.com was issued on 2026-10-20 and was valid until 2027-01-18. The server identified itself as openresty running on an Nginx/OpenResty stack, with ports 22, 80, 443 and 3000 observed open at the time of capture.
What to do
Users should avoid entering any Hyperliquid credentials or approving wallet connections on this domain; if credentials were entered, they should be changed immediately. Organizations should block hyperliquid-btc.com in web filters, monitor outbound traffic for connections to the domain, and review logs for any access attempts. Security teams should add the domain to threat‑intel feeds and apply appropriate incident‑response procedures if any credential or wallet data was submitted.
DOM Analysisanalyzed 2026年10月21日score 10/1004 brand signals
Submitted URLhttp://hyperliquid-btc.com/
Favicon Hash
ケース ID
Observed page title
Hyperliquid | Exchange Platform
Automated brand references
EthereumLedgerNearSolana
TLS証明書
発行者 YE1· stored validity ends in 89 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
130.12.180.154
Network ASN
AS202412
Organization
Omegatech LTD
Observed location
Amsterdam, NL
Server header
openresty
ネームサーバー 3
a.dnspod.com
b.dnspod.com
c.dnspod.com
Location describes the IP network.
TLS証明書
Issuer
YE1
Valid from
2026-10-20 17:34:44
Valid until
2027-01-18 17:34:43
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintffed0b2c76f31f655ff9a3c970b0cba8f61c29ebee2245fd7b4e08be855fb590Certificate names · 2 SANs
hyperliquid-btc.com
www.hyperliquid-btc.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-21 11:03:01 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-21 08:32:56 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.hyperliquid-btc.comDomain record
The original observation time is not recorded for these hostnames.
使用技術 · 2 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
SOCRadar
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of hyperliquid-btc.com· checked Oct 21, 2026
85
Needs Work
Performance
FCP
3.32s
First Contentful Paint
LCP
3.32s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.32s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Stored Capture Evidence 1 snapshot
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
Archived HTTP responseHTTP 200
Requested URL:http://hyperliquid-btc.com/
Final URL:https://hyperliquid-btc.com/
Hyperliquid | Exchange Platform
Hyperliquid DEX lands Pumpfun perps, files an SEC comment letter and keeps burning HYPE. Inside the Hyperliquid exchange, HIP-3 markets and the future of Hyperliquid crypto.
対応 HTTP 200
HTML body 35.4 KB
Compressed 12.0 KB
Links 13 internal · 0 external
Selected response headers
Server: openresty
Content-Type: text/html
Content-Encoding: gzip
HSTS: not observedDNSSEC: not observedWAF / firewall: not observedCloaking flag: not observed
Open Graph title:Hyperliquid | Exchange Platform
Open Graph description:Pump fun perps, an SEC letter and daily HYPE burns. Why the Hyperliquid exchange is setting the pace for decentralized trading in 2026.
Twitter card:summary_large_image
Saved response-header values · 9
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Wed, 21 Oct 2026 08:33:17 GMT
Etag
W/"6ad7b4eb-8d82"
Last-Modified
Tue, 20 Oct 2026 18:37:31 GMT
Server
openresty
Transfer-Encoding
chunked
Vary
Accept-Encoding
Values retained by the collector; long values may be shortened during collection.
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.
Stored observation history4
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
詐欺による金銭の返還を装った詐欺 — 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.
(RO)
