xtrezor[.]io

PhishDestroy first observed xtrezor.io on Aug 25, 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 3 sources: MetaMask, SEAL, and Spamhaus DBL. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Aug 25, 2026 at 14:20 UTC. Spamhaus DBL: DBL_SPAM on Aug 25, 2026 at 14:30 UTC. Non-positive and contextual checks: VirusTotal recorded 0 detections among 91 engines on Aug 25, 2026 at 11:50 UTC. AlienVault OTX listed 2 community pulse references (not vendor detections) on Aug 25, 2026 at 15:35 UTC. Google Safe Browsing returned no flag on Aug 25, 2026 at 15:34 UTC. URLScan captured the page on Aug 25, 2026 at 11:45 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 25, 2026 at 11:45 UTC, but did not retain the HTTP response code. Registration records for the domain list NICENIC INTERNATIONAL GROUP CO., LIMITED as the registrar and Aug 24, 2026 as the creation date. Registration and first observation occurred on the same UTC date. At collection time, the hostname resolved to 142.250.154.121 on AS15169 (Google LLC). The recorded endpoint location is Mountain View, US. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; no page title was retained, so the captures preserve the landing-page appearance. TLS metadata lists Google Trust Services as the certificate issuer with validity through Nov 22, 2026; checked Aug 25, 2026 at 13:02 UTC.

The content indicators and 3 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.