VirusTotal
10 / 89 engine detections
보고서 열기“spotify-web player:music for everyone”
lokendraankel12-lgtm.github.io — 콘텐츠를 사용할 수 없음 (HTTP 404). 브랜드 사칭: Spotify; 사기 유형: Impersonation. 증거 요약: VirusTotal 10/89 (alphaMountain.ai, Emsisoft, Forcepoint ThreatSeeker, G-Data, Gridinsoft); URLScan malicious verdict; PhishDestroy score 80/100. 등록기관: MarkMonitor.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
10 / 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
lokendraankel12-lgtm.github.io is a phishing page that impersonates Spotify. It was hosted as a personal GitHub Pages site and titled "spotify-web player:music for everyone" to pass as the official browser player. Its targets are Spotify listeners and anyone who reuses their Spotify password elsewhere. PhishDestroy first flagged it on 2026-09-11, and it went offline the same day. On our last check, 2026-10-19, the site was still dead and its root served no content.
Fake Spotify web players copy the look of the real player and present a sign-in prompt before any music loads. Whatever the visitor types, usually an email and password and sometimes card details for a fake "premium renewal", goes to the operator rather than to Spotify. A hijacked Spotify account can be resold or used with any stored payment method. Because many people reuse passwords, the same credentials are often tried against email, exchange and wallet-related accounts.
urlscan.io rated the page malicious and recognised Spotify branding on it. On 2026-09-11, 10 of 89 VirusTotal engines flagged it, including Netcraft, Forcepoint ThreatSeeker, Emsisoft, G-Data, Gridinsoft, alphaMountain.ai, LevelBlue and PrecisionSec. That count is moderate, but the vendors include several independent phishing and URL-reputation feeds. PhishDestroy lists the domain on its blocklist.
The 2013-03-08 registration date, the MarkMonitor registrar and the Fastly network in the US all belong to GitHub's shared github.io platform. They say nothing about when this operator started. The only part the attacker controlled is the account-named subdomain, a throwaway pattern common on free static hosting. Such pages inherit the platform's valid HTTPS certificate and trusted reputation, which helps them slip past casual checks.
If you entered your Spotify login on this page, change your Spotify password right away. Sign out of all devices from your account settings and turn on any extra verification Spotify offers. Change the password on every other service where you used the same one, starting with your email account. If you entered card details, ask your bank to block the card and watch for unfamiliar charges. Defenders should block the hostname, report the repository to GitHub, and hunt mail and proxy logs for other github.io pages carrying Spotify branding.
urlscan.io scan and screenshot: https://urlscan.io/result/01a088d5-fde6-731f-b954-661742eede4b/
VirusTotal report: https://www.virustotal.com/gui/domain/lokendraankel12-lgtm.github.io
Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=lokendraankel12-lgtm.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 lokendraankel12-lgtm.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
lokendraankel12-lgtm.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 source10/89 engine detections
View sourcelokendraankel12-lgtm.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 ↗
lokendraankel12-lgtm.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.