VirusTotal
3 / 89 engine detections
보고서 열기“Ledger Getting Started Hub — The Official Guide to Hardware Wallet Setup and Digital Asset Security”
Ledger 사칭: ledgr-get-ledgr.pages.dev — 연결 가능 · 액세스가 제한됨 (HTTP 403). 증거 요약: VirusTotal 3/89 (alphaMountain.ai, Forcepoint ThreatSeeker, LevelBlue); 2 external…
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
3 / 89 engine detections
보고서 열기no community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
ledgr-get-ledgr.pages.dev is a phishing page impersonating Ledger, the hardware wallet maker. It called itself the "Ledger Getting Started Hub — The Official Guide to Hardware Wallet Setup and Digital Asset Security" and was aimed at people unboxing or setting up a Ledger device. PhishDestroy first flagged it on 2026-09-08. The site has been offline since 2026-09-17, and on 2026-10-19 it was still dead, with its content blocked by the hosting provider.
Fake "getting started" pages target the moment a new owner is most likely to follow instructions without questioning them. Scams of this type typically walk the visitor through a convincing setup flow, then ask them to type in their recovery phrase, or push a counterfeit companion app that does the same. Ledger never asks for the recovery phrase on a website or in a form. Anyone who handed it over gave the operators full control of every account derived from that seed, and they can empty those accounts without touching the physical device.
Wallet-security blocklists caught this one before generic scanners did. Besides PhishDestroy, it is listed by MetaMask and SEAL, which means MetaMask users were warned before the page could load. On VirusTotal only 3 of 89 engines flagged it as of 2026-09-18: alphaMountain.ai, Forcepoint ThreatSeeker and LevelBlue. That low count is typical for short-lived brand phishing and does not suggest the page was safe.
The page was a free project on Cloudflare Pages. It was created on 2026-08-16, about three weeks before PhishDestroy detected it, and lived under a misspelled "ledgr" name rather than any Ledger-owned domain. It was served from Cloudflare's network, with the address geolocating to Canada. Its Google Trust Services certificate gave it the browser padlock, which proves only that the connection was encrypted, not that the site was legitimate. The provider block that took it offline came after only about nine days of activity under our watch.
If you entered your 24-word recovery phrase on this page, treat it as stolen. Set up your Ledger again with a brand-new phrase and move any remaining funds to the new accounts immediately. Never reuse or re-import the old seed. If you downloaded any software through the page, uninstall it, scan the machine, and get Ledger Live only from Ledger's official site. Defenders should block the domain, watch for other pages.dev projects using "ledgr" or Ledger setup wording, and report new copies to Cloudflare for takedown.
Last checked
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
Location describes the IP network.
5d09b9b67ee32dcfab13348b36fe3b68080f99671125c320a777570264e50692Saved 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 ledgr-get-ledgr.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.
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
ledgr-get-ledgr.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 source3/89 engine detections
View sourceledgr-get-ledgr.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 ↗
ledgr-get-ledgr.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
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.