VirusTotal
12 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Ledgerなりすまし: ai-ledger-en-main.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 12/89 (alphaMountain.ai, BitDefender, ESET, Emsisoft, Forcepoint…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
12 / 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
ai-ledger-en-main.pages.dev is an impersonation phishing page posing as Ledger, the hardware wallet maker, and aimed at people who keep crypto on Ledger devices. PhishDestroy first flagged it on 2026-08-10. The site has been offline since 2026-09-13, and when last checked on 2026-10-19 its content was blocked by the hosting provider.
Fake Ledger pages usually present an urgent 'update', 'sync' or 'security check' for Ledger Live. The victim is then asked to type in their 24-word recovery phrase, which a genuine Ledger product never requests. Anyone holding that phrase can rebuild the wallet on their own device and empty every account it controls, so the loss is total and irreversible. The page title now reads 'Suspected Phishing | Cloudflare', which is the provider's warning interstitial rather than Ledger branding. The Ledger impersonation classification refers to the content the page served before the block.
On 2026-09-14, 12 of 89 VirusTotal engines flagged the address. Those engines include alphaMountain.ai, BitDefender, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data and Lionic. That is a modest share, but these are independent vendors reaching the same verdict. The domain also appears on the MetaMask and SEAL blocklists alongside PhishDestroy, so wallet users with those protections would have been warned. The hosting provider's own phishing block adds a further, separate confirmation.
This is a free Cloudflare Pages subdomain rather than a purchased domain. It was created on 2025-11-05, roughly nine months before PhishDestroy detected it on 2026-08-10. The 'ai-ledger-en-main' name mimics a localized, official-sounding project deployment, which helps it pass a quick glance. Hosting sits on Cloudflare's network with the address geolocated to Canada, and Cloudflare also cut off the content.
If you entered your Ledger recovery phrase on this site, treat that wallet as compromised. Set up a new device or reset your current one with a freshly generated phrase, then move all remaining funds there immediately, before anything else drains. If you only connected a wallet or signed transactions, review and revoke any token approvals you do not recognize. If you merely browsed and typed nothing, no action is needed beyond avoiding the link. Defenders should block the full pages.dev hostname, and anyone who finds further Ledger-themed Pages deployments with similar naming should report them to the provider and to PhishDestroy.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
edc1dd18a777b1e4fad4508d54aa62563556065c338f79f9b37d9f9f3f318008Saved 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.
ai-ledger-en-main.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 source12/89 engine detections
View sourceai-ledger-en-main.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 ↗
ai-ledger-en-main.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.