rajveersolanki06.github.io is a Spotify impersonation page detected by PhishDestroy on 2026-09-14. Risk: critical (86/100). Registrar: GitHub Pages. Status: Content unavailable. Hosting: Fastly, Inc. VirusTotal: 12/89 engines flag it. PhishDestroy detected it 2 days before VirusTotal engines flagged it (in PhishDestroy’s checks). Do not enter credentials or connect a wallet.
rajveersolanki06.github.io was a phishing page that copied the Spotify Web Player, titled "Spotify - Web Player Music for everyone" to mirror the real service. It targeted Spotify users who could be tricked into signing in on a look-alike page. PhishDestroy first flagged it on 2026-09-14, and it went offline the next day, 2026-09-15. When we checked again on 2026-10-19, the site was still dead and its root served no content.
How the scam works
Fake web-player pages like this one copy Spotify's familiar branding so a visitor assumes they have been logged out and need to sign in again. The login form sends the email and password to the operator instead of Spotify. Stolen accounts are often resold or used to try the same password on other services. If the same email and password protect a mailbox or a crypto exchange, the damage goes well beyond music streaming.
Evidence
On 2026-09-16, 12 of 89 VirusTotal engines flagged the address. They included alphaMountain.ai, BitDefender, ESET, Emsisoft, Fortinet, G-Data, Gridinsoft and MalwareURL. That is a solid share for a short-lived free-hosted page. urlscan.io independently rated the page malicious and recognised Spotify branding on it, which matches our impersonation classification. PhishDestroy lists the domain on its blocklist.
Infrastructure
The page sat on a GitHub Pages subdomain. Free static hosting like this lets anyone publish a cloned login page in minutes without buying a domain. Traffic was served through Fastly's network in the US, the content delivery layer behind GitHub Pages. The page was gone about a day after we first saw it, a typical pattern for short-lived throwaway clones.
What to do
If you entered your Spotify login on this page, change your Spotify password right away and sign out of all devices from your account settings. Change the password anywhere else you used the same one, starting with your email, and turn on two-step verification where it is offered. Check your Spotify account for unfamiliar devices, playlists or changes to your plan or payment details. Defenders should block the hostname, search mail and proxy logs for visits since 2026-09-14, and reset credentials for any user who reached the page.
No. PhishDestroy classifies rajveersolanki06.github.io as a Spotify impersonation page (risk: critical, 86/100); it was first detected on 2026-09-14. VirusTotal: 12/89 engines flag it. PhishDestroy detected it 2 days before VirusTotal engines flagged it (in PhishDestroy’s checks). Treat the site as unsafe.
Is rajveersolanki06.github.io safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on rajveersolanki06.github.io. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used rajveersolanki06.github.io?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Edge-IP reputation is not attributed to this domain.
Nameservers 5
ns-692.awsdns-22.net
ns-1622.awsdns-10.co.uk
dns1.p05.nsone.net
dns2.p05.nsone.net
dns3.p05.nsone.net
Location describes the IP network.
TLS certificate
Issuer
YR1
Valid from
2026-08-02 23:38:02
Valid until
2026-10-31 23:38:01
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintf2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856Certificate names · 6 SANs
*.github.com
*.github.io
*.githubusercontent.com
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.
Fastly is a cloud computing services provider. Fastly's cloud platform provides a content delivery network, Internet security services, load balancing, and video & streaming services.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · rajveersolanki06.github.io
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
3 evidence signal groups linked0 stored notification recordsContent unavailable
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
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.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including rajveersolanki06.github.io)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
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?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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.
