hyperliquid-en.xyz is a Hyperliquid impersonation page detected by PhishDestroy on 2026-10-21. Risk: critical (88/100). Registrar: PDR. Status: Last known active. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 2/92 engines flag it. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 2. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 24H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@publicdomainregistry.com.
The latest stored availability evidence still shows the domain reachable; 33 hours 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.
PhishDestroy’s intake AI automatically classified hyperliquid-en.xyz as malicious after a VirusTotal scan on 2026-10-19 returned one malicious and one suspicious detection. The domain was first observed by PhishDestroy on 2026-10-21, two days after registration, and the captured page displayed a Hyperliquid‑styled trading interface.
How the scam works
Fake‑exchange scams replicate the visual design and terminology of legitimate cryptocurrency platforms to convince victims to create accounts, link wallets, or send funds. Once a user provides credentials or authorises transactions, attackers can steal private keys, approve withdrawals or otherwise drain the victim’s assets.
Evidence
VirusTotal recorded two detections on 2026-10-19: one malicious (LevelBlue) and one suspicious (Forcepoint ThreatSeeker) out of 92 engines. urlscan captured the site on 2026-10-21 and gave an overall clean verdict, though its machine‑learning engine flagged it as malicious with a score of 98. Google Safe Browsing checked on 2026-10-21 and did not flag the URL. PhishDestroy’s internal blocklist marks the domain as malicious, while external blocklists showed zero matches on the same date. OTX reported no pulses for the domain on 2026-10-21.
Infrastructure
The domain was registered on 2026-10-19 through PDR Ltd. d/b/a PublicDomainRegistry.com. DNS resolution points to IP 104.21.10.206, which belongs to Cloudflare, Inc. in Canada and is protected by Cloudflare’s web application firewall. Detected technologies include Cloudflare and HTTP/3.
What to do
Users should avoid entering credentials or connecting wallets to this site; if any information was submitted, change associated passwords and monitor crypto accounts for unauthorized activity. Organizations should add hyperliquid-en.xyz to web filtering and intrusion‑detection rules and review logs for connections to the recorded IP address.
No. PhishDestroy classifies hyperliquid-en.xyz as a Hyperliquid impersonation page (risk: critical, 88/100); it was first detected on 2026-10-21. VirusTotal: 2/92 engines flag it. Treat the site as unsafe.
Is hyperliquid-en.xyz safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on hyperliquid-en.xyz. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used hyperliquid-en.xyz?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
RegistrationCreated Oct 19, 2026 (3d · Brand New!)—Expires Oct 19, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 21, 2026
DOM Analysisanalyzed Oct 21, 2026score 88/10012 brand signals
Submitted URLhttp://hyperliquid-en.xyz/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.67.164.128
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
braelyn.ns.cloudflare.com
emerson.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE2
Valid from
2026-10-19 10:00:12
Valid until
2027-01-17 10:00:11
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbf2526ca0698ba617fc54d86e709e56fc3961d5ddd3a4d55ef69095354a9051eCertificate names · 2 SANs
*.hyperliquid-en.xyz
hyperliquid-en.xyz
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-10-22 10:49:28 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-22 10:49:28 UTClast content: 2026-10-22 10:49:28 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-en.xyzDomain record
The original observation time is not recorded for these hostnames.
Technologies · 9 identified
S
Skolengo
CMSLMS
Skolengo is an Education Management Software developed by Kosmos Education.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Open Graph description:Trade crypto, commodities, indices, and more on Hyperliquid: 300+ perpetual and spot markets, fully onchain, non-custodial, 24/7.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · hyperliquid-en.xyz
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
PDF notice generated Notice text archived (800 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (DE):
German Criminal Code § 263 (Fraud)
German Criminal Code § 263a (Computer Fraud)
Telemedia Act (TMG)
German law prohibits fraud and computer-based deception.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
5 evidence signal groups linked1 stored notification recordsLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
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.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including hyperliquid-en.xyz)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
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?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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.
(DE)
