VirusTotal
10 / 89 engine detections
レポートを開く“ledger desktop”
Ledgerなりすまし: ledgerr-desk-top.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 10/89 (alphaMountain.ai, BitDefender, CyRadar, ESET, Fortinet); URLScan…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
10 / 89 engine detections
レポートを開く悪意あり
レポートを開く悪意あり
レポートを開くno community references
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
ledgerr-desk-top.pages.dev is a phishing page impersonating Ledger, the hardware wallet maker. Its title, "ledger desktop", is aimed at Ledger owners looking for the companion desktop app. The doubled "r" and hyphenated "desk-top" are a typosquat meant to pass a quick glance. PhishDestroy first flagged it on 2026-08-31. The site has been offline since 2026-09-11 after the hosting provider blocked its content, and it was still dead on 2026-10-19.
Fake "Ledger desktop" pages usually catch people who search for Ledger's software and click a lookalike result or link. The victim is then pushed to a counterfeit download, or told the wallet needs "syncing" or "recovery" and asked to type in the 24-word recovery phrase. A Ledger device never needs its recovery phrase entered on a website or into a pop-up. Anyone who hands over that phrase gives the thieves full control of every account it secures, and they can empty the wallet without ever touching the physical device.
On 2026-09-11, ten of 89 VirusTotal engines flagged the site, including alphaMountain.ai, BitDefender, CyRadar, ESET, Fortinet, Kaspersky, Lionic and Sophos. That is a modest share, but it comes from well-known vendors that agree independently. urlscan.io rated the page malicious and recognised Ledger branding on it, which supports the impersonation classification. The domain also appears on the MetaMask and SEAL blocklists as well as PhishDestroy's own.
The site ran as a free subdomain on Cloudflare Pages, served from Cloudflare's network with a Canadian geolocation. The project dates to 2025-09-26, almost a year before PhishDestroy caught it. Free static-hosting platforms let operators put up a convincing page quickly and abandon it once blocked, which is how this one ended.
If you typed your recovery phrase into this site or into software downloaded from it, treat that wallet as compromised. Set up your Ledger with a new phrase and move any remaining funds to the new accounts right away. If you installed anything from the page, uninstall it, scan the computer, and get Ledger Live only from Ledger's official site. If you connected a hot wallet or signed transactions there, revoke token approvals as well. Defenders should block the domain, watch for similar lookalike pages.dev subdomains using Ledger's name, and report new copies to the hosting provider and to PhishDestroy.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
Saved 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
ledgerr-desk-top.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 source10/89 engine detections
View sourceledgerr-desk-top.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 ↗
ledgerr-desk-top.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.