VirusTotal
4 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
認証情報フィッシング: us-ledgr-logins.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 4/89 (Forcepoint ThreatSeeker, LevelBlue, VIPRE, Webroot); 2 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 89 engine detections
レポートを開く悪意あり
レポートを開くno community references
レポートを開く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
us-ledgr-logins.pages.dev is a credential phishing page whose name imitates Ledger, the hardware wallet brand, with the misspelling "ledgr" and a "us-" prefix meant to pass as a regional login portal. It targets Ledger owners who search for a way to sign in or manage their wallet. PhishDestroy first flagged it on 2026-09-16. The site has been offline since 2026-09-21, with its content blocked by the hosting provider, and it was still down when last checked on 2026-10-19.
Fake Ledger "login" pages exploit the fact that Ledger hardware wallets have no web login at all. A visitor is shown a sign-in or verification form that asks for account details or, more damaging, the 24-word recovery phrase. Anyone who types a recovery phrase into such a page hands over full control of the wallet, and the attacker can empty it from any device. The page now carries the title "Suspected Phishing | Cloudflare", which is Cloudflare's own warning screen rather than the scam content we classified as credential phishing.
On 2026-09-21, 4 of 89 VirusTotal engines flagged the address: Forcepoint ThreatSeeker, LevelBlue, VIPRE and Webroot. That is a low count, typical for short-lived phishing on shared hosting, so the stronger signal comes from crypto-focused lists. Besides PhishDestroy, the domain is blocked by MetaMask and SEAL, both of which track threats against wallet users specifically. Cloudflare's own block of the content independently confirms the phishing verdict.
The site was published as a free subdomain on Cloudflare Pages, so there was no domain to register and it could go live within minutes. It resolved to Cloudflare, Inc. address space geolocated to Canada. Free hosting of this kind lets operators discard a flagged page and spin up a lookalike under a new name, so similar Ledger-themed subdomains are likely to follow.
If you entered your Ledger recovery phrase on this site, treat the wallet as compromised: set up a device with a fresh recovery phrase and move your funds to it immediately, before the attacker does. If you entered an email address or password, change them wherever they are reused and turn on two-factor authentication. Remember that Ledger will never ask for your recovery phrase on any website. Defenders should block the pages.dev subdomain and watch for new Pages and similar free-hosting subdomains combining "ledger" misspellings with "login" wording.
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.
Google PageSpeed Insights — mobile performance audit of us-ledgr-logins.pages.dev · checked Sep 21, 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
到達可能→利用不可
到達可能
No threat flag
View source4/89 engine detections
View sourceus-ledgr-logins.pages.dev
View source保存された類似ドメイン:79 件
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
us-ledgr-logins.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 ↗
us-ledgr-logins.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.