Ir al informe de seguridad
Seguridad de dominio e inteligencia sobre amenazas
mohammadhaneef110.github.io favicon

mohammadhaneef110.github.io

“Site not found · GitHub Pages”

Registrador
GitHub
Resolved IP
185.199.108.153
PhishDestroy assessment Crítico
Disponibilidad Contenido no disponible El contenido no estaba disponible en la última observación. Observado · HTTP probe
VirusTotal detecciones: 7/90 Etiqueta automática de marca: Ledger
04/09/2026 CDN
API
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 7. Tenga extrema precaución: no ingrese credenciales o información personal.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Resumen del informe

Suplantación de Ledger: mohammadhaneef110.github.io — Contenido no disponible (HTTP 404). Resumen de las pruebas: VirusTotal 7/90 (alphaMountain.ai, CyRadar…

El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.

Source evidenceVirusTotal 7 / 90 5 sources

VirusTotal

7 / 90 engine detections

Abrir informe

Google Safe Browsing

No threat flag

Abrir informe

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

Analysis

Crítico
VirusTotal
7 / 90
Page captures
2

PhishDestroy threat report

Overview

mohammadhaneef110.github.io is a GitHub Pages project site that PhishDestroy classifies as impersonation phishing. It posed as a legitimate service to win the trust of visitors. We first flagged it on 2026-09-04, and it went offline the next day, 2026-09-05. It was still dead when we last checked on 2026-10-19. The root of the site now returns GitHub's "Site not found · GitHub Pages" title, which shows the project has been removed or unpublished. That title does not reflect the impersonation content we classified.

How the scam works

Impersonation pages copy the look, wording and logos of a brand people already trust, such as a wallet, an exchange or a support portal. Visitors are usually sent there through links in messages, social posts or search ads. The page then asks for something valuable: login credentials, one-time codes, personal details or a wallet recovery phrase. Whatever the victim types goes straight to the operator, who uses it to take over accounts or empty funds. Hosting on a github.io subdomain lends a borrowed sense of legitimacy and costs the operator nothing to set up or abandon.

Evidence

When VirusTotal scanned the site on 2026-09-05, 7 of 90 engines flagged it as malicious. The vendors were alphaMountain.ai, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Sophos. That is a modest count, but these are several independent vendors with their own detection pipelines, and they agreed within a day of our first sighting. Among the blocklists we track, the domain appears only on PhishDestroy's.

Infrastructure

The site sat on GitHub's shared Pages hosting at 185.199.108.153 in the United States. The parent domain is registered through GitHub, Inc., so the operator never had to buy a domain at all. Its certificate came from Let's Encrypt, which GitHub Pages issues automatically and which says nothing about who ran the page. A free throwaway account and a lifespan of about a day point to a disposable operation that can easily reappear under a new username.

What to do

If you entered a password on this page, change it right away on the real service and on any other site where you reused it. Then turn on app-based or hardware two-factor authentication. If you typed a wallet recovery phrase or private key, treat that wallet as compromised and move any remaining assets to a newly created wallet. Watch your accounts for unfamiliar logins or password-reset emails. Defenders should block the domain, hunt for other github.io pages that use the same branding, and report fresh copies to GitHub so they can be taken down quickly.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Captura guardada · 2 captures

Domain details

Dominio
URLScan verdict Análisis finalizado score 0 report ↗
IP Context GitHub Pages shared edge origin IP hidden La reputación de Edge-IP no se atribuye a este dominio.
Proveedor de plataforma GitHub US(US)
Contacto de abusoabuse@github.com
Estado HTTP404 Not Found
Tiempo hasta la primera indisponibilidad 10h
Qué contabilizamos Tiempo transcurrido desde el primer informe de abuso almacenado hasta la primera observación de que el contenido no estaba disponible. Esto no establece la causa.
Qué contiene cada informe Los registros de informes salientes almacenados pueden hacer referencia a evidencia disponible en ese momento, como veredictos de proveedores, datos de registro, detalles de alojamiento, clasificaciones o capturas de pantalla. Esta página no infiere la carga útil entregada, el recibo, el acuse de recibo o la acción exacta por parte de un destinatario.
Detalles técnicosProvenance & timestamps
Primera detección04/09/2026
Submitted URLhttp://mohammadhaneef110.github.io/ledger-todo
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 56 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
185.199.108.153
Observed location
US
Server header
GitHub.com

La reputación de Edge-IP no se atribuye a este dominio.

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-04 16:02:04 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.

Tecnologías · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este dominio Envía pruebas y ayuda a proteger a los demás

Análisis de VirusTotal

7 / Los proveedores de seguridad de 90 marcaron este dominio
View on VT
Last analyzed First positive detection Previous stored snapshot: 7 detections
alphaMountain.ai
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Sophos
Análisis del rendimiento del sitio

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

100
Good
Performance
FCP
0.87s
First Contentful Paint
LCP
0.87s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.91s
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.

mohammadhaneef110.github.io
Resultado guardado
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

    Desconocido→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Desconocido→inactive

    http_no_content

  3. Availability monitor · Recorded state

    Desconocido→inactive

    http_no_content

  4. Availability monitor · Recorded state

    Desconocido→inactive

    http_no_content

  5. Availability monitor · Recorded state

    Desconocido→inactive

    http_no_content

Earlier observations 7
  1. Availability monitor · Recorded state

    Desconocido→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Desconocido→inactive

    hosting_placeholder · placeholder_page

  3. Availability monitor · Recorded state

    Desconocido→inactive

    hosting_placeholder · placeholder_page

  4. Availability monitor · Recorded state

    Desconocido→inactive

    hosting_placeholder · placeholder_page

  5. Availability monitor · Recorded state

    Accesible→No disponible

  6. VirusTotal · Detection count

    6→7

  7. Availability monitor · First collection record

    Accesible

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    7/90 engine detections

    View source
  3. Added to PhishDestroy

    mohammadhaneef110.github.io

    View source
  4. URLScan

    Page captured

    View source

Dominios similares

151 dominios similares almacenados

Mostrar todo (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

Se muestran 100 de 151

Datos y informes externos

Análisis en profundidad
Help & reporting

¿Te ha afectado esta página web?

3 evidence signal groups linked 0 stored notification records Contenido no disponible

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.

Si ingresó credenciales de cuenta, información personal o de pago, o descargó un archivo de este dominio, tome medidas inmediatas. A continuación encontrará recursos que le ayudarán a informar el incidente y protegerse.

Official reporting routes

¡Cuidado con los estafadores que se hacen pasar por empresas de recuperación de datos! Los delincuentes pueden volver a contactar a las víctimas haciéndose pasar por investigadores, abogados o agentes de recuperación. No pague tarifas por adelantado ni comparta credenciales. Más información sobre el fraude en las ayudas de recuperación →

Informa a las autoridades locales

Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.

directorio de 97 países

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

Borrador asistido por IA: el proveedor de IA procesa los detalles del incidente · Revíselo y envíelo usted mismo
After a phishing incident

Recomendaciones y consejos para las víctimas

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

¿Qué debo hacer ahora mismo?

Urgente

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

  • Cambiar todas las contraseñas — correo electrónico, cuentas de Exchange, cualquier cosa que utilice la misma contraseña
  • Activar la autenticación de dos factores utilizando una aplicación de autenticación (no SMS). Desactivar la recuperación mediante SMS
  • Tarjetas de congelación si has introducido tus datos bancarios en la página de phishing

¿Qué información debo recopilar para mi informe?

Directrices del 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.
  • Fechas y horas exactas — de cada transacción y del primer contacto con el estafador
  • Capturas de pantalla — páginas web fraudulentas, mensajes de chat, correos electrónicos, transacciones con monederos electrónicos, redes sociales
  • Todas las URL y dominios utilizados por el estafador (incluidos mohammadhaneef110.github.io)
  • Comunicaciones — correos electrónicos, mensajes de texto, números de teléfono y nombres de usuario que utilizó el estafador

Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.

¿Dónde debo denunciar la estafa?

  • IC3 del FBI — Centro de Denuncias de Delitos en Internet (sistema federal de denuncia de EE. UU.)
  • Europol — Informes sobre la ciberdelincuencia en Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Policía local — deja constancia oficial, aunque no puedan actuar de inmediato

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?

  • Páginas web falsas — Clones idénticos al milímetro de sitios web legítimos, con dominios ligeramente modificados
  • Sacrificio de cerdos — Se ganaba la confianza de las víctimas a lo largo de varias semanas a través de Telegram, WhatsApp o aplicaciones de citas, y luego les robaban el dinero.
  • Estafas relacionadas con la recuperación — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Estafas basadas en la inteligencia artificial — los «deepfakes», el phishing automatizado y los sitios web generados por IA, que hacen que el fraude sea más difícil de detectar

¿Cómo puedo protegerme en el futuro?

  • Añadir a favoritos las páginas web oficiales — Nunca hagas clic en enlaces de correos electrónicos, mensajes directos o anuncios
  • Verificar dominios — comprobar si PhishDestroy antes de interactuar. Comprueba que sea HTTPS, la ortografía y la antigüedad del dominio
  • «Demasiado bueno para ser verdad» = estafa — rendimientos garantizados, recomendaciones de famosos, plazos urgentes

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

Mantente informado, mantente a salvo

Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.

Flujo de amenazas en tiempo real Reclamar este anuncio
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

Incrustar este informe

Comparte esta información sobre amenazas en tu página web o blog

embed.html
<iframe
  src="https://phishdestroy.io/es/embed/domain/mohammadhaneef110.github.io"
  title="PhishDestroy threat report for mohammadhaneef110.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>