hyperliquid[.]so

PhishDestroy first observed hyperliquid.so on Aug 12, 2026. The hostname explicitly references Hyperliquid; stored content metadata identifies the same apparent target. Stored page analysis classifies the content as impersonation. Current evidence score: 88/100 (critical).

Positive findings are stored from 4 sources: VirusTotal, MetaMask, SEAL, and Spamhaus DBL. VirusTotal recorded 5 detections among 91 engines: alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar on Aug 19, 2026 at 03:11 UTC. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Aug 21, 2026 at 18:20 UTC. Spamhaus DBL: DBL_PHISH on Aug 14, 2026 at 06:30 UTC. Non-positive and contextual checks: AlienVault OTX listed 3 community pulse references (not vendor detections) on Aug 15, 2026 at 22:11 UTC. Google Safe Browsing returned no flag on Aug 15, 2026 at 22:10 UTC.

The collector marked the hostname reachable on Aug 20, 2026 at 22:15 UTC, but did not retain the HTTP response code. At collection time, the hostname resolved to 2.59.170.20 on AS49981 (WorldStream B.V.). The recorded endpoint location is Naaldwijk, NL. The stored server header is nginx/1.28.3 (Ubuntu). The evidence archive retains 1 visual capture from Cloudflare Radar; no page title was retained, so the captures preserve the landing-page appearance. TLS metadata lists Let's Encrypt as the certificate issuer with validity through Nov 8, 2026; checked Aug 14, 2026 at 07:02 UTC.

The content indicators and 4 positive source findings support the current Hyperliquid-themed impersonation classification.