VirusTotal
3 / 89 engine detections
レポートを開く“Ledger® Live — Getting Started”
Ledgerなりすまし: ledgeer-live-io.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 3/89 (alphaMountain.ai, Kaspersky, LevelBlue); 2 external blocklist…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
3 / 89 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
ledgeer-live-io.pages.dev impersonated Ledger. It presented itself as "Ledger® Live — Getting Started" and was aimed at people setting up or troubleshooting a Ledger hardware wallet. The doubled "e" in "ledgeer" is easy to miss at a glance. PhishDestroy first flagged it on 2026-09-01. The site has been offline since 2026-09-13, its content blocked by the hosting provider, and it was still dead at the last check on 2026-10-19.
Fake "Getting Started" pages copy Ledger's onboarding flow because new and returning users expect to follow setup steps without questioning them. Pages like this typically walk the visitor toward a prompt to "restore" or "verify" the wallet by typing in the 24-word recovery phrase, or toward downloading a counterfeit Ledger Live app that asks for the same thing. Genuine Ledger software never asks for a recovery phrase on a website or computer. Anyone who types it in hands over full control of every account on that device, and the funds can be moved without the hardware wallet ever being touched.
Vendor coverage was thin. When VirusTotal scanned the site on 2026-09-14, only 3 of 89 engines flagged it: alphaMountain.ai, Kaspersky and LevelBlue. A low score like this is common for short-lived pages on free hosting and should not be read as a sign the site was safe. Stronger confirmation comes from crypto-focused blocklists: besides PhishDestroy, the domain is listed by MetaMask and SEAL, both of which track wallet-targeting fraud specifically.
The site ran as a project on Cloudflare Pages, a free static-hosting service that hands out subdomains under pages.dev with no ownership checks. Registration is dated 2025-10-14, nearly eleven months before PhishDestroy detected it. It was served from Cloudflare's network with a Canadian geolocation. Its certificate came from Google Trust Services, issued automatically, so the padlock in the browser said nothing about who ran the page.
If you entered your recovery phrase on this site, assume it is compromised. Set up a new device or reset your Ledger with a freshly generated phrase, then move your remaining funds to the new accounts immediately. If you installed any "Ledger Live" software reached through this page, uninstall it, scan the machine, and get the app only through Ledger's official channels. If you only viewed the page without typing anything, no action is needed beyond staying wary of lookalike Ledger pages. Defenders should block the hostname, watch for pages.dev subdomains carrying "ledger" variants, and report new copies to the hosting provider for fast removal.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
5084bd793fd2552e8c014e96079b29d0d340eb2fd9cf96d77c97a1b0f21b65abSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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-live-io.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
到達可能→利用不可
到達可能
No threat flag
View source3/89 engine detections
View sourceledgeer-live-io.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-live-io.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.