This domain, jumper.exposed, operates as a crypto drainer specifically designed to exploit WalletConnect integrations. The site deploys a Wallet Connect Abuse drainer kit, which intercepts and siphons cryptocurrency transactions by manipulating user interactions with decentralized applications. Victims are tricked into authorizing malicious smart contracts, resulting in unauthorized fund transfers from their wallets. The threat primarily targets users who rely on WalletConnect for secure connections between wallets and dApps, leveraging social engineering tactics to bypass security measures. Analysis indicates the domain was registered on July 28, 2025, through Devexpanse Ltd d/b/a Regery.com. It resolves to the IP address 172.67.155.162, hosted on Cloudflare's infrastructure (AS13335). The domain lacks an SSL certificate, a red flag for malicious activity. VirusTotal reports 10 out of 95 security vendors flagging this domain as malicious. Additionally, it appears on two security blocklists, including PhishDestroy and ScamSniffer, further confirming its malicious intent. The absence of legitimate branding and the use of Cloudflare suggest an attempt to obscure the true origin of the attack. Users who visited jumper.exposed should immediately revoke any active WalletConnect sessions and disconnect the domain from their wallets. It is critical to review all recent transactions for unauthorized activity and transfer remaining funds to a new, secure wallet. Monitor connected dApps for suspicious permissions and consider resetting wallet authorizations. If financial loss occurred, report the incident to relevant blockchain analytics services and local cybercrime authorities. Proactive measures, such as enabling transaction simulation tools and verifying domain authenticity before interaction, can mitigate future risks.
DOM Analysisanalyzed 2026年4月23日score 98/1001 brand signal
Submitted URLhttps://jumper.exposed/
ICANN OVERSIGHT
認定と RAA の背景
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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:09:05 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-05-16 21:48:40 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-16 21:48:40 UTC → 2026-09-30 16:14:55 UTC · 3,282.44hmidpoint estimate ≈ 2026-07-24 07:01:47 UTC · precision very low · basis bounded
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.
Last analyzed Previous stored snapshot: 8 detections
ADMINUSLabs
alphaMountain.ai
BitDefender
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
ソフォス
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
3282.44
Estimate basis
Bounded by observations
Estimate precision
very_low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='jumper.exposed', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
jumper.exposed
保存済みの結果
到達不能
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
あなたの仮想通貨取引所 — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(UA)
