跳转到安全报告
域安全和威胁情报
gmeet.com.br 的网站图标

gmeet.com.br

简要

gmeet.com.br:冒充 MetaMask,PhishDestroy 于 2026-10-11 检测到。风险:关键(100/100)。注册商:HSTDOMAINS。状态:最后已知的活跃状态。托管:Cloudflare, Inc。VirusTotal:7/92 个引擎标记。已列入 Spamhaus DBL。请勿输入登录凭据,也不要连接钱包。

“Meet — Webinar”

注册商
HSTDOMAINS
Resolved IP
188.114.97.1
Registered
2026年10月2日
PhishDestroy assessment 关键
可用性 最后已知的活跃状态 最新存储的可达性观察 观察到 · HTTP probe
病毒检测总数:7/92 Spamhaus DBL: DBL_PHISH 存储的阻止列表匹配项:2 自动品牌标签:MetaMask 年轻域名:19 天龄
OTX: 4 refs 2026年10月11日 CDN
API
该域名已被标记为恶意域名
安全引擎报告检测:7。 报告匹配的公共黑名单:2。 请格外小心——不要输入凭据或个人信息。
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
页面快照
打开图库
域名年龄
报告概览

冒充 MetaMask: gmeet.com.br — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 7/92 (alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, Fortinet, G-Data); Spamhaus…

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

来源证据VirusTotal 7 / 92 · OTX 4 references 6 sources

VirusTotal

7 / 92 engine detections

打开报告

Spamhaus DBL

DBL_PHISH

Google Safe Browsing

无威胁标记

打开报告

结果反映各来源的采集时间。零检出不代表安全。OTX 引用为社区发布的内容。

Analysis

关键
VirusTotal
7 / 92
OTX
4 community refs
页面快照
6

PhishDestroy threat report

Overview

gmeet.com.br is an impersonation phishing page that borrows Google Meet's name and presents itself as a webinar, with the page title "Meet — Webinar". It targets people who receive a meeting or webinar invitation and expect a routine join screen. The MetaMask and SEAL blocklists also flag it, which points toward crypto users as a likely audience. PhishDestroy first saw it on 2026-10-11, and it was still online with live content on 2026-10-19.

How the scam works

Fake meeting sites usually start with an invitation to a webinar, interview or community call that links to a page styled like a familiar join screen. Instead of a real call, the visitor is asked to sign in, "verify" an account, or install a client or plugin that is supposedly needed to join. Victims who comply hand over login credentials or run software they never meant to install. On a machine that holds a crypto wallet, that can lead to stolen sessions, passwords and funds.

Evidence

On 2026-10-12, 7 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. That count is modest, so many security tools may still let it load without a warning. The stronger signals come from elsewhere. Spamhaus lists it in its DBL as phishing, it appears on the MetaMask and SEAL blocklists alongside PhishDestroy, and four AlienVault OTX threat pulses reference it.

Infrastructure

The domain was registered on 2026-10-02 through HSTDOMAINS, nine days before PhishDestroy caught it. That short gap fits a site built for a specific campaign. It sits behind Cloudflare, with the edge address located in Canada, which hides the real origin server. Its Let's Encrypt certificate gives it a browser padlock, and the padlock says nothing about whether the site is safe.

What to do

If you opened an invitation that led here, do not install anything the page offers. If you already ran a downloaded file, disconnect the device, scan it, and consider reinstalling the system before using it for anything sensitive. If you typed a password, change it everywhere you reuse it, turn on app-based two-factor authentication, and sign out other sessions. If a wallet seed phrase was entered or the infected machine held a wallet, move funds to a new wallet created on a clean device. Defenders should block gmeet.com.br at DNS and mail gateways, search logs for visits, and warn staff about meeting links that lead to non-Google domains.

已采集的来源详情

已存档的页面、网络和扫描器观测结果,按来源和观测时间分组。

URLScan · 2026-10-04T09:15:11Z

观察到: · Retrieved:

Uuid
01a10632-0f46-7083-9fdc-917411f5ede3
Final url
https://gmeet.com.br/
状态
200
Ip
164.68.104.142
Ptr
vmi3310138.contaboserver.net
Contacted IP addresses
[
    "164.68.104.142"
]
Asns
[
    "51167"
]
Countries
[
    "FR"
]
Document hash
300578690edecb14a756a2a60f48c192a8a4ed2b29699b7e1419685cdf7f765f
Script hashes
[
    "6d9e8535934382a3801e72e5444381456ad157f530e25de12f6a2feb2381515c",
    "c8afee969d2bc5e5cef978aa9adcc4105710c4c9076b82033ed288d128b77d84",
    "b9cc61ebca4cf93479374798b846c0061b8a6f8826ed96b3c51d253902ec7bcd"
]
Tls
{
    "san": [
        "gmeet.com.br"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "gmeet.com.br",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-01T20:36:51Z",
    "valid_from": "2026-10-03T20:36:52Z"
}
域名年龄(天)
1
Apex age days
1
Tls age days
0
TLS 有效天数
89
Requests
11
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 93,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Caddy",
    "content-type": "text/html; charset=utf-8",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin"
}
Cloudflare Radar · 2026-10-12T09:16:58Z

