trezor[.]my
PhishDestroy first observed trezor.my on Aug 12, 2026. The hostname explicitly references Trezor; stored content metadata identifies the same apparent target. Stored page analysis classifies the content as impersonation. Current evidence score: 100/100 (critical).
Positive findings are stored from 3 sources: VirusTotal, MetaMask, and SEAL. VirusTotal recorded 11 detections among 91 engines: alphaMountain.ai, Chong Lua Dao, CRDF, CyRadar, ESET, Emsisoft, Fortinet, Gridinsoft, Netcraft, SOCRadar, Webroot on Aug 15, 2026 at 06:50 UTC. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Aug 15, 2026 at 14:20 UTC. Non-positive and contextual checks: On Aug 15, 2026 at 15:18 UTC, AlienVault OTX listed 3 community pulse references (not vendor detections); Google Safe Browsing returned no flag.
The collector marked the hostname reachable on Aug 12, 2026 at 02:28 UTC, but did not retain the HTTP response code.
Neither a page title nor a landing-page capture is stored. The content indicators and 3 positive source findings support the current Trezor-themed impersonation classification.
Network Security Intelligence
Threat Response Pipeline
Public Blocklist Status
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
VirusTotal Analysis
Evidence & External Reports
Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive