VirusTotal
9 / 91 engine detections
レポートを開く“Home - Backpack: Crypto Exchange & Wallet | Solana, Ethereum & BTC”
Aaveなりすまし: bsckpack.exchange — 最後に確認されたアクティブな状態 (HTTP 301). 証拠の概要: VirusTotal 9/91 (alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, Fortinet, G-Data)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
9 / 91 engine detections
レポートを開く23 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
Analysis conducted on July 22, 2026 identifies bsckpack.exchange as an active brand‑impersonation infrastructure targeting the Aave community. The domain was registered on February 21, 2026 through NiceNIC International Group Co., Limited and is hosted behind Cloudflare (ASN 13335). DNS resolution points to IP 172.67.179.206, which GeoIP attributes to the United States. The authoritative nameservers are alexa.ns.cloudflare.com and nolan.ns.cloudflare.com, confirming the use of Cloudflare’s DNS service. HTTP inspection returns a 301 redirect, and the TLS certificate is issued by Google Trust Services under the WE1 intermediate, indicating a valid‑looking HTTPS endpoint.
The front‑end stack reports React, HSTS enforcement, Cloudflare Browser Insights and HTTP/3, consistent with a modern web application that could host a counterfeit crypto exchange interface. The page title presented by the server is “Home - Backpack: Crypto Exchange & Wallet | Solana, Ethereum & BTC”, which aligns with the declared scam type “Fake Exchange”. Reputation checks show the domain appears on one security blocklist and is explicitly listed by PhishDestroy. Automated scoring from Gridinsoft assigns a trust score of 0 / 100, reflecting extreme suspicion. VirusTotal analysis registers detections from 2 of 93 scanning engines, confirming that at least two independent vendors consider the site malicious.
No additional intelligence such as OTX tags or Safe Browsing entries is currently available. The evidence collectively points to a high‑risk impersonation campaign that likely harvests credentials or funds from users seeking to trade Aave‑related assets. Uncertainty remains regarding the specific phishing page content and any associated command‑and‑control infrastructure, as no visual inspection has been performed. Defenders should immediately block DNS resolution for bsckpack.
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.
aa64af4e689d1f5eebd6430e2535f7103588aac9ac0f5b39e74a3e7f9b887420Saved 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.
redirect: raw=redirect_301; http=301; via=https_proxy; location=https://bacbcack.exchange/; server=cloudflare
bsckpack.exchange
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
不明→redirected
http_redirect
redirected
http_redirect
利用不可→到達可能
https://radar.cloudflare.com/scan/9c7f5887-f0fd-40c4-a570-b24d43f3368f
到達可能→利用不可
No threat flag
View source23 community references
View source9/91 engine detections
View sourcePage captured
View sourcebsckpack.exchange
View source保存された類似ドメイン:95 件
コミュニティの 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 ↗
bsckpack.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.