观察到: · Retrieved:

Uuid
b960dc13-028d-478a-804f-f234834a429c
Final url
https://gmeet.com.br/
状态
200
History
[
    {
        "url": "https://gmeet.com.br/",
        "status": 200
    }
]
DOM structure hash
5fe85b5a6f89f695f8ce2fc231b43c710be9f60769aae9e01bdb2f3598b38e5f
Document hash
fbfa5bc894a575cf9c1157ba66465a3c72751c6aaae9d41929609e4634773c53
域名风险
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS 记录
[
    {
        "name": "gmeet.com.br",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "gmeet.com.br",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "gmeet.com.br",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    },
    {
        "name": "gmeet.com.br",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    }
]
DNSSEC 有效
false
Ip
188.114.97.0
注册记录
{
    "created": "2026-10-02T00:00:00Z",
    "updated": "2026-10-05T00:00:00Z",
    "expires": "2027-10-02T00:00:00Z",
    "nameservers": [
        "serena.ns.cloudflare.com",
        "stan.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-14T06:26:22Z

观察到: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 52,
    "malicious": 3,
    "suspicious": 1,
    "undetected": 36
}
Vendor labels
{
    "Fortinet": "spam",
    "Kaspersky": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Expires
2027-10-02T00:00:00Z
首次发现
2026-10-02T21:25:14Z
DNS 记录
[
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.173.99"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3033::ac43:ad63"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "serena.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::6815:3ff8"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "serena.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.63.248"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "stan.ns.cloudflare.com"
    }
]
Dns at
2026-10-14T06:31:28Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.gmeet.com.br",
        "gmeet.com.br"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "5b37fc8b741813434ba5b391d77bd22b0e6",
    "sha256": "77776575fca02056a206032a8558a0ad261a9e7578194cee3d128b3a95594598",
    "subject": "gmeet.com.br",
    "valid_to": "2027-01-03T13:33:04Z",
    "valid_from": "2026-10-05T13:33:05Z"
}

关于 gmeet.com.br 的问题

gmeet.com.br 是正规网站吗?

不是。PhishDestroy 将 gmeet.com.br 归类为“冒充 MetaMask”(风险:关键,100/100),首次检测于 2026-10-11。VirusTotal:7/92 个引擎标记。已列入 Spamhaus DBL。请将该网站视为不安全。

在 gmeet.com.br 连接钱包安全吗?

不安全。请勿在 gmeet.com.br 连接钱包、签署消息或批准代币。钓鱼网站会请求授权(approve、setApprovalForAll、Permit2),让运营者转走你的资产,而已确认的交易无法撤销。

如果我使用过 gmeet.com.br,该怎么办?

更改你在该网站输入过的所有密码,并开启双重验证。如果你连接过钱包或签署过任何内容,请撤销授权,并将剩余资金转到新钱包;切勿透露助记词。分步指南:紧急处理指南。

延伸阅读

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask 已列入 查看来源
PhishDestroy PhishDestroy list 查看来源
SEAL 已列入 查看来源

最近检查

已保存的截图 · 6 张截图

域名详情

域名
URLScan verdict 分析完成 score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
OTX tags 2026-10activeall-domainsblocklistcontentcrypto域名drainerfraudlivemonthlyphishdestroyphishingscam
注册商 HSTDOMAINS
ICANN 注册管理机构ICANN Lookup (RDAP) →
注册信息创建 2026年10月2日 (19d · Very New!) — Expires 2027年10月2日
HTTP 状态码200
技术详情Provenance & timestamps
首次发现2026年10月11日
DOM Analysisanalyzed 2026年10月12日score 100/100
Submitted URLhttp://gmeet.com.br/
Favicon Hash
Observed page title
Meet — Webinar
TLS 证书
颁发者 Let's Encrypt / YE1 · 存储的有效期将在 72 天后结束

网络 & 证书

已存档技术证据

网络 & DNS

Shared CDN edge
Resolved IP
188.114.97.1
网络 ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP 声誉不属于此域。

域名服务器 1

  • stan.ns.cloudflare.com

位置信息描述的是 IP 网络。

TLS 证书

Issuer
Let's Encrypt / YE1
生效时间
2026-10-05 13:33:05
到期时间
2027-01-03 13:33:04
Hostname coverage
已存档证书日期有效
Validity
在存档的有效期内
Collection time
2026-10-12 10:02:06 UTC
采集来源
PhishDestroy collector
证书指纹77776575fca02056a206032a8558a0ad261a9e7578194cee3d128b3a95594598
证书名称 · 2 个 SAN
  • *.gmeet.com.br
  • gmeet.com.br

已保存的证书元数据。未带时区的证书日期按存档原样显示。传输加密并不能证明该网站值得信任。

Latest Classified Outcome 2026-10-22 10:28:49 UTC

