trezor-io.io
“trezor-io.io”
trezor-io.io — Dernier actif connu (HTTP 301). Usurpation de l'identité de la marque : Trezor; Type d'arnaque : Impersonation. Résumé des preuves: VirusTotal 7/91 (alphaMountain.ai, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet); Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 95/100.
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
Résumé des preuves
PhishDestroy first observed trezor-io.io on Aug 23, 2026. The hostname explicitly references Trezor; stored content metadata identifies the same apparent target. The captured page title is “trezor-io.io”. Stored page analysis classifies the content as impersonation. Campaign clustering links the hostname to the Unknown kit. Current evidence score: 95/100 (critical).
Positive findings are stored from 4 sources: VirusTotal, MetaMask, SEAL, and Spamhaus DBL. VirusTotal recorded 7 detections among 91 engines: alphaMountain.ai, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar on Aug 31, 2026 at 02:07 UTC. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Sep 21, 2026 at 02:20 UTC. Spamhaus DBL: DBL_PHISH on Aug 27, 2026 at 22:30 UTC. Non-positive and contextual checks: AlienVault OTX listed 6 community pulse references (not vendor detections) on Aug 29, 2026 at 03:54 UTC. Google Safe Browsing returned no flag on Aug 29, 2026 at 03:53 UTC. URLScan completed without a malicious verdict (score 0) on Sep 19, 2026 at 03:30 UTC.
HTTP 301 was recorded on Sep 21, 2026 at 01:51 UTC. At collection time, the hostname resolved to 45.74.7.27 on AS202412 (Omegatech LTD). The recorded endpoint location is London, GB. The stored server header is Apache. DOM analysis on Sep 17, 2026 at 02:20 UTC returned 95/100. The evidence archive retains 1 visual capture from PhishDestroy. TLS metadata lists Let's Encrypt as the certificate issuer with validity through Nov 19, 2026; checked Aug 27, 2026 at 22:02 UTC.
The content indicators and 4 positive source findings support the current Trezor-themed impersonation classification.
Forensic History & Detection Timeline
-
Threat First Observed Aug 27, 2026 · 21:03 UTCDomain ingestion complete. Initial state is marked as alive.
Processus de réponse aux menaces Pipeline
Statut de la liste de blocage publique
Evasion analysis
Cloaking & traffic-distribution check
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
- Stored cloaking flag
- Not yet scanned
- Last cloaking scan
- Server header seen by scanner
Apache/2.4.52 (Ubuntu)
Scanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://trezor-io.io/; server=Apache/2.4.52 (Ubuntu)
Technologies · 2 identified
Analyse VirusTotal
Domaines ressemblants
74 domaines ressemblants enregistrés
Tout afficher (62)
Renseignement communautaire
6 signalements communautaires
CatégoriePHISHING
Dear Team, We are writing to report a phishing domain, trezor-io[.]io, that impersonates the Trezor cryptocurrency hardware wallet. The name is assembled from the brand and the brand's own top-level domain — "trezor-io" placed in the ".io" zone — so that, written out, it reads l
Données factuelles et rapports externes
“Dear Team, We are writing to report a phishing domain, trezor-io[.]io, that impersonates the Trezor cryptocurrency hardware wallet. The name is assembled from the brand and the brand's own top-level domain — "trezor-io" placed in the ".io" zone — so that, written out, it reads like the address of the rightful owner, trezor.io. The domain was registered on 21 August 2026. Within a single day it had taken the first position in Bing for a search of its own name, ranked above the genuine Trezor pa”
Ce site vous a-t-il affecté ?
Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Signalez-le à vos autorités locales
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
Vérifier n'importe quel domaine
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignaler une tentative d'hameçonnage
Signalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerFlux d'alertes en temps réel
Rapports de phishing récents et changements de disponibilité observés
SurveillerRestez informés, restez en sécurité
Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif