Skip to security report
Domain security and threat intelligence
827262-trezor.io favicon

827262-trezor.io

In short

827262-trezor.io is a credential phishing page detected by PhishDestroy on 2026-10-11. Risk: critical (100/100). Registrar: NiceNIC. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 10/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“Sign in”

Registrar
NiceNIC
Resolved IP
172.67.146.167
Registered
Sep 16, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 10/92 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: Trezor
OTX: 4 refs Oct 11, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 10. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Source evidenceVirusTotal 10 / 92 · OTX 4 references 6 sources

VirusTotal

10 / 92 engine detections

Open report

Spamhaus DBL

DBL_PHISH

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Network Security Intelligence Registrar context
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

Analysis

Critical
VirusTotal
10 / 92
OTX
4 community refs
Page captures
3

PhishDestroy threat report

Overview

827262-trezor.io is a credential phishing page that imitates Trezor, the hardware wallet maker, and targets people who own a Trezor device. A random-looking number sits in front of the brand name, so a quick glance at the address bar reads as Trezor. PhishDestroy first flagged it on 2026-10-11. As of 2026-10-19 the site is still online and serving its phishing content.

How the scam works

The page is titled "Sign in" and presents itself as a Trezor login. Trezor wallets do not need a website login to access funds, so any Trezor-branded sign-in form is a red flag. Pages like this capture whatever the visitor types, usually an email and password, and often push for a PIN or the 12 to 24 word recovery seed. Stolen credentials let attackers take over linked accounts. A recovery seed gives them full control of the wallet, which they can empty from anywhere without the physical device.

Evidence

On 2026-10-16, 10 of 92 VirusTotal engines flagged the domain, including alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. Most engines had not caught up yet, but the vendors that did are mainstream, and other sources agree. Spamhaus lists the domain in its DBL as phishing. MetaMask and SEAL block it alongside PhishDestroy, and four AlienVault OTX threat pulses reference it.

Infrastructure

The domain was registered on 2026-09-16 through NICENIC INTERNATIONAL GROUP CO., LIMITED, 25 days before PhishDestroy detected it. A gap that short is typical of domains bought for a specific campaign. The site sits behind Cloudflare, with its visible address geolocating to Canada. That address belongs to Cloudflare's network and does not reveal where the real server runs. The Let's Encrypt certificate gives the page a padlock icon, which only means the connection is encrypted, not that the site is genuine.

What to do

If you typed a recovery seed into this page, treat the wallet as compromised. Generate a new seed on your device and move any remaining funds to the new wallet immediately. If you entered an email and password, change that password everywhere you reused it, enable app-based two-factor authentication and watch for unfamiliar sign-ins. Security teams should block the domain at DNS and proxy level, add it to mail filters, and report it to Cloudflare and the registrar for takedown.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-10-08T23:36:12Z

Observed: · Retrieved:

Uuid
01a11ddf-abd4-74ad-a177-359dbfaa2147
Final url
https://827262-trezor.io/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://827262-trezor.io/",
        "from": "http://827262-trezor.io/",
        "status": 307
    }
]
Ip
172.67.146.167
Contacted domains
[
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.251.127.95",
    "172.67.146.167"
]
Asns
[
    "15169",
    "13335"
]
Countries
[
    "US"
]
Document hash
3ec7e29dc4075fe262bcc3de5a50b3a7325f7718089b1ad1306adf85c2c86567
Script hashes
[
    "e5dce296228005bce72db8108c8f2ce0b778768b43a2b210e83c209cbbb91909",
    "fbbbb30fc0d9a2561cd8589a7707b108b40d88d49fdc206bde697b4c80a3640a",
    "dcf730ee799bb85852bd9e49482b93b741cdcb4d800f2009e97b1aed078ffd2d",
    "0e8ae037cae7ccf10a90755fe77e60640f125007f0bf25f10f88d642533ac1f9"
]
Globals
[
    "__reactRouterVersion",
    "Buffer",
    "devtoolsFormatters"
]
Tls
{
    "san": [
        "*.827262-trezor.io",
        "827262-trezor.io"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "827262-trezor.io",
    "protocol": "QUIC",
    "valid_to": "2026-12-15T19:44:50Z",
    "valid_from": "2026-09-16T19:44:51Z"
}
Domain age days
22
Apex age days
22
Tls age days
22
Tls valid days
89
Requests
11
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 84,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-10-12T10:06:26Z

Observed: · Retrieved:

Uuid
e1a364dc-e075-42c9-9dfc-74fbd2e5855a
Final url
https://827262-trezor.io/
Status
200
History
[
    {
        "url": "https://827262-trezor.io/",
        "status": 200
    }
]
DOM structure hash
520c38fffcc09041c5f02650cbb449a794effa41ceb957a3f30a5d085d3653e9
Document hash
b1233f376c54fb9f042abf7616cdb191c01a2a55416cc65e67e17541d6244705
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "827262-trezor.io",
        "type": "A",
        "value": "172.67.146.167"
    },
    {
        "name": "827262-trezor.io",
        "type": "A",
        "value": "104.21.57.150"
    },
    {
        "name": "827262-trezor.io",
        "type": "AAAA",
        "value": "2606:4700:3037::ac43:92a7"
    },
    {
        "name": "827262-trezor.io",
        "type": "AAAA",
        "value": "2606:4700:3030::6815:3996"
    }
]
Dnssec valid
false
Ip
172.67.146.167
Registration record
{
    "registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
    "created": "2026-09-16T20:34:35Z",
    "updated": "2026-09-21T20:34:52Z",
    "expires": "2027-09-16T20:34:35Z",
    "nameservers": [
        "george.ns.cloudflare.com",
        "paislee.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-16T18:44:06Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 52,
    "malicious": 3,
    "suspicious": 4,
    "undetected": 33
}
Vendor labels
{
    "ESET": "phishing",
    "Fortinet": "spam",
    "URLQuery": "suspicious",
    "Kaspersky": "phishing",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "spam",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "Sophos": "phishing and fraud",
    "alphaMountain.ai": "Spam (alphaMountain.ai)"
}
Registrar
NICENIC INTERNATIONAL GROUP CO., LIMITED
Created
2026-09-16T20:34:35Z
Expires
2027-09-16T20:34:35Z
Updated
2026-09-16T20:34:35Z
First seen
2026-09-16T22:11:32Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.57.150"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.146.167"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::ac43:92a7"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3030::6815:3996"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "paislee.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "george.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "george.ns.cloudflare.com"
    }
]
Dns at
2026-10-16T18:44:58Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.827262-trezor.io",
        "827262-trezor.io"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "640514491e330682571a65fb9dfd1649f49",
    "sha256": "41444d1601d0d4bd7693c4ed62d7d8c4bd6138d77acd334ce34d9f0bafe1a9fe",
    "subject": "827262-trezor.io",
    "valid_to": "2026-12-15T19:44:50Z",
    "valid_from": "2026-09-16T19:44:51Z"
}
Registration record
{
    "registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
    "registrar_iana_id": "3765",
    "registrar_url": "http://www.nicenic.net",
    "created": "2026-09-16T16:00:00Z",
    "updated": "2026-09-16T16:00:00Z",
    "expires": "2027-09-16T16:00:00Z",
    "status": [
        "addPeriod",
        "clientDeleteProhibited",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "george.ns.cloudflare.com",
        "paislee.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client delete prohibited",
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-09-16T16:00:00Z",
        "registration": "2026-09-16T16:00:00Z",
        "registrar expiration": "2027-09-16T16:00:00Z",
        "last update of RDAP database": "2026-09-16T16:00:00Z"
    }
}

