VirusTotal
1 / 93 engine detections
Open reportclaim.hyperslane.network is a Cosmos impersonation page detected by PhishDestroy on 2026-02-26. Risk: high (65/100). Status: Content unavailable. Hosting: CLOUDFLARENET, US. VirusTotal: 1/93 engines flag it. Do not enter credentials or connect a wallet.
“Hyperlane - Token pre-registration”
1 / 93 engine detections
Open report1/100
Open reportMalicious
Open reportno community references
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain claim.hyperslane.network is a cryptocurrency phishing site engaged in brand impersonation, specifically targeting the Cosmos ecosystem. It presents itself as a token pre-registration page for Hyperlane but is designed to deceive users into disclosing sensitive information or transferring assets under false pretenses. No drainer kit was identified, and the site is currently taken offline.
Technical indicators confirm the elevated risk. claim.hyperslane.network was flagged by 1 of 95 VirusTotal security vendors, including Gridinsoft, which assigned a trust score of 0/100. The domain appears on 2 security blocklists (PhishDestroy and ScamSniffer) and is not flagged by Google Safe Browsing. It was created on February 21, 2026, and resolves to the IPv6 address 2a06:98c1:3121::3, hosted on Cloudflare’s network (AS13335, US). The SSL certificate is issued by WE1, and the observed page title was 'Hyperlane - Token pre-registration'. Scamadviser assigned a trust score of 1/100.
Users who interacted with claim.hyperslane.network should immediately revoke any token approvals granted to unknown contracts and consider transferring funds to a new wallet. Enable two-factor authentication on all accounts and monitor for unauthorized transactions. Report the domain to platforms like Google Safe Browsing, PhishTank, or the impersonated brand’s security team to aid in takedown efforts.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 019868b7-3efe-73ef-8316-bf6c53b6f9ae |
|---|---|
| Final url | https://claim.hyperslane.network/ |
| Status | 200 |
| Ip | 2a06:98c1:3121::3 |
| Contacted domains | [
"bsc-dataseed4.bnbchain.org",
"binance.nodereal.io",
"cdn.jsdelivr.net",
"api.ipify.org",
"bsc-dataseed3.bnbchain.org",
"bsc-dataseed.bnbchain.org",
"cdnjs.cloudflare.com",
"pulse.walletconnect.org",
"fonts.googleapis.com",
"api.web3modal.org",
"secure.walletconnect.org"
] |
| Contacted IP addresses | [
"2606:4700::6810:aee2",
"52.48.192.107",
"172.67.74.152",
"52.209.240.73",
"52.210.90.9",
"2606:4700::6811:180e",
"2a06:98c1:3121::3"
] |
| Asns | [
"13335",
"16509"
] |
| Countries | [
"IE"
] |
| Document hash | e621ddd0e84faa584ad6f21506789fbc20fe6c1137ad7c8691212dad042e96bf |
| Script hashes | [
"3aa3296074f5435ab3f5a170ff402b2c003ced735ddb3cf8ce80dab8736c5076"
] |
| Globals | [
"f431e233a95eba",
"b878df90",
"c024feac6b53b2",
"d7a814f1",
"b8d75d8b8065",
"f5e1e9046b59",
"_qtwjl",
"createSetAuthorityInstruction",
"AuthorityType",
"serialize",
"BN",
"sha256",
"Buffer",
"sendAndConfirmTransaction",
"Connection",
"Transaction",
"SystemProgram",
"PublicKey",
"LAMPORTS_PER_SOL",
"SYSVAR_CLOCK_PUBKEY",
"Keypair",
"getAssociatedTokenAddress",
"AccountLayout",
"TOKEN_PROGRAM_ID",
"ASSOCIATED_TOKEN_PROGRAM_ID",
"createAssociatedTokenAccountInstruction",
"createTransferInstruction",
"TransactionInstruction",
"axios",
"_utujdm",
"global",
"process",
"litPropertyMetadata",
"reactiveElementVersions",
"litHtmlVersions",
"litElementVersions",
"_llsodonbwsfzmelyv",
"CoinbaseWalletSDK",
"CoinbaseWalletProvider",
"WalletLink"
] |
| Cookies | [
"gacfxdn1x7"
] |
| Tls | {
"san": [
"hyperslane.network",
"*.hyperslane.network"
],
"cipher": "AES_128_GCM",
"issuer": "WE1",
"subject": "hyperslane.network",
"protocol": "QUIC",
"valid_to": "2025-10-26T21:51:27Z",
"valid_from": "2025-07-28T20:54:00Z"
} |
| Domain age days | 246 |
| Apex age days | 250 |
| Tls age days | 4 |
| Tls valid days | 90 |
| Requests | 80 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 93,
"malicious": true
},
"overall": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"genericcrypto"
],
"malicious": true,
"categories": [
"phishing"
]
},
"urlscan": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"Generic Crypto"
],
"malicious": true,
"categories": [
"phishing"
]
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html; charset=UTF-8",
"x-powered-by": "Express",
"cross-origin-resource-policy": "cross-origin"
} |
No. PhishDestroy classifies claim.hyperslane.network as a Cosmos impersonation page (risk: high, 65/100); it was first detected on 2026-02-26. VirusTotal: 1/93 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on claim.hyperslane.network. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
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.
Last checked
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
hyperslane.network*.hyperslane.networkSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='claim.hyperslane.network', port=80): Max retries exceeded with url: / (Caused by NewConnec
claim.hyperslane.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
1/93 engine detections
View sourceNo threat flag
View sourceclaim.hyperslane.network
View sourceReported by 1 community member, first seen Aug 2, 2025
Listed domains receive at least one abuse report; this entry has no retained notification history.
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
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
claim.hyperslane.network)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
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.