VirusTotal
3 / 89 engine detections
打开报告被列入黑名单的域名: crypto-cs5.netlify.app — 内容不可用 (HTTP 404). 证据摘要: VirusTotal 3/89 (alphaMountain.ai, Forcepoint ThreatSeeker, VIPRE); 2 external blocklist matches…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
3 / 89 engine detections
打开报告no community references
打开报告provider verdict: clean
打开报告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
crypto-cs5.netlify.app is a phishing page that impersonates a crypto service. It sits on a free Netlify subdomain, and its generic "crypto" label is the kind of name that passes as an official support or access page. PhishDestroy first flagged it on 2026-09-08. The site went offline on 2026-09-11, and on 2026-10-19 it was still dead, with nothing served at the root.
Crypto impersonation pages copy the look of a wallet, exchange or project so that visitors treat them as the real thing. The page then asks for whatever unlocks the victim's funds. That can be a seed phrase or private key typed into a fake "restore" or "verify" form, exchange login credentials, or a wallet connection followed by a transaction or approval request. Anything entered goes straight to the operator, who can empty the wallet or account, usually within minutes and with no way to reverse it.
Three of 89 VirusTotal engines (alphaMountain.ai, Forcepoint ThreatSeeker and VIPRE) rated the URL malicious on 2026-09-16. That is a low count, typical for short-lived pages on shared hosting platforms. The more telling signal comes from crypto-focused blocklists: MetaMask and SEAL both list the page alongside PhishDestroy. This means wallet users running MetaMask's protections would have seen a warning.
The operator did not register a domain. They used a Netlify subdomain, which costs nothing, takes minutes to set up and inherits the platform's reputation. Traffic resolved to Amazon infrastructure in Germany, which is the shared hosting behind the platform rather than anything chosen by the scammer. The DigiCert certificate is Netlify's own, so the padlock in the browser said nothing about who ran the page. The site lasted only three days after detection, a pattern consistent with throwaway deployments that are rotated once flagged.
If you typed a seed phrase or private key into this page, treat that wallet as compromised. Create a new wallet on a trusted device and move any remaining assets to it immediately. If you connected a wallet and signed anything, review and revoke token approvals for that address, and watch it for unexpected transfers. If you entered exchange credentials, change the password, reset 2FA and check the account's withdrawal settings and API keys. Defenders should block netlify.app subdomains that impersonate crypto brands at the hostname level and report new instances to Netlify's abuse team.
Last checked
Edge-IP 声誉不属于此域。
Location describes the IP network.
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478netlify.appSaved 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 crypto-cs5.netlify.app · checked Sep 8, 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.
crypto-cs5.netlify.app
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
http_no_content
未知→inactive
http_no_content
未知→inactive
http_no_content
未知→inactive
http_no_content
2→3
可访问→不可用
0→2
可访问
No threat flag
View source3/89 engine detections
View sourcecrypto-cs5.netlify.app
View sourcePage captured
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 ↗
crypto-cs5.netlify.app)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.