VirusTotal
11 / 91 engine detections
Відкрити звіт“Home - Backpack: Crypto Exchange & Wallet | Solana, Ethereum & BTC”
підробка під Aave: backoack.exchange — Доступно · доступ обмежено (HTTP 403). Зведення доказів: VirusTotal 11/91 (ChainPatrol, alphaMountain.ai, BitDefender…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
11 / 91 engine detections
Відкрити звітDBL_PHISH
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.
PhishDestroy threat report
The domain backoack.exchange was registered on February 21, 2026 through NiceNIC International Group Co., Limited and is currently listed as taken offline. DNS resolution points to the IP address 188.114.96.3, which belongs to Cloudflare, Inc. (AS13335) and is geolocated in the United States. The domain uses Cloudflare nameservers (alexa.ns.cloudflare.com and nolan.ns.cloudflare.com) and presents a TLS certificate issued by Google Trust Services under the WE1 label, indicating a valid HTTPS endpoint despite the site’s offline status. An HTTP request to the host returns a 403 Forbidden response, suggesting that the server is actively denying access to unauthenticated requests.
Threat intelligence shows that the site is flagged by three independent blocklists—PhishDestroy, MetaMask, and SEAL—and appears on three broader security blocklists. VirusTotal analysis reports three of ninety‑three scanning engines flagging the domain, reinforcing the suspicion of malicious activity. The page title observed during the brief scan reads "Home - Backpack: Crypto Exchange & Wallet | Solana, Ethereum & BTC," which aligns with the declared scam type of a crypto scam and indicates an attempt to present a cryptocurrency exchange or wallet service.
The domain is explicitly associated with brand impersonation of Aave, a well‑known DeFi platform, and therefore represents a targeted brand‑spoofing threat. While the current offline status limits immediate user exposure, the infrastructure choices—Cloudflare hosting, a Google‑issued TLS certificate, and the presence on multiple anti‑phishing blocklists—demonstrate a typical pattern used by actors to lend credibility to fraudulent crypto services. Defenders should continue to block the domain at network perimeter devices, update URL filtering policies to include the observed host and its IP range, and monitor for any re‑activation or similar domain registrations that mimic the Aave brand.
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.
65f388e36a1dcb17dcaef75be8bc68079c1c9acb09319553c8e50a42047ebfaeSaved 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
backoack.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/90315160-99a6-41eb-8be7-10a7d0940397
Доступний→Недоступно
11/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcebackoack.exchange
View sourceЗбережено 95 схожих доменів
Повідомив 1 учасник спільноти; уперше помічено 12.02.2026
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 ↗
backoack.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.