VirusTotal
12 / 89 engine detections
Open reporttrezor.com.vc is a Trezor impersonation page detected by PhishDestroy on 2026-08-30. Risk: critical (100/100). Registrar: NiceNIC. Status: Content unavailable. Hosting: Cloudflare, Inc. VirusTotal: 12/89 engines flag it. Google Safe Browsing flags it. PhishDestroy detected it 14 days before Google Safe Browsing flagged it (in PhishDestroy’s checks). Do not enter credentials or connect a wallet.
“Suspected Phishing | Cloudflare”
12 / 89 engine detections
Open reportThreat flag recorded
Open reportDBL_PHISH
Malicious
Open report3 community references
Open reportprovider verdict: clean
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
trezor.com.vc is an impersonation phishing page that borrows the name of Trezor, the hardware wallet maker. It sits on a Brazilian-style .com.vc ending so the address reads almost like the real brand at a glance. It targets Trezor owners and anyone looking for wallet software or support. PhishDestroy first flagged it on 2026-08-30, and it has been offline since 2026-09-13, still dead as of 2026-10-19.
Fake Trezor sites usually pose as a setup, firmware update or Trezor Suite download page. They then ask the visitor to type in their 12- or 24-word recovery seed, or they push a tampered app that harvests it. With the seed, the attacker can rebuild the wallet on their own device and sweep every coin it holds, and the theft cannot be reversed. The last page title served on this domain was "Suspected Phishing | Cloudflare", a provider warning screen rather than a Trezor lookalike, while our classification rests on the impersonation itself.
Twelve of 89 VirusTotal engines flagged the domain when checked on 2026-09-13. They include BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, CRDF, CyRadar and Gridinsoft. Google Safe Browsing lists it for social engineering, and urlscan.io returned a malicious verdict. Spamhaus carries it on the DBL as phishing. MetaMask and SEAL block it alongside PhishDestroy, and three AlienVault OTX threat pulses reference it, so the call is shared well beyond a single source.
The domain resolved to 188.114.97.3 on Cloudflare's network, geolocated to Canada. That address belongs to Cloudflare's shared proxy, so it hides the server that actually hosted the phishing kit. The site went dark two weeks after we first spotted it, the same day the VirusTotal check ran.
If you typed your recovery seed into this site or into software downloaded from it, treat the wallet as compromised. Set up a new seed on a reset device right away and move any remaining funds to it. Trezor never asks for your seed on a website, in an app or through support. If you only connected a wallet through the page, review and revoke any token approvals it requested. Defenders should block the domain at DNS and the mail gateway, and should watch for sibling Trezor lookalikes on other country-code endings.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a04fec-340d-72f0-8e2d-2344ccb8fae1 |
|---|---|
| Final url | https://trezor.com.vc/ |
| Status | 403 |
| Ip | 188.114.97.3 |
| Contacted domains | [
"challenges.cloudflare.com"
] |
| Contacted IP addresses | [
"104.18.95.41",
"104.18.94.41",
"188.114.97.3"
] |
| Asns | [
"13335"
] |
| Linked domains | [
"www.cloudflare.com"
] |
| Document hash | d59283d9a702792c8ad44872c4ec3088875e6844940bbc8e2380cd878216936c |
| Globals | [
"onTurnstileSuccess",
"_cf_translation",
"turnstile",
"singleSelectors",
"groupSelectors"
] |
| Tls | {
"san": [
"trezor.com.vc",
"*.trezor.com.vc"
],
"cipher": "AES_128_GCM",
"issuer": "WE1",
"subject": "trezor.com.vc",
"protocol": "QUIC",
"valid_to": "2026-11-27T15:47:54Z",
"valid_from": "2026-08-29T14:50:09Z"
} |
| Domain age days | 0 |
| Apex age days | 0 |
| Tls age days | 0 |
| Tls valid days | 90 |
| Requests | 6 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 97,
"malicious": true
},
"overall": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"genericcloudflare"
],
"malicious": true,
"categories": [
"phishing"
]
},
"urlscan": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"Generic Cloudflare"
],
"malicious": true,
"categories": [
"phishing"
]
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html; charset=utf-8",
"x-frame-options": "SAMEORIGIN",
"referrer-policy": "same-origin"
} |
Observed: · Retrieved:
| Uuid | 37a97601-6686-4492-9550-efd27dd8aae0 |
|---|
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 44,
"malicious": 13,
"suspicious": 1,
"undetected": 34
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"VIPRE": "phishing",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "phishing",
"CyRadar": "phishing",
"Fortinet": "spam",
"SOCRadar": "phishing",
"LevelBlue": "phishing",
"PhishFort": "phishing",
"BitDefender": "phishing",
"alphaMountain.ai": "phishing",
"Google Safe Browsing": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Registrar | NICENIC INTERNATIONAL GROUP CO., LIMITED |
| Created | 2026-08-29T15:40:48Z |
| Expires | 2027-08-29T15:40:48Z |
| Updated | 2026-08-29T15:40:48Z |
| First seen | 2026-08-29T16:01:36Z |
| DNS records | [
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3037::ac43:99e3"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3035::6815:ce9"
},
{
"ttl": 21600,
"type": "NS",
"value": "jeremy.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "172.67.153.227"
},
{
"ttl": 21600,
"type": "NS",
"value": "monroe.ns.cloudflare.com"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "jeremy.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "104.21.12.233"
}
] |
| Dns at | 2026-09-01T07:45:14Z |
| Jarm | 27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c |
| Certificate | {
"san": [
"trezor.com.vc",
"*.trezor.com.vc"
],
"issuer": "Google Trust Services / WE1",
"serial": "23a970618cc82cb3138a1443253d0f7a",
"sha256": "f545d1e576e0df0f44cb5478f22805a5ea6e8477b0dd52cbfc2b222cba6ebcb8",
"subject": "trezor.com.vc",
"valid_to": "2026-11-27T15:47:54Z",
"valid_from": "2026-08-29T14:50:09Z"
} |
| Registration record | {
"registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
"registrar_iana_id": "3765",
"registrar_url": "http://www.nicenic.net",
"created": "2026-08-28T16:00:00Z",
"updated": "2026-08-28T16:00:00Z",
"expires": "2027-08-28T16:00:00Z",
"status": [
"addPeriod",
"clientDeleteProhibited",
"clientTransferProhibited"
],
"nameservers": [
"jeremy.ns.cloudflare.com",
"monroe.ns.cloudflare.com"
],
"dnssec": "unsigned"
} |
No. PhishDestroy classifies trezor.com.vc as a Trezor impersonation page (risk: critical, 100/100); it was first detected on 2026-08-30. VirusTotal: 12/89 engines flag it. Google Safe Browsing flags it. Listed on Spamhaus DBL. PhishDestroy detected it 14 days before Google Safe Browsing flagged it (in PhishDestroy’s checks). Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on trezor.com.vc. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
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.
Last checked
Edge-IP reputation is not attributed to this domain.
jeremy.ns.cloudflare.commonroe.ns.cloudflare.comLocation describes the IP network.
f545d1e576e0df0f44cb5478f22805a5ea6e8477b0dd52cbfc2b222cba6ebcb8trezor.com.vc*.trezor.com.vcSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable→Unavailable
No flag recorded→Flag recorded
Reachable
3 community references
View sourceThreat flag recorded
View source12/89 engine detections
View sourcetrezor.com.vc
View source74 stored lookalike domains
1 community report
CategoryIMPERSONATION
Brand abuse: impersonation, fake affiliation, impersonating Trezor
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
trezor.com.vc
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
trezor.com.vc)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.