VirusTotal
13 / 89 engine detections
レポートを開く“JAMES”
Ledgerなりすまし: james-co-ledger-app.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 13/89 (BitDefender, Ermes, ESET, Forcepoint ThreatSeeker, Fortinet)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
13 / 89 engine detections
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
james-co-ledger-app.pages.dev is a phishing page that impersonates Ledger, the hardware wallet maker, and targets people who hold crypto on Ledger devices. PhishDestroy first saw it on 2026-09-15. The site has been offline since 2026-09-21, and the hosting provider has blocked its content. It was still down when last checked on 2026-10-19.
Fake Ledger pages usually claim there is a firmware problem, a security alert or a required app update. The visitor is then asked to 'restore' or 'verify' the wallet by typing in the 24-word recovery phrase. Anyone who holds that phrase controls the funds, so the operators can empty the wallet from their own device without ever touching the victim's hardware. The page carried the title 'JAMES' rather than any Ledger branding. We classified it as Ledger impersonation based on its domain and purpose.
Thirteen of 89 VirusTotal engines flagged the domain when it was checked on 2026-09-21. The flagging vendors include BitDefender, ESET, Kaspersky, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft and Ermes. That is a meaningful spread of independent security vendors for a short-lived free subdomain. Beyond PhishDestroy, the domain is listed on the MetaMask and SEAL blocklists, so wallet users and crypto security responders were warned independently.
The page was not a registered domain but a project subdomain on Cloudflare Pages. Attackers favour free hosting like this because a new site can be deployed in minutes and inherits a trusted parent domain. Traffic resolved to Cloudflare, Inc. address space geolocated to Canada. Its TLS certificate came from WE1, an issuer used routinely for such deployments, so the padlock in the browser said nothing about whether the page was genuine. The offline date of 2026-09-21 came six days after first detection.
If you typed your Ledger recovery phrase into this page, treat that wallet as compromised. Set up a new wallet with a fresh phrase on your device and move any remaining funds there immediately. Never reuse the exposed phrase. Ledger never asks for your recovery phrase on a website, by email or in chat, and genuine updates happen only through Ledger's official app. If you only visited without entering anything, no funds are at risk, but clear saved form data and be wary of follow-up messages. Defenders should block the domain and watch for sibling projects on the same hosting platform that combine 'ledger' with personal names or 'app' keywords.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
Saved 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
james-co-ledger-app.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
https://radar.cloudflare.com/scan/d20e21b8-d479-4383-8b96-81488562a076
到達可能→利用不可
到達可能
No threat flag
View source13/89 engine detections
View sourcejames-co-ledger-app.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 ↗
james-co-ledger-app.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.