VirusTotal
9 / 91 engine detections
レポートを開く“®Ledger® Live: Login | Getting started™ with Ledger®”
認証情報フィッシング: en-us-ledgr-livelgn.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 9/91 (alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
9 / 91 engine detections
レポートを開く悪意あり
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This Cloudflare Pages subdomain posed as a Ledger Live sign-in page. Its trademark-cluttered title, "®Ledger® Live: Login | Getting started™ with Ledger®", targeted people setting up or reconnecting a Ledger hardware wallet. PhishDestroy first flagged it on 2026-08-26. The page has been offline since 2026-09-03, when the hosting provider blocked its content, and it was still dead when rechecked on 2026-10-19.
Fake Ledger Live pages exploit a common belief that the wallet needs an online "login" or "getting started" step. The visitor is walked through a convincing setup flow and asked to type in account details or, most damaging, the 24-word recovery phrase. Ledger never asks for that phrase on a website. Anyone who holds it can rebuild the wallet on their own device and empty it, and the hardware wallet cannot stop that.
On 2026-09-03, nine of 91 VirusTotal engines flagged the address. The detecting vendors include BitDefender, ESET, Kaspersky, Fortinet, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai and LevelBlue, a spread of independent consumer and enterprise vendors. urlscan.io returned a malicious verdict, although its brand detection matched only a generic Cloudflare template rather than Ledger itself. Beyond PhishDestroy, the domain sits on the MetaMask and SEAL blocklists, so wallet-focused security teams have independently confirmed it.
The site ran on Cloudflare Pages, a free static hosting service whose subdomains cost nothing to create and are easy to replace. The registration date on record is 2025-11-06, about nine months before PhishDestroy detected the page. The site was served through Cloudflare's network from an address located in Canada, with a Google Trust Services certificate. That padlock is issued automatically on this platform and says nothing about whether the site is legitimate. The misspelled "ledgr" and the "en-us" prefix are meant to look like a regional official page at a glance.
If you entered your recovery phrase here, treat that wallet as compromised. Initialize a wallet with a new phrase on a genuine Ledger device and move any remaining funds there at once. If you reused a password or email login on the page, change it everywhere it was used and turn on two-factor authentication. Only install Ledger Live from Ledger's official site, and ignore any page asking for your seed. Defenders should block the domain and watch for similar pages.dev subdomains that combine misspellings of "ledger" with "live" or "login".
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
ce07bff02182805d4444df7285df7d473fa0803e08615e11baec9d2148d43ed9Saved 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 en-us-ledgr-livelgn.pages.dev · checked Sep 2, 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
en-us-ledgr-livelgn.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
1→9
到達可能→利用不可
到達可能
No threat flag
View source9/91 engine detections
View sourceen-us-ledgr-livelgn.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 ↗
en-us-ledgr-livelgn.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.