VirusTotal
4 / 89 engine detections
打开报告“Ledger Start - Secure Your Crypto”
冒充 Ledger: ledgeer-com-app-start.pages.dev — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 4/89 (alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, LevelBlue); 2…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
4 / 89 engine detections
打开报告no community references
打开报告provider verdict: clean
打开报告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
ledgeer-com-app-start.pages.dev is an impersonation phishing page built to look like Ledger's device onboarding, titled "Ledger Start - Secure Your Crypto". The misspelled "ledgeer-com" prefix is meant to pass a quick glance as Ledger's own address. It targets people setting up or troubleshooting a Ledger hardware wallet. PhishDestroy first flagged it on 2026-09-01. It went offline on 2026-09-16, and the hosting provider had blocked its content as of 2026-10-19.
The real Ledger Start flow guides new owners through setup, so a copy of it reaches users at the moment they expect to handle sensitive steps. Fake Ledger setup pages of this kind usually walk the victim to a "restore" or "verify" screen that asks for the 24-word recovery phrase, or push a counterfeit Ledger Live download. Anyone who types that phrase into the page hands over full control of every account derived from it. The attacker can then empty the wallet from their own device without ever touching the hardware.
Detection by security vendors was thin. VirusTotal showed 4 of 89 engines flagging the site on 2026-09-14: alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet and LevelBlue. Crypto-focused blocklists carried more of the weight. Besides PhishDestroy, the domain is listed by MetaMask and SEAL, which means wallet users relying on those protections were warned even when general antivirus scanners stayed silent.
The page ran as a project on Cloudflare Pages, which issues free subdomains under pages.dev. That let the operator put the brand-like string in the hostname without buying a domain. Registration dates to 2025-09-24, close to a year before PhishDestroy detected the page on 2026-09-01. Traffic resolved to a Cloudflare, Inc. address located in Canada. The provider-issued certificate means the padlock icon said nothing about whether the site was legitimate.
If you entered your recovery phrase on this page, treat the wallet as compromised. Initialize a new Ledger with a fresh phrase and move any remaining funds to it immediately. Never reuse the exposed phrase. If you installed software from the page, remove it and reinstall Ledger Live only from Ledger's official site. Remember that Ledger never asks for your 24 words online. Defenders should block the hostname and watch for similar misspelled Ledger strings on free hosting subdomains. Report new copies to the hosting provider and to wallet blocklists.
Last checked
Edge-IP 声誉不属于此域。
Location describes the IP network.
a374d374a3c9f67417d32820341741e4776a7d70a76d10ef343b681f33b1f66aSaved 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 ledgeer-com-app-start.pages.dev · checked Sep 13, 2026
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
ledgeer-com-app-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
可访问→不可用
2→Observation retained
可访问
4/89 engine detections
View sourceNo threat flag
View sourceledgeer-com-app-start.pages.dev
View source已存储 151 个仿冒域名
显示 151 个中的 100 个
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 ↗
ledgeer-com-app-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
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.