VirusTotal
6 / 89 engine detections
Abrir relatório“Trezor @Wallet* | us”
Imitação de Trezor: treeeziorrrrwleeett.gitbook.io — Acessível · acesso restrito (HTTP 403). Resumo das evidências: VirusTotal 6/89 (alphaMountain.ai…
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
6 / 89 engine detections
Abrir relatórioDBL_ABUSED_PHISH
no community references
Abrir relatórioprovider verdict: clean
Abrir relatórioNo threat flag
Abrir relatórioResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
treeeziorrrrwleeett.gitbook.io is a phishing page that impersonated Trezor, the hardware wallet maker, and targeted Trezor owners. The page was published on GitBook, a public documentation platform. PhishDestroy first flagged it on 2026-09-16. It went offline on 2026-09-23, and the content has been blocked by the hosting provider. It was still down when last checked on 2026-10-19.
The page carried the title "Trezor @Wallet* | us". Its jumbled subdomain, a misspelled run of letters that loosely echoes "Trezor wallet", was built to look official in a search result or a forwarded link. Fake Trezor pages like this usually claim the wallet needs to be set up, verified, updated or recovered. They then ask for the 12- or 24-word recovery phrase, or push a counterfeit download. Anyone holding that phrase can rebuild the wallet on their own device and empty it. The hardware itself offers no protection once the seed has been typed into a web page.
On 2026-09-23, VirusTotal showed 6 of 89 engines flagging the address: alphaMountain.ai, Emsisoft, Kaspersky, Netcraft, PhishFort and Webroot. That count is modest, but the list includes phishing-focused services such as Netcraft and PhishFort, which supports the classification. Spamhaus lists the address in its Domain Block List as an abused domain used for phishing. It also appears on the PhishDestroy blocklist.
The 2014-03-30 registration date and the Cloudflare, Inc. registrar belong to gitbook.io itself, not to the scammer. The operator simply rented a free subdomain on a long-established, trusted platform. Traffic was served through Cloudflare's network, with the IP located in Canada. The TLS certificate came from Google Trust Services, so the padlock in the browser said nothing about whether the page was genuine. The page lasted about a week after PhishDestroy first saw it before going offline.
If you typed your Trezor recovery phrase into this page, treat the wallet as compromised. Set up a new wallet with a freshly generated seed and move any remaining funds to it immediately. If you installed anything the page offered, remove it and scan the computer before using it for crypto again. Trezor never asks for your recovery phrase online. Only download Trezor Suite from the official Trezor site, and only enter your seed on the device itself. Defenders should block the subdomain and watch for similar misspelled Trezor subdomains on documentation and site-builder platforms, reporting them to the platform for removal.
A reputação do Edge-IP não é atribuída a este domínio.
hugh.ns.cloudflare.comLocation describes the IP network.
f3e0d20bcdcb0f6afa89f62c0f4ef0ea0ddd7a7445d5cc7ae8b2e212568ea348gitbook.ioSaved 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
treeeziorrrrwleeett.gitbook.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconhecido→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Desconhecido→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Desconhecido→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Desconhecido→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Desconhecido→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Desconhecido→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Desconhecido→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Desconhecido→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Desconhecido→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Desconhecido→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Acessível→Indisponível
Acessível
No threat flag
View source6/89 engine detections
View sourcetreeeziorrrrwleeett.gitbook.io
View source74 domínios semelhantes armazenados
1 denúncia da comunidade
CategoriaIMPERSONATION
Brand abuse: impersonation, impersonating Trezor
Listed domains receive at least one abuse report; this entry has no retained notification history.
Se você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.
Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.
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 ↗
treeeziorrrrwleeett.gitbook.io)Mesmo que você não tenha todos os detalhes — registre uma ocorrência mesmo assim. Mesmo informações parciais ainda ajudam nas investigações.
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
Análise de ameaças usando lista de bloqueio armazenada, WHOIS, DNS e evidências de verificação pública
Digitalize agoraEnvie domínios suspeitos para nosso banco de dados de ameaças — proteja a comunidade
DenunciarRelatórios recentes de phishing e alterações de disponibilidade observadas
MonitorarMonitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo
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.