VirusTotal
5 / 92
“Hyperliquid”
hyperliquid.my.id was first observed on 2026-10-11, and a blocklist check on 2026-10-12 recorded its entry on both the MetaMask and SEAL blocklists. The domain also has a documented internal listing from PhishDestroy, adding to the context of its recorded security profile.
On 2026-10-12, MetaMask and SEAL both included hyperliquid.my.id in their external blocklists. VirusTotal checked the domain on 2026-10-10, recording 5 detections out of 92 total scanners. OTX referenced the domain in four pulses as of 2026-10-12. PhishDestroy internally listed the domain on 2026-10-12, and the domain was first observed on 2026-10-11.
The VirusTotal record provides a scanner-based measurement of detections, which can be compared to the blocklist entries from MetaMask and SEAL. OTX documents pulse activity, offering a different type of intelligence signal, while PhishDestroy contributes an internal listing. These sources collectively capture a range of security-related observations for hyperliquid.my.id within a short period.
For hyperliquid.my.id, it is important to preserve the MetaMask and SEAL blocklist records for future reference. VirusTotal detection results should be compared with subsequent scans to monitor for any changes. OTX and PhishDestroy records can supplement ongoing security reviews and inform future monitoring strategies.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
VercelScanner note: redirect: raw=redirect_308; http=308; via=https_proxy; location=https://www.hyperliquid.my.id/; server=Vercel
Edge-IP reputation is not attributed to this domain.
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.
216.198.79.1. 11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive