VirusTotal
11 / 89 engine detections
レポートを開く“How to Set up Ledger Portfolio & Wallet App”
Ledgerなりすまし: io-ledger-com--start.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 11/89 (alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 89 engine detections
レポートを開くThreat flag recorded
レポートを開く悪意あり
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
io-ledger-com--start.pages.dev impersonated Ledger behind the title "How to Set up Ledger Portfolio & Wallet App". It targeted people setting up a Ledger hardware wallet or its companion app. The hostname packs "io", "ledger" and "com" together to look like an official address, but it is a free Cloudflare Pages subdomain. PhishDestroy first flagged it on 2026-09-07. The site has been offline since 2026-09-16, and the hosting provider had blocked its content as of 2026-10-19.
Fake Ledger setup guides catch users at a vulnerable moment, when they expect to follow on-screen instructions with a new device. Pages like this typically walk the victim through a fake onboarding flow. That flow ends in a request to type in the 24-word recovery phrase, or in a download of a counterfeit wallet app that collects it. Ledger never asks for the recovery phrase on a website or in software. Anyone who has the phrase can rebuild the wallet elsewhere and empty every account it controls, and stolen funds cannot be recovered.
On 2026-09-17, 11 of 89 VirusTotal engines flagged the site. The flagging vendors included alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safe Browsing and Kaspersky. Google Safe Browsing classed it as social engineering, which triggers browser warnings for visitors. urlscan.io returned a malicious verdict and matched the page to the Ledger brand. Beyond PhishDestroy, the MetaMask and SEAL blocklists also list it, so wallet software and security responders can block it directly.
The subdomain was created on 2026-08-06, about a month before PhishDestroy caught it, so it had a window of several weeks to reach victims. It was served through Cloudflare Pages on Cloudflare network address 188.114.97.9, geolocated to Canada. Free static hosting like this lets operators launch lookalike pages quickly and replace them once they are taken down. Variants under other pages.dev names should be expected.
If you typed your recovery phrase into this page, treat the wallet as compromised. Set up a new device or reset your Ledger with a fresh phrase, then move any remaining funds there immediately. A leaked phrase cannot be secured or changed. If you installed software from the page, uninstall it, run a full malware scan, and download Ledger's app only through the official channel. If you connected a wallet and signed anything, review and revoke unfamiliar token approvals. Defenders should block this hostname and watch for similar "ledger" subdomains on pages.dev and other free hosting platforms.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
3f3403260eb15389679f6d3faa8ce0c691b99f6d5e7966f6e86a5f65729bcf42Saved 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 io-ledger-com--start.pages.dev · checked Sep 15, 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
io-ledger-com--start.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 flag recorded→Flag recorded
到達可能
Threat flag recorded
View source11/89 engine detections
View sourceio-ledger-com--start.pages.dev
View source保存された類似ドメイン:151 件
151 件中 100 件を表示
コミュニティ報告:1 件
カテゴリPHISHING
Phishing site impersonating Ledger: https://io-ledger-com--start.pages.dev/ Basis: a credential-harvesting or wallet-connect flow was confirmed on the live page; independently corroborated by 1 external source(s) (urlscan:verdict(score=100)). Hosted on Cloudflare Pages. First se
“Phishing site impersonating Ledger: https://io-ledger-com--start.pages.dev/ Basis: a credential-harvesting or wallet-connect flow was confirmed on the live page; independently corroborated by 1 external source(s) (urlscan:verdict(score=100)). Hosted on Cloudflare Pages. First seen 2026-08-05 23:00:28; last confirmed live 2026-09-07 02:46:05. The site was confirmed live at the time of reporting. Reported by an automated phishing-monitoring pipeline; official Ledger domains are excluded from rep”
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 ↗
io-ledger-com--start.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.