Cloudflare Radar
ضار
فتح التقرير“Suspected Phishing | Cloudflare”
انتحال Trezor: account-safety-trezor.pages.dev — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 0/89; Google Safe Browsing flagged; CF…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
ضار
فتح التقريرThreat flag recorded
فتح التقرير0 / 89 engine detections
فتح التقريرno community references
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
account-safety-trezor.pages.dev is a phishing page that impersonates Trezor, the hardware wallet maker, and targets people who keep crypto on Trezor devices. The "account-safety" wording is designed to make a security scare look like an official warning. PhishDestroy first detected it on 2026-09-04. The site has been offline since 2026-09-13, and its content was blocked by the hosting provider when last checked on 2026-10-19.
Fake Trezor "account safety" pages usually claim the visitor's wallet is compromised or needs urgent verification, then push them to type in their 12- or 24-word recovery seed or to install a fake Trezor app. Anyone holding that seed can rebuild the wallet on their own device and empty it, so the victim loses every asset it controls. Trezor never asks for a recovery seed on a website. The current page title, "Suspected Phishing | Cloudflare", is the provider's own warning screen rather than Trezor-branded content, while we classify the original site as Trezor impersonation.
Google Safe Browsing flags the domain for social engineering, which is its category for phishing and deceptive pages. PhishDestroy lists it on our blocklist. VirusTotal returned 0 detections out of 89 engines on 2026-09-13, the same day the site went offline, so antivirus scanners alone would not have warned visitors about it.
The subdomain was created on 2026-09-03 and detected the next day, which fits the pattern of short-lived phishing pages that run for days, not months. It was set up on Cloudflare Pages, a free hosting service that gives each project a pages.dev address. Traffic went through Cloudflare's network at an address located in Canada. The free subdomain cost the operator nothing and could be replaced quickly once blocked.
If you entered your Trezor recovery seed or passphrase on this site, treat the wallet as compromised. Set up a new seed on your Trezor device and move all funds there right away, before the attacker does. If you downloaded any software from the page, uninstall it, scan the computer, and get Trezor Suite only from Trezor's official site. Defenders should block this exact subdomain rather than all of pages.dev and watch for similar Trezor-themed names on free hosting platforms.
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
f20f0bc82aed702c6d316dc9a22b25985818c326a345ec99c3b702b11d78a72bSaved 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.
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
يمكن الوصول إليه→غير متوفر
No flag recorded→Flag recorded
Threat flag recorded
View source0/89 engine detections
View sourceaccount-safety-trezor.pages.dev
View source٧٤ نطاقًا متشابهًا محفوظًا
بلاغ مجتمعي واحد
الفئةIMPERSONATION
Brand abuse: impersonation, wallet connect, impersonating Trezor
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
account-safety-trezor.pages.dev
Listed domains receive at least one abuse report; this entry has no retained notification history.
إذا أدخلت بيانات اعتماد الحساب أو المعلومات الشخصية أو معلومات الدفع أو قمت بتنزيل ملف من هذا النطاق، فاتخذ إجراءً فوريًا. فيما يلي موارد لمساعدتك في الإبلاغ عن الحادث وحماية نفسك.
حدد بلدك للحصول على الاتصالات الرسمية المتعلقة بالجرائم الإلكترونية أو إنشاء مسودة شكوى →.
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 ↗
account-safety-trezor.pages.dev)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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
تحليل التهديدات باستخدام قائمة الحظر المخزنة، وWHOIS، وDNS، وأدلة الفحص العامة
امسح الآنأرسل النطاقات المشبوهة إلى قاعدة بيانات التهديدات الخاصة بنا — ساهم في حماية المجتمع
إبلاغتقارير التصيد الاحتيالي الأخيرة وتغييرات التوفر الملحوظة
مراقبةراقب التهديدات في الوقت الفعلي أو اعترض على هذا الإدراج إذا كنت تعتقد أنه إنذار كاذب
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.