VirusTotal
5 / 91 engine detections
レポートを開く“403 Forbidden”
Jupiterなりすまし: fizjupiter.com — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 5/91 (alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Gridinsoft…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
5 / 91 engine detections
レポートを開くDBL_PHISH
3 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
fizjupiter.com is an impersonation phishing page built around the Jupiter brand. It targets crypto traders who expect the real Jupiter swap interface and may not notice the extra "fiz" prefix. PhishDestroy first flagged it on 2026-08-15. As of 2026-10-19 the site was still online and serving content.
Sites that copy Jupiter usually reproduce the familiar swap screen and prompt visitors to connect a wallet. They then push a transaction or signature request that looks like a routine swap, claim or verification. Signing it can hand an attacker token approvals or direct transfers, so the victim loses whatever assets the wallet holds. The page currently returns the title "403 Forbidden", while our classification is impersonation phishing based on the domain and the detections below.
Five of 91 VirusTotal engines flagged the domain as of 2026-10-06: alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That count is modest, but the wallet-security blocklists agree with it. MetaMask and SEAL both list the domain alongside PhishDestroy, so many wallet users will see a warning before the page loads. Spamhaus DBL lists it under its phishing category. Three AlienVault OTX pulses reference the domain, which shows other researchers have tracked it independently.
The domain was registered on 2026-08-14 through HOSTINGER operations, UAB, and PhishDestroy picked it up the following day. That one-day gap fits a lookalike domain that was bought and put to use almost immediately. It resolves to 76.13.73.5 on Hostinger International Limited's network in the US. Its free Let's Encrypt certificate means the browser padlock says nothing about whether the site is legitimate.
Do not connect a wallet to fizjupiter.com, and reach Jupiter only through a bookmark you saved yourself. If you connected a wallet and signed anything, use a token-approval checker to revoke the permissions you granted. Move any remaining funds to a fresh wallet if you approved unfamiliar transactions or entered a seed phrase. Never type a recovery phrase into a site, since no swap service ever needs one. Defenders should block the domain and its IP at DNS and proxy level, and search their logs for users who reached it after 2026-08-14.
Last checked
nebula.dns-parking.comLocation describes the IP network.
68b26c85fec8c0435995ff81fc48603a769de86ab343ab17a72aad6d982c64b1www.fizjupiter.comSaved 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.fizjupiter.comDomain 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.
alive_content: raw=ok; http=200; via=https_proxy; server=LiteSpeed
fizjupiter.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→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
不明→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
利用不可→到達可能
到達可能→利用不可
到達可能
5/91 engine detections
View source3 community references
View sourceNo threat flag
View sourcefizjupiter.com
View sourceListed 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 ↗
fizjupiter.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.