VirusTotal
6 / 89 engine detections
打开报告“cbsupport.help”
冒充 MetaMask: cbsupport.help — 最后已知的活跃状态 (HTTP 308). 证据摘要: VirusTotal 6/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); Spamhaus…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 89 engine detections
打开报告DBL_PHISH
3 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
cbsupport.help is an impersonation phishing site built to look like an official customer-support channel for crypto users. The name pairs a short brand-style prefix with "support" on a .help domain, which is the pattern of fake help desks that catch people searching for assistance. PhishDestroy first flagged it on 2026-08-31. As of 2026-10-19 the domain is still alive and redirects visitors onward.
Fake support sites wait for users who already have a problem, such as a stuck transaction, a locked account or a missing deposit. The victim is pulled into a chat or form and asked to verify their identity by handing over login credentials, one-time 2FA codes, a wallet recovery phrase, or a wallet connection. Anyone who gives up a seed phrase or signs what they are told is a fix loses control of their funds, and stolen exchange logins let the operators drain accounts directly. The page title shows only the bare domain name, so no brand is visible on the tab, and visitors are passed along through the redirect.
Six of 89 VirusTotal engines flagged the domain as of 2026-09-10: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That count is modest, but other sources back it up. MetaMask's and SEAL's crypto-focused blocklists list the domain alongside PhishDestroy, and Spamhaus carries it in its DBL under the phishing category. It also appears in three AlienVault OTX threat pulses, so other researchers have tracked it independently.
The domain was registered through Name.com, Inc. on 2026-08-29, and PhishDestroy detected it just two days later. A gap that short suggests it was registered to be used in a campaign right away. The site resolves to the Amazon.com, Inc. network in the US and uses a free Let's Encrypt certificate, so the padlock in the browser says nothing about whether the site is legitimate.
Real support teams never ask for your recovery phrase, password or 2FA codes. If you typed any of these here, change the password and reset 2FA from the official app right away. If you revealed a seed phrase, move your funds to a newly created wallet, because the old one cannot be made safe again. If you connected a wallet or signed anything, revoke the approvals with a reputable approval checker. Defenders should block the domain at DNS and proxy level, match it against the Spamhaus DBL, and warn users that support is only reached from inside official apps.
Last checked
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.
Edge-IP 声誉不属于此域。
ns2.vercel-dns.comLocation describes the IP network.
c3885b8114b4a14a65136bff22743a90565468a37ac23cfacd7064be2d52dde2Saved 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 cbsupport.help · checked Sep 10, 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.
cbsupport.help
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
可访问→不可用
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
不可用→可访问
可访问→不可用
未知→protected
http_access_restricted · access_restriction
未知→redirected
http_redirect
protected→redirected
http_redirect
未知→protected
http_access_restricted · access_restriction
redirected→protected
http_access_restricted · access_restriction
未知→redirected
http_redirect
redirected→protected
http_access_restricted · access_restriction
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→inactive
http_no_content
未知→inactive
http_no_content
未知→inactive
http_no_content
不可用→可访问
可访问→不可用
可访问
3 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcecbsupport.help
View source已存储 79 个仿冒域名
Listed 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 ↗
cbsupport.help)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.