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.
How the scam works
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.
Evidence
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.
Infrastructure
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.
What to do
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.
注册信息创建 2026年10月7日 (13d · Very New!)—Expires 2027年10月7日
HTTP 状态码200
技术详情Provenance & timestamps
首次发现2026年10月10日
DOM Analysisanalyzed 2026年10月10日score 100/1001 brand signal
Submitted URLhttp://fleet-ledger.com/
Observed page title
Fleet Ledger
Automated brand references
Ledger
TLS 证书
颁发者 Google Trust Services / WE1· stored validity ends in 77 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
104.21.0.130
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
Edge-IP 声誉不属于此域。
域名服务器 2
carol.ns.cloudflare.com
vicente.ns.cloudflare.com
Mail routing 3 MX records
route3.mx.cloudflare.netpriority 7
route1.mx.cloudflare.netpriority 77
route2.mx.cloudflare.netpriority 97
Location describes the IP network.
TLS 证书
Issuer
Google Trust Services / WE1
Valid from
2026-10-09 03:31:13
Valid until
2027-01-07 04:31:10
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-10 16:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintd9a55341bede85f3ad385e5dbf2b0ccea1496156819f67212ded324aa80c5878Certificate names · 1 SANs
www.fleet-ledger.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-21 01:54:54 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-21 01:54:54 UTClast content: 2026-10-21 01:54:54 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
技术 · 3 identified
Cloudflare Browser Insights
AnalyticsRUM
Cloudflare Browser Insights is a tool that measures the performance of websites from the perspective of users.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(US)
