trezorsdevices.support is a Trezor impersonation page detected by PhishDestroy on 2026-08-12. Risk: critical (100/100). Status: Content unavailable. VirusTotal: 17/91 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 17. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
trezorsdevices.support was an impersonation phishing page posing as Trezor. Its name combines the brand with "devices" and a .support ending to look like an official help desk, and it targeted owners of Trezor hardware wallets. PhishDestroy first flagged it on 2026-08-12. The site has been offline since 2026-09-11, and on 2026-10-19 its domain no longer resolved in DNS.
How the scam works
Fake Trezor support sites usually warn about a firmware problem, a security alert or a wallet that needs "verification" or "recovery." The page then asks for the 12- or 24-word recovery seed, sometimes through a form styled like Trezor Suite. A Trezor's seed is the master key to every account on the device, so anyone who has it can rebuild the wallet elsewhere and empty it without touching the hardware. The physical device stays safe in the victim's hands while the funds are swept remotely.
Evidence
On 2026-08-26, 17 of 91 VirusTotal engines flagged the domain, including ESET, BitDefender, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, Cluster25, CRDF and CyRadar. Spamhaus lists it in its DBL under the phishing category. Beyond PhishDestroy, the wallet-focused MetaMask and SEAL blocklists also carry it, so MetaMask users were warned before reaching the page. Three AlienVault OTX threat pulses reference the domain, showing that several independent researchers tracked it.
Infrastructure
The domain borrows the trust people place in vendor help desks. The .support extension and the plural "trezors" are typical of throwaway lookalikes registered to catch people searching for help. The site went dark about a month after PhishDestroy first detected it, and its DNS is now inactive, which fits a short-lived campaign domain.
What to do
If you typed your recovery seed into this site, treat that wallet as compromised. Set up your Trezor, or a new device, with a freshly generated seed, then move every remaining asset to the new addresses right away. Do not reuse the old seed or any passphrase entered alongside it. Trezor never asks for your seed on a website, by email or through a support agent. Defenders should keep blocking the domain and watch for similar Trezor-themed names on support-style TLDs.
Stored page, network and scanner observations, grouped by source and observation time.
Cloudflare Radar · 2026-08-14T03:34:21Z
Observed: · Retrieved:
Uuid
1d11ab40-7174-4d82-9096-2be688811c55
Questions about trezorsdevices.support
Is trezorsdevices.support legit?
No. PhishDestroy classifies trezorsdevices.support as a Trezor impersonation page (risk: critical, 100/100); it was first detected on 2026-08-12. VirusTotal: 17/91 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
Is trezorsdevices.support safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on trezorsdevices.support. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used trezorsdevices.support?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 12, 2026
Favicon Hash
Latest Classified Outcome 2026-10-21 14:53:36 UTC
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-21 01:13:36 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-08-12 17:28:07 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-12 17:28:07 UTC → 2026-09-30 16:14:55 UTC · 1,174.78hmidpoint estimate ≈ 2026-09-06 04:51:31 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · trezorsdevices.support
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
2 evidence signal groups linked0 stored notification recordsContent unavailable
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including trezorsdevices.support)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
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.
