VirusTotal
7 / 91 engine detections
レポートを開く“Jupiter”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@qweb.nl.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Jupiterなりすまし: jupiter.boost.community — 最後に確認されたアクティブな状態 (HTTP 302). 証拠の概要: VirusTotal 7/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
7 / 91 engine detections
レポートを開く3 threat-system alerts
レポートを開くno 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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Nextron YARA rules | bulsis.net/go/3115960?subid1=cloudfine.quest |
malware | Unique code from Jetriz, Swid & Jeniva of the Tetris framework |
| DNS4EU | fveyha6b.cloudfine.quest |
malicious | Sinkholed |
| DNS4EU | bulsis.net |
malicious | Sinkholed |
PhishDestroy threat report
jupiter.boost.community poses as Jupiter, the Solana swap aggregator, and its page title simply reads "Jupiter" to pass as the real app in a browser tab or a shared link. It targets Solana users who expect to trade, stake or claim tokens through Jupiter. PhishDestroy first flagged it on 2026-08-26. As of 2026-10-19 the site was still online and its content now redirects elsewhere, so the lure remains live.
Victims usually arrive through a link promising an airdrop, a token claim or a better swap, then land on a page styled as Jupiter. The page asks them to connect a wallet and approve what looks like a routine swap or claim. In practice, signing that request can authorize a transfer of SOL and other tokens out of the wallet, and some variants also prompt for a recovery phrase, which hands over the whole wallet. Once a transaction is signed on-chain it cannot be reversed.
Seven of 91 VirusTotal engines classify the domain as malicious: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, Netcraft and SOCRadar, as of 2026-10-06. That is a modest count, so many security products will still let the page load without a warning. Wallet-side protection is stronger, because the domain appears on the MetaMask and SEAL blocklists as well as PhishDestroy's.
The parent domain boost.community was registered on 2019-08-07 through Hosting Concepts B.V. d/b/a Registrar.eu, about seven years before this Jupiter subdomain was detected. Because of that gap, the age of the parent domain says little about how long the phishing page has existed. The site is hosted on Infopact Netwerkdiensten B.V. in the Netherlands and uses a free Let's Encrypt certificate, so the padlock in the address bar only means the connection is encrypted, not that the site is legitimate.
If you connected a wallet here, open your wallet's connected-apps settings, disconnect the site and revoke any token delegations or approvals you granted. Then check your transaction history for transfers you did not make. If you typed in your recovery phrase, treat the wallet as compromised and move any remaining assets to a newly created wallet at once. Reach Jupiter only through a bookmark you saved yourself. Defenders should block jupiter.boost.community and keep an eye on other subdomains under boost.community for new lures.
Last checked
For the registrable domain boost.community behind this subdomain, 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.
ns3.forcemedia.nlLocation describes the IP network.
8041ba70764ef6224aa86ca8881488440e2e37a9da17e437fc684e3fe829e5e9boost.communitywww.boost.communitywww.jupiter.boost.communitySaved 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.jupiter.boost.communityDomain recordThe original observation time is not recorded for these hostnames.
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://jupiter.boost.community/login; server=nginx
jupiter.boost.community
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
0→4
到達可能
7/91 engine detections
View sourceNo threat flag
View sourcePD-20260826-DB2418
jupiter.boost.community
View sourcePage captured
View sourcePD-20260826-DB2418 Recipient: abuse@qweb.nl アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
jupiter.boost.community)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.