Cloudflare Radar
悪意あり
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: eng--desktop-ledgr.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 0/91; URLScan malicious verdict; 2 external blocklist matches…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
悪意あり
レポートを開く悪意あり
レポートを開く0 / 91 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
eng--desktop-ledgr.pages.dev is an impersonation phishing page hosted on a Cloudflare Pages subdomain. Its misspelled name, "desktop-ledgr", points at Ledger hardware wallet users, and urlscan.io detected Ledger branding on the page. PhishDestroy first flagged it on 2026-08-26. The site has been offline since 2026-09-03, and it was still dead and blocked by the provider when last checked on 2026-10-19.
Pages like this copy a trusted wallet brand, often presented as a desktop app or support portal. They then push visitors to type in their recovery phrase or install fake software. Anyone who hands over a seed phrase gives the operator full control of every account derived from it, and the funds can be swept without any further action from the victim. The current page title, "Suspected Phishing | Cloudflare", is the provider's own warning screen. PhishDestroy's classification lists Cloudflare as the impersonated brand, while urlscan.io matched the content to Ledger.
urlscan.io returned a malicious verdict and identified Ledger as the imitated brand. The domain sits on three independent blocklists: PhishDestroy, MetaMask and SEAL. MetaMask and SEAL are both focused on protecting crypto users. VirusTotal tells a different story, with 0 of 91 engines flagging it on 2026-09-03. That clean result came on the day the site went offline, so it shows how far conventional antivirus engines lagged behind crypto-specific detection.
The pages.dev subdomain was created on 2025-09-04, almost a year before PhishDestroy caught it. That timeline suggests it either sat dormant or operated quietly for months. It was served from 188.114.97.9 on Cloudflare's network, geolocated to Canada. Its Google Trust Services (WE1) certificate is issued automatically to Pages projects, so the padlock said nothing about who ran the site.
If you typed your Ledger recovery phrase into this site, treat it as compromised. Set up a new wallet with a fresh phrase on your device and move any remaining funds immediately. If you downloaded a "desktop" app from it, uninstall it, scan the machine and only reinstall Ledger software from the official source. If you connected a browser wallet, review and revoke any token approvals you granted there. Defenders should block the domain, hunt for similar lookalike pages.dev subdomains combining "ledger" misspellings with words like "desktop", and report new ones to the hosting provider.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
970cf0f212014ab7ee6e3b09cf7377da5175919adb53eb853311e60e9008be6cSaved 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 eng--desktop-ledgr.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.
eng--desktop-ledgr.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 source0/91 engine detections
View sourceeng--desktop-ledgr.pages.dev
View source保存された類似ドメイン:142 件
142 件中 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 ↗
eng--desktop-ledgr.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.