VirusTotal
6 / 91 engine detections
Abrir relatório“PHP 7.4.33 - phpinfo()”
Imitação de Trezor: trezor.locker — Conteúdo indisponível. Resumo das evidências: VirusTotal 6/91 (alphaMountain.ai, Chong Lua Dao, Forcepoint ThreatSeeker…
A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.
6 / 91 engine detections
Abrir relatórioScan report
Abrir relatório4 community references
Abrir relatórioprovider verdict: clean
Abrir relatório80/100
Abrir relatórioNo threat flag
Abrir relatórioNo malicious flag
Abrir relatórioResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
trezor.locker is a phishing domain that borrows the Trezor name to target owners of Trezor hardware wallets. PhishDestroy first flagged it on 2026-08-14, a single day after registration. The site has been offline since 2026-09-10, and its DNS was still inactive when last checked on 2026-10-19.
Trezor impersonation sites typically copy the brand's look and push visitors through a fake setup, firmware update or "wallet recovery" step. That step asks for the 12- or 24-word recovery seed. Anyone who types those words hands over full control of the wallet, and the attacker can then empty it from any device. The page title served on the domain read "PHP 7.4.33 - phpinfo()", a default server diagnostics page, while PhishDestroy classified the domain as a Trezor impersonation.
Detection was limited but came from several independent sources. VirusTotal showed 6 of 91 engines flagging the domain on 2026-08-25: alphaMountain.ai, Chong Lua Dao, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. Besides PhishDestroy, the wallet-focused blocklists of MetaMask and SEAL list it, so users of those protections were warned. It also appears in 4 AlienVault OTX threat pulses, which means other researchers tracked it as well.
The domain was registered on 2026-08-13 through Gname.com Pte. Ltd. and was caught the next day. That fast turnaround points to a disposable domain registered for a short campaign. It resolved to 43.108.86.51 on the Alibaba (US) Technology Co., Ltd. network, with the server located in South Korea. The ".locker" extension paired with the brand name is meant to sound like secure storage, a lure aimed at security-minded hardware wallet users.
If you entered your Trezor recovery seed on this site, treat that wallet as compromised. Set up a new wallet with a freshly generated seed and move any remaining funds to it right away. Trezor never asks for your seed on a website, so any page that does is a scam. If you only visited and entered nothing, you need no further action beyond avoiding the domain. Defenders should block trezor.locker at DNS and proxy level and add lookalike Trezor domains on unusual extensions to their monitoring.
Last checked
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.
a.share-dns.coma3.share-dns.comb.share-dns.netb3.share-dns.netLocation describes the IP network.
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.
trezor.locker
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
Desconhecido→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Acessível→Indisponível
0→4
Acessível
6/91 engine detections
View source4 community references
View sourceNo threat flag
View sourcePD-20260814-781FB2
trezor.locker
View sourcePage captured
View source74 domínios semelhantes armazenados
PD-20260814-781FB2 Recipient: abuse@alibaba-inc.com Registrar: Gname.com Pte. Ltd. (Singapore) Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
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 ↗
trezor.locker)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.