VirusTotal
10 / 89 engine detections
レポートを開く“Jumper.finance for sale | Spaceship.com”
MetaMaskなりすまし: jumper.finance — 最後に確認されたアクティブな状態 (HTTP 302). 証拠の概要: VirusTotal 10/89 (ChainPatrol, alphaMountain.ai, BitDefender, CRDF, Fortinet); Spamhaus…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
10 / 89 engine detections
レポートを開くDBL_PHISH
3 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
jumper.finance borrows the name of Jumper, a cross-chain swap and bridge service, to catch DeFi users who guess or mistype the address. PhishDestroy classifies it as an impersonation phishing page and first flagged it on 2026-09-01. As of 2026-10-19 the domain was still alive and redirecting visitors elsewhere. The page title currently reads "Jumper.finance for sale | Spaceship.com", a domain-marketplace listing, while our classification is impersonation phishing.
Lookalike bridge and swap domains rely on users already trusting the brand. A visitor lands on a page that resembles the real interface, clicks to connect a wallet, and is asked to sign a transaction or token approval presented as a routine swap. That signature can hand the operator permission to move the victim's tokens, and assets leave the wallet without any further prompt. A domain that redirects can send traffic to a parking page one day and a cloned dApp the next, so a harmless-looking visit does not make the domain safe.
On 2026-09-15, 10 of 89 VirusTotal engines flagged the domain, including ChainPatrol, alphaMountain.ai, BitDefender, CRDF, Fortinet, G-Data, Kaspersky and LevelBlue. That count is modest, but it includes crypto-focused detection alongside major antivirus vendors. Spamhaus lists the domain in its DBL under the phishing category. The MetaMask and SEAL blocklists carry it next to PhishDestroy, so many wallet users get a warning before the page loads. Three AlienVault OTX threat pulses reference it.
The domain was registered through Dynadot Inc on 2026-07-08, about eight weeks before PhishDestroy caught it. It resolves to Amazon cloud hosting in the United States. Its certificate comes from Let's Encrypt, so the padlock in the browser says nothing about whether the site is legitimate.
If you connected a wallet or signed anything on jumper.finance, open a token-approval checker right away and revoke every allowance you granted through it. Then move any remaining funds to a fresh wallet if you approved unknown contracts or entered a seed phrase. Never type a recovery phrase into any bridge or swap site. Reach Jumper only through a bookmark you have verified, not search ads or links. Defenders should block the domain at DNS and proxy level, add it to wallet and email filters, and keep watching it while it stays live and redirecting.
Last checked
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.
launch2.spaceship.netLocation describes the IP network.
6d22cf5dcefd889861e5de420bca9f7eaad3c62e26588c942f3f1e782c7369b8www.jumper.financeSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.jumper.financeDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of jumper.finance · checked Sep 15, 2026
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.
redirect: raw=redirect_302; http=302; via=https_proxy; location=https://domains.atom.com/lpd/name/jumper.finance; server=openresty
jumper.finance
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
live_content→redirected
http_redirect
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
利用不可→到達可能
到達可能→利用不可
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→inactive
domain_for_sale · parking_or_lifecycle_page
不明→inactive
domain_for_sale · parking_or_lifecycle_page
不明→inactive
domain_for_sale · parking_or_lifecycle_page
利用不可→到達可能
到達可能→利用不可
到達可能
3 community references
View sourceNo threat flag
View source10/89 engine detections
View sourcejumper.finance
View source保存された類似ドメイン:79 件
コミュニティ報告:2 件
カテゴリPHISHING
angel drainer
“angel drainer”
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
jumper.finance)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.