VirusTotal
18 / 89 engine detections
Відкрити звіт“WalletConnect™ | Official Home Site”
фішинг сид-фраз: counntktwalt.gitbook.io — Останній відомий активний (HTTP 307). Зведення доказів: VirusTotal 18/89 (ChainPatrol, alphaMountain.ai…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
18 / 89 engine detections
Відкрити звітШкідливий
Відкрити звіт15/100
Відкрити звіт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
This GitBook-hosted page masquerades as the official WalletConnect site, targeting cryptocurrency wallet holders who may be searching for wallet connection help or support. PhishDestroy first identified it on 2026-09-11, and as of 2026-10-18 the site remains fully alive and reachable. Its use of a legitimate documentation platform lends it a superficial air of credibility that makes it more dangerous to non-technical users.
The page presents itself under the title "WalletConnect™ | Official Home Site", borrowing the brand's name and trademark symbol to appear authoritative. Visitors are prompted to enter their wallet seed phrase — the 12- or 24-word recovery phrase that grants complete, irrevocable control over a wallet. Once submitted, those words are captured by the attacker, who can then drain every asset in the wallet and any linked accounts instantly and without further interaction from the victim.
VirusTotal flagged this domain across 18 of 89 scanning engines as of 2026-09-24, with detections from well-regarded vendors including BitDefender, ESET, Emsisoft, ChainPatrol, alphaMountain.ai, CyRadar, Ermes, and Chong Lua Dao. The domain appears on three independent blocklists: PhishDestroy, MetaMask, and SEAL, meaning major wallet software is already actively warning users away from it.
The underlying gitbook.io platform has been registered since 2014-03-30 through Cloudflare, Inc. as registrar. The site is served from a Cloudflare network address geolocated in Canada, and its TLS certificate is issued by Google Trust Services under the WE1 intermediate. These are all standard infrastructure providers; their involvement reflects the attacker's deliberate choice of reputable platforms to avoid easy takedown.
If you visited this page but did not enter anything, no immediate action is required beyond avoiding the site. If you typed in your seed phrase, treat your wallet as fully compromised: move all assets to a new wallet with a freshly generated seed phrase immediately, and do not reuse the exposed phrase anywhere. Security teams and platform defenders should add counntktwalt.gitbook.io to DNS and proxy blocklists and report the page to GitBook's abuse team for removal.
Last checked
Репутація Edge-IP не пов’язана з цим доменом.
Location describes the IP network.
d76aa1094c3d1ca19014ac824313b04e833289dec61fbca06aa6f92bad9464adgitbook.ioSaved 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 counntktwalt.gitbook.io · checked Sep 11, 2026
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.
counntktwalt.gitbook.io
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
17→18
16→17
15→16
14→15
12→14
7→12
4→7
3→4
No threat flag
View source18/89 engine detections
View sourcecounntktwalt.gitbook.io
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 ↗
counntktwalt.gitbook.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.