VirusTotal
12 / 89 engine detections
Raporu aç“Site not found · GitHub Pages”
Near taklidi: vyankatesh9880.github.io — İçerik kullanılamıyor (HTTP 404). Kanıt özeti: VirusTotal 12/89 (alphaMountain.ai, CyRadar, ESET, Emsisoft…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
12 / 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
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.
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.
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.
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.
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.
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 vyankatesh9880.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.
vyankatesh9880.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
Erişilebilir→Mevcut değil
10→12
9→10
8→9
Erişilebilir
No threat flag
View source12/89 engine detections
View sourcevyankatesh9880.github.io
View sourcePage captured
View sourceListed 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 ↗
vyankatesh9880.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.