VirusTotal
15 / 91 engine detections
レポートを開く“Home - Backpack: Crypto Exchange & Wallet | Solana, Ethereum & BTC”
Solanaなりすまし: baxkpack.exchange — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 15/91 (ChainPatrol, alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
15 / 91 engine detections
レポートを開くSuspicious
レポートを開くno community references
レポートを開く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
The domain baxkpack.exchange was registered on February 21 2026 through NiceNIC International Group Co., Limited. It resolves to 172.67.179.206, an address owned by Cloudflare (AS13335) located in the United States. The site served HTTP 403 responses and employed HSTS, HTTP/3, and a React front‑end, indicating a modern web stack. SSL is issued by Google Trust Services under the WE1 intermediate, confirming a valid TLS certificate. The page title observed in the capture reads “Home - Backpack: Crypto Exchange & Wallet | Solana, Ethereum & BTC”, explicitly referencing Solana and other blockchain assets, which aligns with the declared brand impersonation of Solana and the categorisation as a crypto scam.
The domain appears on three independent security blocklists and has been flagged by PhishDestroy, MetaMask, and SEAL. VirusTotal analysis shows four of ninety‑three scanners labeling the host as malicious. Nameservers are set to alexa.ns.cloudflare.com and nolan.ns.cloudflare.com, typical of Cloudflare‑hosted domains. The current status is offline, suggesting the site has been taken down or is no longer serving content. Uncertainty remains regarding the exact malicious payload or user‑interaction flow because the site content has not been captured beyond the title.
No additional indicators such as phishing page screenshots, credential‑stealing scripts, or cryptocurrency address harvesting have been disclosed. Defenders should immediately add baxkpack.exchange to deny lists across web filtering, DNS sinkholing, and email security gateways. Monitoring for newly registered domains that reuse the same registrar, similar naming patterns, or identical Cloudflare IP ranges is advisable. Updating endpoint and browser protection signatures to reflect the four VirusTotal detections will improve detection of any residual components.
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.
Edge-IP の評判はこのドメインに起因しません。
nolan.ns.cloudflare.comLocation describes the IP network.
930ff52907e8245f42e22c15b7c47ae36bd38c8e7b7b7666878a4a43500d9b81Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
baxkpack.exchange
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
利用不可→到達可能
https://radar.cloudflare.com/scan/3c43c7dc-39dc-4894-80da-d0c87f978db0
到達可能→利用不可
到達可能→利用不可
15/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcebaxkpack.exchange
View source保存された類似ドメイン:118 件
118 件中 100 件を表示
コミュニティの 1 人が報告・初回確認 2026年2月12日
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 ↗
baxkpack.exchange)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.