VirusTotal
15 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
フィッシング: ledgrr-livv-app.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 15/89 (alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
15 / 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
ledgrr-livv-app.pages.dev is an impersonation phishing page. Its name is a deliberate misspelling of Ledger Live, the companion app for Ledger hardware wallets, so it targets people who own or manage crypto on those devices. PhishDestroy first saw it on 2026-09-08. It went offline on 2026-09-16, eight days later, and was still dead when last checked on 2026-10-19. The hosting provider has blocked its content.
Fake Ledger Live pages usually claim the user must sync, update or repair the app. They then ask for the 24-word recovery phrase, which no legitimate Ledger product ever requests. Anyone who types that phrase gives the attacker full control of every account derived from it, and the attacker can empty those accounts from anywhere without touching the physical device. The page now shows the title "Suspected Phishing | Cloudflare", which is the provider's warning screen rather than the original lure. We classify the site as Ledger-themed impersonation.
On 2026-09-18, VirusTotal showed 15 of 89 engines flagging the site. They included BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, alphaMountain.ai and CyRadar. urlscan.io returned a malicious verdict. Its brand match, generic Cloudflare, reflects the warning page now in place. The domain is also on the MetaMask and SEAL blocklists alongside PhishDestroy, so wallet software and crypto security responders identified the same threat independently.
The site was published as a project on Cloudflare Pages. This free hosting service lets attackers stand up a lookalike under a trusted shared domain in minutes, with no registration of their own. Traffic resolved to Cloudflare, Inc. infrastructure geolocated in Canada. The short gap between first sighting and the provider taking the content down is typical of throwaway Pages deployments, and the same operator may simply redeploy under a new subdomain.
If you entered your recovery phrase on this site, treat it as compromised. Set up a new Ledger, or reset your current one, with a fresh phrase, and move any remaining funds to it immediately. Do not import the old phrase anywhere. If you connected a software wallet, review and revoke token approvals you do not recognize. Defenders should block pages.dev subdomains that mimic wallet brands, report new variants to Cloudflare's abuse team, and remind users that recovery phrases belong only on the hardware device itself.
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 ledgrr-livv-app.pages.dev · checked Sep 16, 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 source15/89 engine detections
View sourceledgrr-livv-app.pages.dev
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
ledgrr-livv-app.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 ↗
ledgrr-livv-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.