VirusTotal
4 / 89 engine detections
Відкрити звіт“Debank™ : ( Home ) Exchange”
підробка під Aave: web-debonk.github.io — Останній відомий активний (HTTP 200). Зведення доказів: VirusTotal 4/89 (ChainPatrol, alphaMountain.ai, ESET…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
4 / 89 engine detections
Відкрити звітШкідливий
Відкрити звітno community references
Відкрити звітprovider verdict: clean
Відкрити звіт80/100
Відкрити звітNo threat flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
web-debonk.github.io is a phishing page that poses as DeBank, the DeFi portfolio dashboard, under the misspelled name "debonk". It is aimed at crypto users who search for DeBank or follow a shared link and assume they have reached the real service. PhishDestroy first saw it on 2026-09-07, and the page was still online with its content live on 2026-10-19.
The page presents itself as "Debank™ : ( Home ) Exchange", borrowing the DeBank name and a trademark symbol to look official, even though DeBank is a portfolio tracker rather than an exchange. Impersonation pages of this kind push visitors to connect a wallet, sign a transaction or type in a recovery phrase under the pretext of viewing balances or claiming something. Any of those steps can hand the operator control of the wallet or permission to move its tokens, and the theft is usually irreversible.
urlscan.io rated the page malicious and recognised DeBank as the imitated brand. On VirusTotal, 4 of 89 engines flagged it as of 2026-09-20: ChainPatrol, alphaMountain.ai, ESET and Forcepoint ThreatSeeker. That count is low, so many security tools may still let the page load without a warning. The domain is listed by PhishDestroy, MetaMask and SEAL, which means MetaMask users should see a block screen before the page opens.
The site is a free GitHub Pages project, so there was no domain to register. Spinning up a lookalike costs nothing and takes minutes. Traffic is served from Fastly's network in the US, the content delivery network behind GitHub Pages. The Let's Encrypt certificate is issued automatically to every such page, so the padlock in the browser proves nothing about legitimacy.
If you connected a wallet to this page, revoke every token approval and permission it may have obtained using a trusted approval checker, and move remaining funds to a new wallet if you signed anything you did not understand. If you typed your seed phrase here, treat the wallet as compromised and transfer assets to a freshly generated wallet immediately. Open DeBank only from a saved bookmark and check the spelling of the name before connecting. Defenders should block this github.io subdomain and report the repository to GitHub for removal. Watch for similar misspelled DeBank projects on the same platform.
Last checked
Репутація Edge-IP не пов’язана з цим доменом.
Location describes the IP network.
71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84github.comgithub.iogithubusercontent.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of web-debonk.github.io · checked Sep 7, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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
2→3
0→2
Доступний
No threat flag
View source4/89 engine detections
View sourceweb-debonk.github.io
View sourcePage captured
View sourceЗбережено 95 схожих доменів
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
web-debonk.github.io
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 ↗
web-debonk.github.io)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.