VirusTotal
6 / 92 engine detections
فتح التقرير“Fleet Ledger”
انتحال Ledger: fleet-ledger.com — آخر نشاط معروف (HTTP 200). ملخص الأدلة: VirusTotal 6/92 (CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, Kaspersky); 2…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
6 / 92 engine detections
فتح التقريرSuspicious
فتح التقرير3 community references
فتح التقريرNo threat flag
فتح التقريرNo malicious flag
فتح التقريرResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
fleet-ledger.com is an impersonation phishing page that trades on the Ledger name under the page title "Fleet Ledger". It targets owners of Ledger hardware wallets and anyone searching for Ledger support or software. PhishDestroy first saw the domain on 2026-10-10. It was still online and serving its content when last checked on 2026-10-19.
Ledger impersonation pages exist to get around the hardware wallet's main protection, which is that private keys never leave the device. They usually do this by asking the victim to type in the 24-word recovery phrase, presented as a sync, a security check or a fix for some problem. Some versions instead push the visitor to connect a wallet and sign transactions. Anyone who enters the recovery phrase gives away full control of every account it secures, and the funds can be emptied within minutes. The "Fleet Ledger" branding is meant to look like an official Ledger service. Ledger will never ask for your recovery phrase on any website.
VirusTotal shows 6 of 92 engines flagging the domain as of 2026-10-14: CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, Kaspersky and SOCRadar. That is a low count, but it comes from independent vendors, and the domain is also blocked by MetaMask and the SEAL security alliance alongside PhishDestroy. Three AlienVault OTX threat pulses reference it, so other researchers are tracking it too.
The domain was registered on 2026-10-07 through Cloudflare, Inc. and was caught just three days later. That short gap is typical of throwaway phishing domains set up for a single campaign. The site resolves to 104.21.0.130 on Cloudflare's US network, a shared proxy address that hides the real origin server. Its certificate comes from Google Trust Services (WE1), so the padlock in the browser only means the connection is encrypted, not that the site is legitimate.
If you typed your Ledger recovery phrase into this site, treat that wallet as compromised. Set up a new device or wallet with a fresh phrase and move any remaining funds there immediately, before an attacker does. If you connected a wallet or signed anything, revoke token approvals with a trusted approval checker and watch for unexpected transactions. Only get Ledger software and support through Ledger's official channels. Security teams should block fleet-ledger.com at DNS and proxy level and look for similar Ledger-themed domains registered in the same period.
Last checked
لا تُنسب سمعة Edge-IP إلى هذا المجال.
carol.ns.cloudflare.comvicente.ns.cloudflare.comroute3.mx.cloudflare.netpriority 7route1.mx.cloudflare.netpriority 77route2.mx.cloudflare.netpriority 97Location describes the IP network.
d9a55341bede85f3ad385e5dbf2b0ccea1496156819f67212ded324aa80c5878www.fleet-ledger.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of fleet-ledger.com · checked Oct 10, 2026
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.
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
غير معروف→live_content
content_served
يمكن الوصول إليه
No threat flag
View source6/92 engine detections
View source3 community references
View sourcefleet-ledger.com
View sourcePage captured
View source١٥١ نطاقًا متشابهًا محفوظًا
عرض 100 من 151
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
fleet-ledger.com
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 ↗
fleet-ledger.com)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.