跳转到安全报告
域安全和威胁情报
cbsupport.help favicon

cbsupport.help

“cbsupport.help”

注册商
Name.com
Resolved IP
216.150.1.129
Registered
2026年8月29日
PhishDestroy assessment 关键
可用性 最后已知的活跃状态 以前不可用;最新观察结果已可达 观察到 · HTTP probe
病毒检测总数:6/89 Spamhaus DBL: DBL_PHISH 存储的阻止列表匹配项:2 自动品牌标签:MetaMask
OTX: 3 refs 2026年8月31日 CDN
API
该域名已被标记为恶意域名
安全引擎报告检测:6。 报告匹配的公共黑名单:2。 请格外小心——不要输入凭据或个人信息。
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
报告概览

冒充 MetaMask: cbsupport.help — 最后已知的活跃状态 (HTTP 308). 证据摘要: VirusTotal 6/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); Spamhaus…

为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。

Source evidenceVirusTotal 6 / 89 · OTX 3 references 6 sources

VirusTotal

6 / 89 engine detections

打开报告

Spamhaus DBL

DBL_PHISH

Google Safe Browsing

No threat flag

打开报告

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

关键
VirusTotal
6 / 89
OTX
3 community refs
Page captures
1

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask 已列入 View source
PhishDestroy PhishDestroy list View source
SEAL 已列入 View source

Last checked

已保存的截图 · 1 capture

Observed page title
cbsupport.help
TLS 证书
颁发者 Let's Encrypt / YR2 · stored validity ends in 38 days

Domain details

域名
URLScan verdict 分析完成 score 0 report ↗
IP Context Vercel shared edge origin IP hidden Edge-IP 声誉不属于此域。
OTX tags 2026-08activeall-domainsblocklistcontentcrypto域名drainerfraudmonthlyphishdestroyphishingscam
注册商 Name.com US(US)
滥用举报联系方式["abuse@name.com"]
ICANN 注册管理机构ICANN Lookup (RDAP) →
注册信息创建 2026年8月29日 (51d · New) — Expires 2027年8月29日
HTTP 状态码308 Permanent Redirect
Elapsed Since First Report 50 days
统计口径 Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 最后已知的活跃状态.
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据,例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情Provenance & timestamps
首次发现2026年8月31日
DOM Analysisanalyzed 2026年10月9日score 95/100
Favicon Hash
ICANN OVERSIGHT

认证和 RAA 背景

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accountability draft 不会自动发送任何内容。

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
216.150.1.129
Network ASN
AS16509
Organization
Vercel, Inc
Observed location
Walnut, US
Server header
Vercel

Edge-IP 声誉不属于此域。

域名服务器 1

  • ns2.vercel-dns.com

Location describes the IP network.

TLS 证书

Issuer
Let's Encrypt / YR2
Valid from
2026-08-30 06:24:14
Valid until
2026-11-28 06:24:13
Validity
Within stored validity dates
Collection time
2026-10-11 01:03:02 UTC
Collection source
PhishDestroy collector
Certificate fingerprintc3885b8114b4a14a65136bff22743a90565468a37ac23cfacd7064be2d52dde2

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 22:34:38 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-19 22:34:38 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-10-19 22:34:38 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
技术 · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

6 / 89 安全供应商标记了该域
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
网站性能分析

Google PageSpeed Insights — mobile performance audit of cbsupport.help · checked Sep 10, 2026

100
Good
Performance
FCP
0.81s
First Contentful Paint
LCP
0.81s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.81s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

cbsupport.help
已保存的结果
Cloaked / Filtered
Stored observation history23

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    可访问→不可用

  2. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  3. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  4. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  5. Availability monitor · Recorded state

    未知→redirected

    http_redirect

Earlier observations 18
  1. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  2. Availability monitor · Recorded state

    不可用→可访问

  3. Availability monitor · Recorded state

    可访问→不可用

  4. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · access_restriction

  5. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  6. Availability monitor · Recorded state

    protected→redirected

    http_redirect

  7. Availability monitor · Recorded state

    未知→protected

    http_access_restricted · access_restriction

  8. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  9. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  10. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  11. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  12. Availability monitor · Recorded state

    未知→redirected

    http_redirect

  13. Availability monitor · Recorded state

    未知→inactive

    http_no_content

  14. Availability monitor · Recorded state

    未知→inactive

    http_no_content

  15. Availability monitor · Recorded state

    未知→inactive

    http_no_content

  16. Availability monitor · Recorded state

    不可用→可访问

  17. Availability monitor · Recorded state

    可访问→不可用

  18. Availability monitor · First collection record

    可访问

Recorded activity

4 entries
  1. AlienVault OTX

    3 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    6/89 engine detections

    View source
  4. Added to PhishDestroy

    cbsupport.help

    View source

仿冒域名

已存储 79 个仿冒域名

显示全部(67)
metasmask.io insertion 内部报告 metramask.io insertion 内部报告 mewtamask.io insertion 内部报告 mmetamask.io homoglyph 内部报告 mtamask.io omission 内部报告 mwetamask.io insertion 内部报告 nmetamask.io homoglyph 内部报告 metamark.io bitsquatting 内部报告 metamaskj.io addition 内部报告 metammask.io homoglyph 内部报告 metamnask.io homoglyph 内部报告 emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

证据与外部报告

深度分析
Help & reporting

您是否受到本网站的影响?

4 evidence signal groups linked 0 stored notification records 最后已知的活跃状态

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.

如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。

Official reporting routes

警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录

Template-based draft · optional AI wording assistance requires separate consent

AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident

针对受害者的建议与指导

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.

  • 更改所有密码 — 电子邮件、Exchange 账户,以及任何使用同一密码的账户
  • 启用双因素认证 使用身份验证器应用(而非短信)。禁用基于短信的恢复功能
  • 冻结卡片 如果您在钓鱼网站上输入了银行信息

我应该为报告收集哪些信息?

联邦调查局(FBI)指南

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.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的(包括 cbsupport.help)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。

我应该向哪里举报这起诈骗?

  • 联邦调查局(FBI)IC3 — 互联网犯罪投诉中心(美国联邦举报渠道)
  • 欧洲刑警组织 — 欧洲网络犯罪报告(欧盟)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 当地警方 — 即使无法立即采取行动,也能留下正式记录

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?

  • 虚假网站 — 与正规网站完全一致的克隆网站,仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任,随后钱被骗走
  • 退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站,使得欺诈行为更难被察觉

将来我该如何保护自己?

  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 验证域名 — 查看 PhishDestroy 在进行互动之前,请检查HTTPS、拼写和域名注册时间。
  • “好得令人难以置信”=骗局 — 保证收益、名人代言、紧迫的截止日期

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

随时掌握最新信息,确保安全

请实时监控威胁,或者如果您认为这是误报,请对该条目提出异议

实时威胁动态 对该列表提出异议
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html
<iframe
  src="https://phishdestroy.io/zh/embed/domain/cbsupport.help"
  title="PhishDestroy threat report for cbsupport.help"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>