Cloudflare Radar
悪意あり
レポートを開く“Suspected Phishing | Cloudflare”
Ledgerなりすまし: live-cloud-ledger.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 0/89; URLScan malicious verdict; 2 external blocklist matches…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
悪意あり
レポートを開く悪意あり
レポートを開く0 / 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
live-cloud-ledger.pages.dev is a phishing page that impersonates Ledger, the hardware wallet maker, and targets people who keep crypto on a Ledger device. The "live" and "cloud" in the name suggest an official Ledger Live or cloud backup service, which Ledger does not offer at this address. PhishDestroy first saw it on 2026-09-08. The site has been offline since 2026-09-16, and the hosting provider was still blocking its content on 2026-10-19.
Ledger impersonation pages usually claim the visitor must sync, verify or restore a wallet, then ask for the 24-word recovery phrase. Anyone who holds that phrase can rebuild the wallet on their own device and empty it, and the hardware wallet gives no protection once the phrase is typed into a website. The page currently shows the title "Suspected Phishing | Cloudflare". That is the provider's warning interstitial, not the original lure, so it does not conflict with our Ledger impersonation classification.
urlscan.io rated the site malicious. Its brand tag "genericcloudflare" reflects the Cloudflare warning page rather than the original content. Beyond PhishDestroy, the domain is listed on the MetaMask and SEAL blocklists, both of which focus on crypto threats. VirusTotal showed 0 detections out of 89 engines on 2026-09-18, two days after the site went dark. A clean VirusTotal result here says nothing reassuring about the page.
The subdomain was created on Cloudflare Pages on 2026-07-19, about seven weeks before PhishDestroy flagged it. Free static hosting on a shared platform domain lets operators launch quickly and borrow the provider's reputation. It resolves to Cloudflare, Inc. network space located in CA. Its Google Trust Services certificate is the standard one for Pages sites and does not indicate legitimacy.
If you entered your Ledger recovery phrase on this site, treat it as compromised. Set up a new wallet with a fresh phrase, ideally after resetting your device, and move any remaining funds there immediately, because a phrase cannot be changed or revoked. If you connected a software wallet, revoke any token approvals you granted. Remember that Ledger will never ask for your recovery phrase online. Security teams should block the domain, watch for other pages.dev lookalikes using Ledger branding, and report new ones to the hosting provider.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
d0c8dae54e089546f6eea0ce84f586acc896bfc42c93e8e984db964861e3634eSaved 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 live-cloud-ledger.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.
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
14→Observation retained
到達可能→利用不可
到達可能
No threat flag
View source0/89 engine detections
View sourcelive-cloud-ledger.pages.dev
View source保存された類似ドメイン:151 件
151 件中 100 件を表示
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
live-cloud-ledger.pages.dev
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 ↗
live-cloud-ledger.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.