VirusTotal
14 / 89 engine detections
打开报告“Ledger Live – Secure Crypto Management App”
冒充 Ledger: manage-device-connects-ledgrs.pages.dev — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 14/89 (alphaMountain.ai, BitDefender, ESET, Forcepoint…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
14 / 89 engine detections
打开报告Threat flag recorded
打开报告no community references
打开报告provider verdict: clean
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
manage-device-connects-ledgrs.pages.dev is an impersonation phishing page that copied Ledger, using the page title "Ledger Live – Secure Crypto Management App". It targeted owners of Ledger hardware wallets. The misspelled "ledgrs" and the "manage-device-connects" wording were chosen to look like an official device-management page. PhishDestroy first saw it on 2026-09-08. It has been offline since 2026-09-17, its content is blocked by the hosting provider, and it was still dead at the last check on 2026-10-19.
Fake Ledger Live pages usually claim the visitor's device needs to be reconnected, synced or verified. They then ask for the 24-word recovery phrase, presented as a routine security step. The phrase is the master key to every account the device protects, so whoever types it in hands the attacker full control of those funds. The thief can then empty the wallet from anywhere, and the hardware device does nothing to stop it. Ledger never asks for a recovery phrase on any website or in any app.
VirusTotal showed 14 of 89 engines flagging the site on 2026-09-18. They included alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safe Browsing and Gridinsoft. Google Safe Browsing classifies it as SOCIAL_ENGINEERING, so Chrome, Firefox and Safari users were warned before the page loaded. Beyond PhishDestroy, the domain is listed by MetaMask's phishing blocklist and by SEAL, so several crypto-focused sources reached the same verdict independently.
The project was created on Cloudflare Pages on 2026-08-22, seventeen days before PhishDestroy detected it. It served from Cloudflare, Inc. address 188.114.97.9, located in Canada. Free pages.dev subdomains take minutes to set up and come with an automatic Google Trust Services certificate. The padlock in the address bar therefore said nothing about whether the page was legitimate. The operation ran for about nine days after detection before the provider pulled the content.
If you entered your recovery phrase on this page, treat the wallet as compromised. Set up a new device or wallet with a fresh phrase and move any remaining funds there immediately, because the attacker can act at any moment. Simply connecting without typing the phrase is far less dangerous, but reset any password you entered and stay alert for follow-up phishing emails. Only download Ledger Live from Ledger's official site and never type your 24 words into a browser. Defenders should block the subdomain and watch for similar Ledger-themed pages.dev names that reuse the "ledgrs" spelling or device-connection wording.
Last checked
Edge-IP 声誉不属于此域。
Location describes the IP network.
b407b350db69ac997342c56e4b7d91bb848088512f0df669cb77e7c96d4cd1d7Saved 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 manage-device-connects-ledgrs.pages.dev · checked Sep 16, 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
manage-device-connects-ledgrs.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→14
可访问→不可用
No flag recorded→Flag recorded
可访问
Threat flag recorded
View source14/89 engine detections
View sourcemanage-device-connects-ledgrs.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 ↗
manage-device-connects-ledgrs.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.