usblog-trezor[.]com
“Critical Security Update: Addressing the Recent Trezor Data Breach”
usblog-trezor.com — Erreur de serveur (HTTP 502). Usurpation de l'identité de la marque : Trezor; Type d'arnaque : Crypto Scam. Résumé des preuves: VirusTotal 10/91 (ADMINUSLabs, ChainPatrol, alphaMountain.ai, BitDefender, Chong Lua Dao); URLQuery 1 alert; URLScan malicious verdict; Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 84/100. Bureau d’enregistrement: NiceNIC.
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
Analysis indicates that the domain usblog-trezor.com was registered on 14 March 2026 through NiceNIC International Group Co., Limited. The domain resolves to IP 104.21.86.35, which belongs to AS13335 Cloudflare, Inc. and is geolocated in the United States. The site presented an HTTPS certificate issued by Let’s Encrypt (E7) and used Cloudflare nameservers anna.ns.cloudflare.com and zahir.ns.cloudflare.com. The public page title observed was “Critical Security Update: Addressing the Recent Trezor Data Breach,” directly referencing the Trezor brand and suggesting a crypto‑related impersonation.
Classification in the intelligence set labels the campaign as a crypto scam targeting Trezor users. The domain appears on three security blocklists and has been explicitly blocked by PhishDestroy, MetaMask, and SEAL. VirusTotal scanning reported a single positive detection out of ninety‑five vendors, indicating at least one security product identified malicious behavior. The current operational status is offline, and the hosting infrastructure remains under Cloudflare’s protection, which can obscure the underlying origin server.
Uncertainty remains regarding the exact payload delivered, the presence of any credential‑harvesting forms, or additional command‑and‑control infrastructure, as no further page content analysis is available. Defenders should update their URL filtering rules to block usblog-trezor.com across web gateways, email gateways, and endpoint protection suites. Threat intelligence feeds should be refreshed to include the domain and its associated IP address, and any alerts triggered by the single VirusTotal detection should be investigated for possible false negatives. Continuous monitoring of Cloudflare‑hosted IP ranges for similar Trezor‑related impersonation attempts is recommended, and incident response teams should be prepared to advise users that any unsolicited communications referencing a “critical security update” from Trezor are likely fraudulent.
Renseignements sur la sécurité réseau Registrar context
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | usblog-trezor.com |
malicious | Sinkholed |
Processus de réponse aux menaces Pipeline
Statut de la liste de blocage publique
Capture enregistrée
Informations sur les domaines
Détails techniquesDNS, SAN SSL, horodatages
ICANN OVERSIGHT
Contexte de l’accréditation et du RAA
Contexte de l’accréditation et du RAA
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Latest Classified Outcome 2026-08-15 03:27:57 UTC
Analyse VirusTotal
Analyse des performances du site
Google PageSpeed Insights — mobile performance audit of usblog-trezor.com · checked Mar 14, 2026
Données factuelles et rapports externes
PD-20260314-C73955 Recipient: abuse@nicenic.net, abuse@verisign-grs.com, compliance@icann.org 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