Ir para o relatório de segurança
Segurança de domínio e inteligência contra ameaças
jaweriakhan6906.github.io favicon

jaweriakhan6906.github.io

“Site not found · GitHub Pages”

Registrador
GitHub
Resolved IP
185.199.111.153
PhishDestroy assessment Crítico
Disponibilidade Conteúdo indisponível O conteúdo estava indisponível na última observação Observado · HTTP probe
Detecções do VirusTotal: 8/89 Rótulo automático de marca: Ledger
06/09/2026 CDN
API
Este domínio foi sinalizado como malicioso
Mecanismos de segurança relatando uma detecção: 8. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Resumo do relatório

Imitação de Ledger: jaweriakhan6906.github.io — Conteúdo indisponível (HTTP 404). Resumo das evidências: VirusTotal 8/89 (alphaMountain.ai, Forcepoint…

A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.

Source evidenceVirusTotal 8 / 89 5 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Crítico
VirusTotal
8 / 89
Page captures
2

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Captura armazenada · 2 captures

Domain details

Domínio
URLScan verdict Malicioso score 100 Phishing brand: Ledger report ↗
IP Context Fastly shared edge origin IP hidden A reputação do Edge-IP não é atribuída a este domínio.
Provedor de plataforma GitHub US(US)
Contato para abusosabuse@github.com
Status HTTP404 Not Found
Tempo até a primeira indisponibilidade 4 days
O que contabilizamos Tempo decorrido desde a primeira denúncia de abuso armazenada até a primeira observação de que o conteúdo estava indisponível. Isto não estabelece a causa.
O que cada relatório contém Os registros de relatórios de saída armazenados podem fazer referência a evidências disponíveis no momento, como veredictos de fornecedores, dados de registro, detalhes de hospedagem, classificações ou capturas de tela. Esta página não infere a carga exata entregue, recebimento, confirmação ou ação de um destinatário.
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez06/09/2026
DOM Analysisanalyzed 06/09/2026score 68/1001 brand signal
Submitted URLhttp://jaweriakhan6906.github.io/ledger
Favicon Hash
Observed page title
Site not found · GitHub Pages
Automated brand references
Ledger
Certificado TLS
Emitido por Let's Encrypt · stored validity ends in 53 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
185.199.111.153
Network ASN
AS54113
Organization
Fastly, Inc.
Observed location
San Francisco, US
Server header
GitHub.com

A reputação do Edge-IP não é atribuída a este domínio.

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt
Valid from
2026-08-02 23:38:02
Valid until
2026-10-31 23:38:01
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-06 16:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprint71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84
Certificate names · 3 SANs
  • github.com
  • github.io
  • githubusercontent.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Tecnologias · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este domínio Envie evidências e ajude a proteger outras pessoas

Análise do VirusTotal

8 / Os fornecedores de segurança 89 sinalizaram este domínio
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
LevelBlue
Sophos
Webroot
Análise de desempenho do site

Google PageSpeed Insights — mobile performance audit of jaweriakhan6906.github.io · checked Sep 6, 2026

100
Good
Performance
FCP
0.79s
First Contentful Paint
LCP
0.79s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.79s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

jaweriakhan6906.github.io
Resultado salvo
Cloaked / Filtered
Stored observation history12

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Desconhecido→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Desconhecido→inactive

    http_no_content

  3. Availability monitor · Recorded state

    Desconhecido→inactive

    http_no_content

  4. Availability monitor · Recorded state

    Desconhecido→inactive

    http_no_content

  5. Availability monitor · Recorded state

    Desconhecido→inactive

    http_no_content

Earlier observations 7
  1. Availability monitor · Recorded state

    Desconhecido→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Desconhecido→inactive

    hosting_placeholder · placeholder_page

  3. Availability monitor · Recorded state

    Desconhecido→inactive

    hosting_placeholder · placeholder_page

  4. Availability monitor · Recorded state

    Desconhecido→inactive

    hosting_placeholder · placeholder_page

  5. VirusTotal · Detection count

    6→8

  6. Availability monitor · Recorded state

    Acessível→Indisponível

  7. Availability monitor · First collection record

    Acessível

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    8/89 engine detections

    View source
  3. Added to PhishDestroy

    jaweriakhan6906.github.io

    View source
  4. URLScan

    Page captured

    View source

Domínios semelhantes

151 domínios semelhantes armazenados

Mostrar tudo (88)
eldger.com transposition kedger.com replacement kledger.com insertion l3dger.com replacement ldeger.com transposition ldger.com omission le.dger.com subdomain lecger.com replacement ledber.com replacement ledegr.com transposition leder.com omission ledg3r.com replacement ledge.com omission ledged.com replacement ledgedr.com insertion ledgee.com replacement ledgeer.com repetition ledgercom.com various ledget.com replacement ledgewr.com insertion ledgger.com repetition ledgir.com vowel-swap ledgor.com vowel-swap ledgr.com omission ledgre.com transposition ledgrer.com insertion ledgsr.com replacement ledgwer.com insertion ledgwr.com replacement ledher.com replacement ledhger.com insertion ledsger.com insertion ledtger.com insertion ledyer.com replacement ledzer.com replacement leedger.com insertion legder.com transposition leger.com omission lerdger.com insertion lerger.com replacement lesger.com replacement lewdger.com insertion lidger.com vowel-swap lledger.com repetition lodger.com vowel-swap lrdger.com replacement lsdger.com replacement oedger.com replacement pedger.com replacement pledger.com insertion dedger.com bitsquatting hedger.com bitsquatting iedger.com homoglyph l-edger.com hyphenation ladger.com bitsquatting lcdlger.com homoglyph lddger.com bitsquatting lebger.com homoglyph leclger.com homoglyph ledcer.com bitsquatting leddger.com insertion ledeer.com bitsquatting ledeger.com insertion ledfer.com bitsquatting ledg-er.com hyphenation ledgar.com bitsquatting ledger0.com addition ledger1.com addition ledger4.com addition ledger5.com addition ledger6.com addition ledgerb.com addition ledgerc.com addition ledgerf.com addition ledgeri.com addition ledgern.com addition ledgerq.com addition ledgerx.com addition ledges.com bitsquatting ledgez.com bitsquatting ledgur.com bitsquatting lediger.com homoglyph ledqer.com homoglyph leeger.com bitsquatting leelger.com homoglyph lefger.com bitsquatting letger.com bitsquatting ludger.com bitsquatting

Exibindo 100 de 151

Evidências e relatórios externos

Análise aprofundada
Help & reporting

Você foi afetado por este site?

3 evidence signal groups linked 0 stored notification records Conteúdo indisponível

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

Se você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.

Official reporting routes

Cuidado com os golpistas que prometem recuperação! Os criminosos podem entrar em contato novamente com as vítimas fingindo ser investigadores, advogados ou agentes de recuperação. Não pague taxas antecipadas nem compartilhe credenciais. Saiba mais sobre fraudes relacionadas à recuperação →

Notifique as autoridades locais

Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.

Diretório de 97 países

Template-based draft · optional AI wording assistance requires separate consent

Rascunho assistido por IA – os detalhes do incidente são processados pelo provedor de IA · Revise e envie você mesmo
After a phishing incident

Recomendações e orientações para as vítimas

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

O que devo fazer agora mesmo?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Alterar todas as senhas — e-mail, contas do Exchange, qualquer coisa que use a mesma senha
  • Ativar a autenticação de dois fatores usando um aplicativo autenticador (não por SMS). Desative a recuperação por SMS
  • Cartões de congelamento se você inseriu dados bancários no site de phishing

Que informações devo coletar para o meu relatório?

Diretrizes do FBI

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Datas e horários exatos — de cada transação e do primeiro contato com o golpista
  • Capturas de tela — sites fraudulentos, mensagens de bate-papo, e-mails, transações em carteiras digitais, redes sociais
  • Todas as URLs e domínios utilizado pelo golpista (incluindo jaweriakhan6906.github.io)
  • Comunicações — e-mails, mensagens de texto, números de telefone e nomes de usuário que o golpista utilizou

Mesmo que você não tenha todos os detalhes — registre uma ocorrência mesmo assim. Mesmo informações parciais ainda ajudam nas investigações.

A quem devo denunciar o golpe?

  • FBI IC3 — Centro de Denúncias de Crimes na Internet (sistema federal de denúncias dos EUA)
  • Europol — Relatórios sobre crimes cibernéticos na Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polícia local — cria um registro oficial, mesmo que não possam agir imediatamente

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Sites falsos — clones idênticos, até o último pixel, de sites legítimos, com domínios ligeiramente alterados
  • Abate de suínos — confiança construída ao longo de semanas pelo Telegram, WhatsApp e aplicativos de namoro; em seguida, o dinheiro foi roubado
  • Golpes relacionados à recuperação — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Golpes baseados em IA — deepfakes, phishing automatizado e sites gerados por IA, o que torna a fraude mais difícil de detectar

Como posso me proteger no futuro?

  • Adicione os sites oficiais aos favoritos — nunca clique em links de e-mails, mensagens diretas ou anúncios
  • Verificar domínios — verificar PhishDestroy antes de interagir. Verifique se o site usa HTTPS, a ortografia e a idade do domínio
  • "Bom demais para ser verdade" = golpe — retornos garantidos, endossos de celebridades, prazos urgentes

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Mantenha-se informado, mantenha-se seguro

Monitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo

Feed de ameaças em tempo real Recorrer deste anúncio
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Incorporar este relatório

Compartilhe essas informações sobre ameaças em seu site ou blog

embed.html
<iframe
  src="https://phishdestroy.io/pt-br/embed/domain/jaweriakhan6906.github.io"
  title="PhishDestroy threat report for jaweriakhan6906.github.io"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>