VirusTotal
10 / 89 engine detections
レポートを開く“Setup Ledger Hardware Wallet — Crypto WendyO”
Ledgerなりすまし: ledger--hardwere-wallet--run.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 10/89 (alphaMountain.ai, BitDefender, CyRadar, ESET…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
10 / 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
This Cloudflare Pages site impersonated Ledger. Its title, "Setup Ledger Hardware Wallet — Crypto WendyO", pitched it as an onboarding page for people configuring a new Ledger device. The misspelled "hardwere" in the address is easy to miss at a glance. PhishDestroy first saw it on 2026-09-01. The site has been offline since 2026-09-14, and the hosting provider was still blocking its content when we last checked on 2026-10-19.
Fake Ledger setup pages exploit the moment a new owner is most likely to follow instructions without question. The page walks the visitor through a supposed setup or verification step. Sooner or later it asks for the 24-word recovery phrase, or for a wallet connection presented as part of activation. Anyone holding that phrase can rebuild the wallet on their own device and empty it, so the victim loses every asset tied to that seed, not just what sits in one account. Ledger never asks for a recovery phrase on a website, and that request alone marks a page like this as fraudulent.
When VirusTotal scanned the site on 2026-09-15, 10 of 89 engines flagged it. The vendors included BitDefender, ESET, Kaspersky, Fortinet, G-Data, Lionic, CyRadar and alphaMountain.ai. That count is modest, but it comes from several unrelated security vendors. urlscan.io returned a malicious verdict and identified Ledger as the imitated brand. MetaMask and SEAL list the site alongside PhishDestroy, so wallet users relying on those protections would have received warnings.
The project was created on 2026-07-23, about 40 days before PhishDestroy caught it. It was hosted on Cloudflare Pages, a free static hosting service that is easy to set up again under a new name. Traffic resolved to Cloudflare's network, geolocated to Canada. The pages.dev subdomain carried a valid Google Trust Services certificate, so the browser padlock gave no hint that anything was wrong.
If you typed your recovery phrase into this site, treat that seed as compromised. Set up a fresh wallet with a new phrase, ideally after resetting your Ledger, and move any remaining funds to it immediately. If you only connected a wallet, review and revoke any token approvals you granted around that time. If you browsed without entering anything, no action is needed beyond avoiding look-alike setup pages, and you should only set up a device through Ledger's official app. Defenders should block lookalike pages.dev subdomains that combine Ledger branding with setup or wallet wording, and report new ones to Cloudflare quickly.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
3683ef0f505735fa27222c9553fc46922108a550eead919b450bd654a3f9050cSaved 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 ledger--hardwere-wallet--run.pages.dev · checked Sep 13, 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
ledger--hardwere-wallet--run.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 sourceledger--hardwere-wallet--run.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 ↗
ledger--hardwere-wallet--run.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.