VirusTotal
7 / 92 engine detections
Open reportgmeet.com.br is a MetaMask impersonation page detected by PhishDestroy on 2026-10-11. Risk: critical (100/100). Registrar: HSTDOMAINS. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 7/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
“Meet — Webinar”
7 / 92 engine detections
Open reportSuspicious
Open reportDBL_PHISH
4 community references
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
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.
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.
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.
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.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a10632-0f46-7083-9fdc-917411f5ede3 |
|---|---|
| Final url | https://gmeet.com.br/ |
| Status | 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"
} |
| Domain age days | 1 |
| Apex age days | 1 |
| Tls age days | 0 |
| Tls valid days | 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"
} |
Observed: · Retrieved:
| Uuid | b960dc13-028d-478a-804f-f234834a429c |
|---|---|
| Final url | https://gmeet.com.br/ |
| Status | 200 |
| History | [
{
"url": "https://gmeet.com.br/",
"status": 200
}
] |
| DOM structure hash | 5fe85b5a6f89f695f8ce2fc231b43c710be9f60769aae9e01bdb2f3598b38e5f |
| Document hash | fbfa5bc894a575cf9c1157ba66465a3c72751c6aaae9d41929609e4634773c53 |
| Domain risks | [
"Newly Seen Domains",
"Security Risks"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"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 valid | false |
| Ip | 188.114.97.0 |
| Registration record | {
"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"
]
} |
Observed: · 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 |
| First seen | 2026-10-02T21:25:14Z |
| DNS records | [
{
"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"
} |
No. PhishDestroy classifies gmeet.com.br as a MetaMask impersonation page (risk: critical, 100/100); it was first detected on 2026-10-11. VirusTotal: 7/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on gmeet.com.br. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Last checked
Edge-IP reputation is not attributed to this domain.
stan.ns.cloudflare.comLocation describes the IP network.
77776575fca02056a206032a8558a0ad261a9e7578194cee3d128b3a95594598*.gmeet.com.brgmeet.com.brSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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 recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of gmeet.com.br · checked Oct 12, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
No threat flag
View source4 community references
View source7/92 engine detections
View sourcegmeet.com.br
View source79 stored lookalike domains
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
gmeet.com.br
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
gmeet.com.br)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.