VirusTotal
13 / 91
The domain leapwallet.network was registered on May 13, 2026 through NameSilo, LLC and currently resolves to the IPv4 address 38.132.122.144. Analytical feeds have placed the domain on three independent security blocklists, and it is actively blocked by PhishDestroy, MetaMask, and SEAL, indicating that multiple defensive platforms have observed malicious activity associated with the host. VirusTotal scans show that 13 of 91 security vendors have flagged the domain, reinforcing the suspicion that the infrastructure is being used for illicit purposes.
The threat classification supplied is a crypto drainer, a category that typically targets cryptocurrency wallets by attempting to harvest private keys or redirect transactions. No public page title, SSL certificate details, or HTTP response codes have been disclosed, so the exact content served by the site remains unverified. However, the convergence of recent domain creation, a dedicated IP address, blocklist presence, and multi‑vendor detections suggests a purpose‑built operation rather than an incidental compromise.
Defenders should add leapwallet.network to DNS and URL filtering policies, monitor outbound connections to 38.132.122.144, and consider extending threat‑intel feeds to include any newly observed subdomains or related IPs. Continuous re‑scanning of the domain with sandbox and endpoint tools is advised to capture any payloads that may be delivered in future interactions. Given the high risk rating and active status, organizations handling cryptocurrency assets should treat any communication from this domain as malicious and block it at the network perimeter.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='leapwallet.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
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.
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.
Location describes the IP network.
38.132.122.144. 13 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.
79 stored lookalike domains
Reported by 1 community member, first seen Jun 10, 2026
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