VirusTotal
14 / 89 engine detections
فتح التقرير“ledger start”
انتحال Ledger: ledgerr--start.pages.dev — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 14/89 (alphaMountain.ai, BitDefender, CyRadar…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
14 / 89 engine detections
فتح التقريرضار
فتح التقريرضار
فتح التقريرno community references
فتح التقريرNo threat flag
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
ledgerr--start.pages.dev is a phishing page impersonating Ledger, the hardware wallet maker. The page title is "ledger start", and the address doubles the letter r, so it reads like an official onboarding page for people setting up or restoring a device. PhishDestroy first saw it on 2026-08-31. It has been offline since 2026-09-11 after the hosting provider blocked the content, and it was still down at the last check on 2026-10-19.
Fake Ledger start pages copy the look of the real setup flow, then claim the device needs to be activated, synchronized or recovered. The victim is told to type in their 24-word recovery phrase. The genuine Ledger process never asks for that phrase on a website. Once the words are submitted, the operators can rebuild the wallet on their own hardware and empty every account it controls, and they no longer need the physical device to do it.
On 2026-09-11, 14 of 89 VirusTotal engines flagged the domain, including alphaMountain.ai, BitDefender, CyRadar, ESET, Emsisoft, Fortinet, G-Data and Kaspersky. That count is modest, but it comes from a broad mix of independent vendors. urlscan.io returned a malicious verdict and recognized Ledger branding on the page. The domain is also listed by MetaMask and SEAL alongside PhishDestroy, so wallet users with those protections should see warnings.
The site ran on Cloudflare Pages, so it used a free pages.dev subdomain rather than a domain the operators registered themselves. It was served from Cloudflare's US network. The registration date is 2025-09-18, almost a year before PhishDestroy first detected the page. The TLS certificate from WE1 is a routine automated certificate, which shows that a padlock in the browser proves nothing about whether a site is genuine.
If you entered your recovery phrase on this page, treat the wallet as fully compromised. Reset your Ledger or set up a new device with a freshly generated phrase, then move any remaining funds to the new accounts immediately. Do this before the attackers drain them. Never reuse the exposed words, and only set up your device through Ledger's official desktop or mobile app. Defenders should block the domain and watch for lookalike pages.dev subdomains that use Ledger branding.
Last checked
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
Saved 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.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
ledgerr--start.pages.dev
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 threat flag
View source14/89 engine detections
View sourceledgerr--start.pages.dev
View source١٥١ نطاقًا متشابهًا محفوظًا
عرض 100 من 151
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 ↗
ledgerr--start.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.