Primary outcome 内容在线 reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation 内容在线 Ordinary HTTP content served 90% 2026-10-22 10:28:49 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-10-22 10:28:49 UTC last content: 2026-10-22 10:28:49 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.gmeet.com.brDomain record

The original observation time is not recorded for these hostnames.

技术 · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

7 / 92 安全供应商标记了该域
在 VT 上查看
最近分析时间 First positive detection 上一份存档快照: 7 detections
alphaMountain.ai
BitDefender
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基

存档证据

Wayback Machine Snapshot
历史快照可供证据审查
查看存档
网站性能分析

Google PageSpeed Insights — 移动端性能审核: gmeet.com.br · checked Oct 12, 2026

96
Good
Performance
FCP
1.81s
首次内容绘制
LCP
2.11s
Largest Contentful Paint
CLS
0.025
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.75s
Speed Index
数据来源: Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

最近一次可访问观测
最近一次内容观测
Estimate basis
Currently reachable

估算时间描述的是一个观测时间窗口。它并不能证明注册商采取了措施,也不代表网站变为不可访问的确切时刻。

已存档的观测历史9

由监测程序和来源采集器保留的带日期变更记录。最新观测排在最前;来源状态并不能证明站点已被下架。

  1. 可用性监测 · 记录状态

    未知→live_content

    content_served

  2. 可用性监测 · 记录状态

    未知→live_content

    content_served

  3. 可用性监测 · 记录状态

    未知→live_content

    content_served

  4. 可用性监测 · 记录状态

    未知→live_content

    content_served

  5. 可用性监测 · 记录状态

    未知→live_content

    content_served

Earlier observations 4
  1. 可用性监测 · 记录状态

    未知→live_content

    content_served

  2. 可用性监测 · 记录状态

    未知→live_content

    content_served

  3. 可用性监测 · 记录状态

    未知→live_content

    content_served

  4. 可用性监测 · 记录状态

    未知→live_content

    content_served

已记录的活动

4 entries
  1. Google Safe Browsing

    无威胁标记

    查看来源
  2. AlienVault OTX

    4 community references

    查看来源
  3. VirusTotal

    7/92 engine detections

    查看来源
  4. 已添加至 PhishDestroy

    gmeet.com.br

    查看来源

仿冒域名

已存储 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

伪装检测

比较浏览器与爬虫各自收到的内容,并检查是否存在 Keitaro 流量分发。

gmeet.com.br

证据与外部报告

深度分析
Help & reporting

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

4 个证据信号组已关联 0 条已存档通知记录 最后已知的活跃状态

列入名单的域名至少会收到一份滥用举报;此条目没有保留的通知记录。

如果凭据已泄露,请立即报告。 切勿理会声称可追回资金的诈骗者。

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

Official reporting routes

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

向当地主管部门报告

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

97个国家目录

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

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

针对受害者的建议与指导

请根据您提供过的信息选择相应的步骤。请将本报告的副本与您自己的记录一并保存。

我应该立即采取什么措施?

紧急

停止使用可疑网站。请通过官方应用或您已信任的网址访问真正的服务。

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

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

联邦调查局(FBI)指南

请将原始邮件、收据、消息和截图保存在安全的地方。基于事实的时间线有助于受理机构了解事件经过。 IC3 evidence guidance ↗

  • 付款记录 — 如果已付款,请保存收据、金额、日期、支付服务商和收款方信息。
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的(包括 gmeet.com.br)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

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

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

  • 联邦调查局(FBI)IC3 — 互联网犯罪投诉中心(美国联邦举报渠道)
  • 欧洲刑警组织 — 欧洲网络犯罪报告(欧盟)
  • Your bank or payment provider — 如果资金或银行卡信息已泄露,请通过官方联系方式尽快联系其反欺诈团队。
  • 当地警方 — 即使无法立即采取行动,也能留下正式记录

举报并不能保证追回损失或启动调查,但及时、准确的交易数据可以帮助执法机构和服务提供商追踪事件。

How do phishing scams typically work?

  • 虚假网站 — 与正规网站完全一致的克隆网站,仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任,随后钱被骗走
  • 退款诈骗 — 诈骗者冒充资金追回机构并索要预付费用。在独立核实服务方之前,切勿分享助记词或付款
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站,使得欺诈行为更难被察觉

将来我该如何保护自己?

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

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

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

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

实时威胁动态 对该列表提出异议
关于本报告来源、观测日期与更正

本报告汇总了已保存的页面快照、注册与网络记录、扫描器结果以及 PhishDestroy 举报历史。每个来源均保留各自的观测日期。打开来源报告即可查看原始结果。

AI 辅助分析的撰写时间: 。该分析描述的是当时可获得的证据;之后的来源核查结果可能有所变化。

快照记录的是当时显示的内容。扫描器结果记录的是该服务商在检查时的评估。有效证书或零检出结果都不能保证安全。

嵌入此报告附带证据链接的紧凑型小组件
HTML · IFRAME

嵌入此报告

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

embed.html
<iframe
  src="https://phishdestroy.io/zh/embed/domain/gmeet.com.br"
  title="PhishDestroy threat report for gmeet.com.br"
  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>