Questions about 827262-trezor.io

Is 827262-trezor.io legit?

No. PhishDestroy classifies 827262-trezor.io as a credential phishing page (risk: critical, 100/100); it was first detected on 2026-10-11. VirusTotal: 10/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is 827262-trezor.io safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on 827262-trezor.io. 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 827262-trezor.io?

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.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 3 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
RegistrationCreated Sep 16, 2026 (35d · New) — Expires Sep 16, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 11, 2026
DOM Analysisanalyzed Oct 13, 2026score 100/100
Submitted URLhttp://827262-trezor.io/
Favicon Hash
Observed page title
Sign in
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 54 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.146.167
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • paislee.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-09-16 19:44:51
Valid until
2026-12-15 19:44:50
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-12 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint41444d1601d0d4bd7693c4ed62d7d8c4bd6138d77acd334ce34d9f0bafe1a9fe
Certificate names · 2 SANs
  • *.827262-trezor.io
  • 827262-trezor.io

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-22 11:01:01 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-22 11:01:01 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 11:01:01 UTC last content: 2026-10-22 11:01:01 UTC
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.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

10 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
BitDefender
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
SOCRadar
URLQuery

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history10

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 5
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    redirected→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    10/92 engine detections

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. Added to PhishDestroy

    827262-trezor.io

    View source

Lookalike domains

74 stored lookalike domains

Show all (62)
grezor.io replacement rezor.io omission rrezor.io replacement rtezor.io transposition tdezor.io replacement teezor.io replacement terzor.io transposition tezor.io omission tfezor.io replacement tr.ezor.io subdomain tr3zor.io replacement treeor.io replacement treezor.io insertion treor.io omission treqor.io replacement tresor.io replacement trezeor.io insertion trezer.io vowel-swap trezior.io insertion trezir.io replacement trezkor.io insertion trezlor.io insertion trezo.io omission trezoe.io replacement trezoir.io insertion trezopr.io insertion trezor-io.com various trezorio.com various trezot.io replacement trezpor.io insertion trezpr.io replacement trezr.io omission trezro.io transposition trezxor.io insertion trezzor.io insertion trizor.io vowel-swap trozor.io vowel-swap trrzor.io replacement trtezor.io insertion trwezor.io insertion trwzor.io replacement trzeor.io transposition trzzor.io replacement ttezor.io replacement ttrezor.io insertion tyrezor.io insertion yrezor.io replacement ytrezor.io insertion prezor.io bitsquatting treazor.io insertion trerzor.io insertion trewzor.io insertion trexor.io bitsquatting trez0r.io homoglyph trezaor.io insertion trezora.io addition trezore.io addition trezoro.io addition trezorr.io addition trezors.io addition xn--tezor-5bb.io homoglyph xn--trezo-9bb.io homoglyph

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

827262-trezor.io

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Last known active

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.

Official reporting routes

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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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 827262-trezor.io)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/827262-trezor.io"
  title="PhishDestroy threat report for 827262-trezor.io"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>