VirusTotal
9 / 89 engine detections
보고서 열기“spotify - web player:music everyone”
shaktikumar72.github.io — 콘텐츠를 사용할 수 없음 (HTTP 404). 브랜드 사칭: Spotify; 사기 유형: Impersonation. 증거 요약: VirusTotal 9/89 (alphaMountain.ai, ESET, Emsisoft, Forcepoint ThreatSeeker, G-Data); URLScan malicious verdict; PhishDestroy score 80/100. 등록기관: MarkMonitor.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
9 / 89 engine detections
보고서 열기악성
보고서 열기no community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
AI-assisted evidence review
shaktikumar72.github.io was an impersonation phishing page dressed up as Spotify's browser player, carrying the title "spotify - web player:music everyone". It targeted Spotify listeners who might follow a link expecting to sign in and play music. PhishDestroy first flagged it on 2026-09-11, and the site went offline the same day. As of 2026-10-19 the address no longer serves any content.
Pages like this copy the look and wording of Spotify's web player so a visitor assumes they are on the real service and need to log in. Whatever goes into the fake sign-in form, usually an email and password, is sent to the operator instead of Spotify. A stolen Spotify login can be used to take over the account, change its email, or be tested against other services where the victim reused the same password. Some clones also push a fake billing or subscription step to collect card details.
On 2026-09-11, VirusTotal showed 9 of 89 security engines flagging the page as malicious, including ESET, Sophos, Netcraft, Forcepoint ThreatSeeker, G-Data, Emsisoft, Gridinsoft and alphaMountain.ai. That count is modest, but it comes from several unrelated vendors that reached the same conclusion independently. urlscan.io also returned a malicious verdict and identified Spotify as the brand being imitated, which matches PhishDestroy's own classification and blocklist entry.
The page was published as a user subdomain on GitHub Pages. The 2013-03-08 registration date and the MarkMonitor, Inc. registrar belong to the shared github.io parent domain, not to this operator, so they say nothing about how long this particular page existed. Traffic was served from Fastly, Inc. infrastructure in the US, which is the standard delivery network for GitHub Pages. Free hosting of this kind lets a phishing page go live with no domain purchase and be replaced quickly once it is reported.
If you entered your Spotify login on this page, change your Spotify password right away and use the option to sign out of all devices. Then review the account's email address, linked devices and payment details for changes you did not make. Change the password anywhere else you used the same one, and turn on two-step verification where it is offered. If you entered card details, contact your bank and watch for unfamiliar charges. Defenders should block the subdomain, search mail and proxy logs for visits since 2026-09-11, and report any new Spotify clones on github.io to GitHub for removal.
urlscan.io scan and screenshot: https://urlscan.io/result/01a08b06-a31d-75ff-8497-996eb9506f41/
VirusTotal report: https://www.virustotal.com/gui/domain/shaktikumar72.github.io
Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=shaktikumar72.github.io
Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/
Site owner? Request a review: https://phishdestroy.io/appeals/
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
Location describes the IP network.
Saved 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 shaktikumar72.github.io · checked Sep 11, 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.
http_other: raw=http_404; http=404; via=http_proxy; server=GitHub.com
shaktikumar72.github.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→inactive
http_no_content
알 수 없음→inactive
http_no_content
알 수 없음→inactive
http_no_content
알 수 없음→inactive
http_no_content
알 수 없음→inactive
http_no_content
알 수 없음→inactive
hosting_placeholder · placeholder_page
알 수 없음→inactive
hosting_placeholder · placeholder_page
알 수 없음→inactive
hosting_placeholder · placeholder_page
접속 가능→이용 불가
No threat flag
View source9/89 engine detections
View sourceshaktikumar72.github.io
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
shaktikumar72.github.io)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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
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.