VirusTotal
15 / 89 engine detections
فتح التقرير“Ledger.com - Official Start Page”
انتحال Ledger: start-ledgrecom-edge-us-en.pages.dev — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 15/89 (alphaMountain.ai…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
15 / 89 engine detections
فتح التقريرThreat flag recorded
فتح التقريرضار
فتح التقريرno community references
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain start-ledgrecom-edge-us-en.pages.dev served a fake Ledger.com start page, copying the official Ledger branding to lure Ledger wallet owners. PhishDestroy first detected the page on 2026-09-15. The site displayed the title “Ledger.com – Official Start Page” to appear legitimate. As of the latest check on 2026-10-19 the page is dead, with the provider blocking the content since 2026-09-22.
Visitors are presented with a page that looks exactly like Ledger’s official start page, including the Ledger logo and the title “Ledger.com – Official Start Page”. The page asks users to log in with their Ledger account email and password, or to connect a hardware wallet and approve a transaction. Once credentials or wallet approvals are submitted, attackers can hijack the account and drain funds. The scheme relies on the trust users have in Ledger’s brand to harvest login data and wallet authorizations.
In VirusTotal the URL was flagged by 15 of 89 scanners, including AlphaMountain.ai, BitDefender, ESET, Fortinet and G‑Data, confirming malicious intent. Google Safe Browsing lists the domain as a social‑engineering threat. urlscan.io returned a malicious verdict and identified Ledger as the impersonated brand. The domain is already on PhishDestroy, MetaMask and SEAL blocklists.
The domain was registered on 2026-08-07 through Cloudflare Pages, giving the operators roughly five weeks before PhishDestroy’s first sighting. Hosting runs on Cloudflare’s network in Canada (IP 188.114.96.9). The site used a Google Trust Services / WE1 TLS certificate, which is a legitimate public CA and does not indicate abuse.
If you entered your Ledger credentials or connected a hardware wallet on this page, change your Ledger password immediately and revoke any unknown device approvals from your Ledger account. Monitor your wallet addresses for unauthorized transactions and consider moving funds to a new device. Security teams should block the domain, add it to URL filtering, and monitor for similar Cloudflare‑Pages impersonation patterns. Keep software and firmware up to date to reduce the impact of credential theft.
Last checked
لا تُنسب سمعة Edge-IP إلى هذا المجال.
Location describes the IP network.
448db900d4bbbd9efe00ca0ce0dede144c25bba6ae806d48c8108930c8d720fcSaved 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
start-ledgrecom-edge-us-en.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 flag recorded→Flag recorded
يمكن الوصول إليه
Threat flag recorded
View source15/89 engine detections
View sourcestart-ledgrecom-edge-us-en.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 ↗
start-ledgrecom-edge-us-en.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.