VirusTotal
8 / 89 engine detections
Raporu aç“Site not found · GitHub Pages”
Ledger taklidi: jaweriakhan6906.github.io — İçerik kullanılamıyor (HTTP 404). Kanıt özeti: VirusTotal 8/89 (alphaMountain.ai, Forcepoint ThreatSeeker…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
8 / 89 engine detections
Raporu açZararlı
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
jaweriakhan6906.github.io is a phishing page that impersonated Ledger, the hardware wallet maker. It was hosted on a free GitHub Pages user subdomain and aimed at people who keep crypto on Ledger devices. PhishDestroy first flagged it on 2026-09-06. The site has been offline since 2026-09-11 and still served no content when checked on 2026-10-19.
Fake Ledger pages usually copy the brand's look and claim the visitor must update firmware, verify the device or restore access. The victim is then asked to type their 24-word recovery phrase into a web form. Anyone holding that phrase can rebuild the wallet on their own device and empty it, and the hardware wallet offers no protection once the phrase leaves it. The page title now reads "Site not found · GitHub Pages", which is GitHub's default error for a removed site, while we classified the earlier content as Ledger impersonation.
urlscan.io returned a malicious verdict and identified Ledger branding on the page, which independently confirms the impersonation. On 2026-09-11, 8 of 89 VirusTotal engines flagged the site: alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, LevelBlue, Sophos and Webroot. That is a modest count, but it is typical for short-lived pages on trusted shared domains like github.io, where many engines hesitate to flag a subdomain. PhishDestroy lists the domain on its blocklist.
The operator did not register a domain. They used a GitHub account subdomain, so the registrar is GitHub, Inc. and traffic was served through Fastly's US network, which carries all GitHub Pages sites. This setup costs nothing, comes with HTTPS automatically, and borrows the reputation of github.io. It is also easy to take down, which fits the roughly five days between first detection and the site going dark.
If you entered your Ledger recovery phrase on this page, treat the wallet as compromised. Set up a new wallet with a new phrase, ideally on a reset or new device, and move any remaining funds there right away. Ledger never asks for your recovery phrase online, by email or through an app. If you also connected a software wallet, review and revoke any token approvals you do not recognise. Defenders should block this specific subdomain rather than all of github.io and report similar Ledger-themed GitHub Pages sites to GitHub for removal.
Edge-IP itibarı bu etki alanıyla ilişkilendirilmez.
Location describes the IP network.
71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84github.comgithub.iogithubusercontent.comSaved 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 jaweriakhan6906.github.io · checked Sep 6, 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.
jaweriakhan6906.github.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
hosting_placeholder · placeholder_page
Bilinmiyor→inactive
hosting_placeholder · placeholder_page
Bilinmiyor→inactive
hosting_placeholder · placeholder_page
6→8
Erişilebilir→Mevcut değil
Erişilebilir
No threat flag
View source8/89 engine detections
View sourcejaweriakhan6906.github.io
View sourcePage captured
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 ↗
jaweriakhan6906.github.io)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.