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

vyankatesh9880.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: 12/89 Etiqueta automática de marca: Near
06/09/2026 CDN
API
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 12. 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 Near: vyankatesh9880.github.io — Contenido no disponible (HTTP 404). Resumen de las pruebas: VirusTotal 12/89 (alphaMountain.ai, CyRadar…

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

Source evidenceVirusTotal 12 / 89 5 sources

VirusTotal

12 / 89 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
12 / 89
Page captures
2

PhishDestroy threat report

Overview

vyankatesh9880.github.io was a phishing page hosted on a free GitHub Pages subdomain that impersonated Spotify to deceive the streaming service's users. PhishDestroy first flagged it on 2026-09-06. It went offline on 2026-09-11, and on 2026-10-19 it was still dead, returning no content at its root. The page title now reads "Site not found · GitHub Pages", which is GitHub's default error page, while our classification is based on the Spotify impersonation detected while the site was live.

How the scam works

Spotify phishing usually starts with an email, text or ad that claims a payment failed, an account is suspended or a free Premium offer is waiting. The link opens a copy of Spotify's login page. Anything typed there, such as email, password and often card details on a fake billing form, goes straight to the operators. Hosting on github.io lends the page a familiar, trustworthy-looking address, and the operator can delete a throwaway repository as soon as it has served its purpose. Stolen Spotify logins are resold or tested against other services where victims reused the same password.

Evidence

urlscan.io rated the page malicious and identified Spotify as the impersonated brand, which directly supports the classification. On 2026-09-11, 12 of 89 VirusTotal engines flagged it, including ESET, Emsisoft, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai, CyRadar, Gridinsoft and Lionic. That is a moderate detection rate, but it comes from a varied set of independent vendors. PhishDestroy lists the domain on its blocklist.

Infrastructure

The site was a user subdomain on GitHub Pages rather than a registered domain, so the operator paid nothing and needed no registration that could be traced. Traffic was served through Fastly's content delivery network in the US, the standard front end for all GitHub Pages sites. Its Let's Encrypt certificate is issued automatically to every Pages site, so the padlock said nothing about legitimacy. The site was online for only about five days after detection, which fits a short-lived campaign.

What to do

If you entered your Spotify login here, change your Spotify password right away. Then use Spotify's option to sign out everywhere and change the password on any other account that shared it. If you gave card details, contact your bank to block the card and dispute any unfamiliar charges. Turn on two-factor authentication on your email account, since that is how attackers reset other passwords. Defenders should block the hostname, search mail logs for links to it, and report similar github.io Spotify lures to GitHub for removal.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Captura guardada · 2 captures

Domain details

Dominio
URLScan verdict Malicioso score 100 Phishing brand: Spotify report ↗
IP Context Fastly 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 4 days
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ón06/09/2026
DOM Analysisanalyzed 06/09/2026score 73/1002 brand signals
Submitted URLhttp://vyankatesh9880.github.io/Spotify-Clone
Favicon Hash
Observed page title
Site not found · GitHub Pages
Automated brand references
Near Spotify
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.108.153
Network ASN
AS54113
Organization
GitHub, Inc
Observed location
San Francisco, 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-06 13:02:06 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

12 / Los proveedores de seguridad de 89 marcaron este dominio
View on VT
Last analyzed First positive detection Previous stored snapshot: 12 detections
alphaMountain.ai
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
G-Data
Gridinsoft
Lionic
Netcraft
PrecisionSec
Sophos
Webroot
Análisis del rendimiento del sitio

Google PageSpeed Insights — mobile performance audit of vyankatesh9880.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.

vyankatesh9880.github.io
Resultado guardado
Cloaked / Filtered
Stored observation history14

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 9
  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

    10→12

  7. VirusTotal · Detection count

    9→10

  8. VirusTotal · Detection count

    8→9

  9. Availability monitor · First collection record

    Accesible

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    12/89 engine detections

    View source
  3. Added to PhishDestroy

    vyankatesh9880.github.io

    View source
  4. URLScan

    Page captured

    View source

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 vyankatesh9880.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/vyankatesh9880.github.io"
  title="PhishDestroy threat report for vyankatesh9880.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>