trezor-io[.]store

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

Positive findings are stored from 4 sources: VirusTotal, MetaMask, SEAL, and Cloudflare Radar. VirusTotal recorded 11 detections among 91 engines: alphaMountain.ai, BitDefender, CRDF, Emsisoft, Fortinet, G-Data, Kaspersky, LevelBlue, Netcraft, Sophos, Webroot on Aug 14, 2026 at 08:10 UTC. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Aug 14, 2026 at 06:20 UTC. Cloudflare Radar classified the hostname as malicious and placed it in the phishing category; its verdict timestamp was not retained. Non-positive and contextual checks: AlienVault OTX listed 4 community pulse references (not vendor detections) on Aug 14, 2026 at 08:42 UTC. Google Safe Browsing returned no flag on Aug 14, 2026 at 08:39 UTC. URLScan captured the page on Aug 14, 2026 at 08:02 UTC.

The collector marked the hostname reachable on Aug 14, 2026 at 08:02 UTC, but did not retain the HTTP response code. At collection time, the hostname resolved to 127.0.0.1. The evidence archive retains 3 visual captures from PhishDestroy, URLScan, and Cloudflare Radar; no page title was retained, so the captures preserve the landing-page appearance. TLS metadata lists PhishDestroy as the certificate issuer.

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