VirusTotal
4 / 92 engine detections
Raporu aç“LedgerOS v771”
Ledger taklidi: ledgeros.pages.dev — Bilinen son aktif (HTTP 200). Kanıt özeti: VirusTotal 4/92 (alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
4 / 92 engine detections
Raporu açno community references
Raporu açprovider verdict: clean
Raporu açNo threat flag
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
ledgeros.pages.dev is a phishing page that impersonates Ledger, the hardware wallet maker, under the invented product name "LedgerOS v771." It targets Ledger owners who might believe they are getting an official system or firmware release. PhishDestroy first flagged it on 2026-08-28. The site was still online and serving its content on 2026-10-19.
Ledger does not distribute a product called "LedgerOS." A versioned title like "v771" is meant to make the page look like a routine software update. Fake Ledger update pages usually push one of two things. Some tell the visitor to type in the 24-word recovery phrase to "restore" or "verify" the device. Others offer a download that is really malware. Either way, once the attacker has the recovery phrase, they can rebuild the wallet on their own hardware and empty it, and the hardware device offers no protection after the phrase is exposed.
Detection by antivirus engines is thin. On 2026-10-12, 4 of 92 VirusTotal engines flagged the page: alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet and desenmascara.me. Most scanners would therefore let it through. Crypto-focused blocklists give stronger coverage, because MetaMask and SEAL list it alongside PhishDestroy. Wallet users browsing with MetaMask may see a warning, but users of ordinary browsers often will not.
The project was set up on Cloudflare Pages on 2026-04-16, roughly four and a half months before PhishDestroy caught it. That gap suggests the page ran unnoticed for some time or was held in reserve. It lives on a free pages.dev subdomain on Cloudflare's network, geolocated to Canada. Because the subdomain sits under a widely trusted platform name, link filters and casual readers are less likely to treat it as suspicious.
If you entered your recovery phrase on this page, treat the wallet as compromised. Set up a new device or reset your current one with a fresh phrase, then move any remaining assets immediately. Do not reuse the old phrase anywhere. If you downloaded and ran anything from the site, disconnect that computer, scan it thoroughly, and stop using it for crypto until it has been cleaned or reinstalled. Get Ledger software only through Ledger's official channels, and never type your recovery phrase into a website or app. Security teams should block ledgeros.pages.dev and report it to Cloudflare for takedown.
Last checked
Edge-IP itibarı bu etki alanıyla ilişkilendirilmez.
Location describes the IP network.
94498d2c35a17ed8c20169eda428b3088a1208670f23def122b3a8da10c15999Saved 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 ledgeros.pages.dev · checked Sep 7, 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.
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
ledgeros.pages.dev
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Bilinmiyor→live_content
content_served
live_content
content_served
Erişilebilir
4/92 engine detections
View sourceNo threat flag
View sourceledgeros.pages.dev
View source151 kayıtlı benzer alan adı
151 kaydın 100 kadarı gösteriliyor
Listed domains receive at least one abuse report; this entry has no retained notification history.
Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
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 ↗
ledgeros.pages.dev)Tüm ayrıntıları bilmeseniz bile — yine de şikayette bulun. Kısmi bilgiler de soruşturmalara yardımcı olmaktadır.
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
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin
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.