trezor[.]locker

PhishDestroy first observed trezor.locker on Aug 14, 2026. The hostname explicitly references Trezor; stored content metadata identifies the same apparent target. Current evidence score: 66/100 (high).

Positive findings are stored from 2 sources: MetaMask and SEAL. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Aug 14, 2026 at 18:20 UTC. Non-positive and contextual checks: VirusTotal recorded 0 detections among 91 engines on Aug 14, 2026 at 17:30 UTC. URLQuery recorded no positive detection; no observation timestamp was retained. Google Safe Browsing returned no flag on Aug 14, 2026 at 17:26 UTC. URLScan captured the page on Aug 14, 2026 at 17:20 UTC. The 0/91 VirusTotal snapshot and the positive findings above are conflicting observations from different sources or collection times.

The collector marked the hostname reachable on Aug 14, 2026 at 17:20 UTC, but did not retain the HTTP response code. Registration records for the domain list Gname.com Pte. Ltd. as the registrar and Aug 13, 2026 as the creation date. Registration preceded first observation by 1 day. At collection time, the hostname resolved to 43.108.86.51 on AS45102 (Alibaba (US) Technology Co., Ltd.). The recorded endpoint location is Seoul, KR. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; no page title was retained, so the captures preserve the landing-page appearance.

The content indicators and 2 positive source findings support the current Trezor impersonation and phishing classification. The target field identifies Trezor, but the record does not establish whether the page requested credentials, a seed phrase, or a wallet connection.