VirusTotal
15 / 92 engine detections
レポートを開く“spotify-payment.click”
["spotify"]なりすまし: spotify-payment.click — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 15/92 (alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, ESET)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
15 / 92 engine detections
レポートを開く悪意あり
レポートを開くDBL_PHISH
4 community references
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
spotify-payment.click is an impersonation phishing page posing as Spotify. It targets subscribers who believe there is a problem with their plan or billing. PhishDestroy first detected it on 2026-10-07. When checked on 2026-10-19, the site was still online and serving live content.
The domain combines the Spotify name with the word "payment," a common lure for messages claiming a subscription renewal failed or a card was declined. Victims who follow the link land on a page imitating Spotify's look. There they are asked to sign in and re-enter billing details to keep their account active. Anything typed is sent to the operators, including the email, password and full card data with expiry and security code. That gives them both a hijacked account and a card they can charge or resell. The page title shows only the bare domain name, so the browser tab gives victims no branded cue.
On 2026-10-07, 15 of 92 VirusTotal engines flagged the domain as malicious. Vendors flagging it include alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet and Gridinsoft. Spamhaus lists it on its Domain Block List under the phishing category (DBL_PHISH), which many mail filters use to block links in incoming messages. The domain also appears in 4 AlienVault OTX threat pulses, and PhishDestroy carries it on its own blocklist.
The domain was registered on 2026-02-14 through Sav.com, LLC. That is almost eight months before PhishDestroy detected it, which suggests it was registered in advance and activated later. The site is hosted on Google Cloud infrastructure (AS396982, Google LLC) at IP 34.76.205.124 in Belgium.
If you entered your Spotify login on this site, change your Spotify password at once from the official app. Also change it anywhere else you reused it, and turn on two-factor authentication on your email account. If you submitted card details, call your bank to block the card and request a replacement. Then watch your statements for small test charges. Treat any payment-failure message as suspect and check your billing status only inside the Spotify app. Defenders should block spotify-payment.click at mail gateways and DNS resolvers. They should also search mail logs for messages linking to it and warn users about Spotify billing lures.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
ns2.all-harmless.domainsmx.all-harmless.domainspriority 10Location describes the IP network.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
admin.spotify-payment.clickDomain recordmail.spotify-payment.clickDomain recordwebmail.spotify-payment.clickDomain recordwww.spotify-payment.clickDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of spotify-payment.click · checked Oct 7, 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.
alive_content: raw=ok; http=200; via=https_proxy; server=Caddy
spotify-payment.click
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
No threat flag
View source4 community references
View source15/92 engine detections
View sourcespotify-payment.click
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 ↗
spotify-payment.click)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.