Ir para o relatório de segurança
Segurança de domínio e inteligência contra ameaças
mexc.monster favicon

mexc.monster

“MEXC 是您获取加密货币的最简单方式。探索世界领先的加密货币交易所,购买、交易和赚取加密货币。交易比特…”

Registrador
Gname
Resolved IP
45.192.98.52
Registered
31/08/2025
PhishDestroy assessment Crítico
First observed Sep 9, 2025 13:04 UTC · PhishDestroy
Detecções do VirusTotal: 3/91 Rótulo automático de marca: Mexc
OTX: 11 refs 09/09/2025
API
Este domínio foi sinalizado como malicioso
Mecanismos de segurança relatando uma detecção: 3. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Resumo do relatório

Imitação de Mexc: mexc.monster — Não verificado. Resumo das evidências: VirusTotal 3/91 (alphaMountain.ai, Chong Lua Dao, Gridinsoft); PhishDestroy score…

A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.

Source evidenceVirusTotal 3 / 91 · OTX 11 references 5 sources

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

Analysis

Crítico
VirusTotal
3 / 91
OTX
11 community refs
Page captures
2

PhishDestroy threat report

The domain mexc.monster is a confirmed phishing site engaged in brand impersonation targeting the cryptocurrency exchange MEXC. It presents itself as the legitimate MEXC platform to deceive users into entering credentials or transferring funds, posing an elevated risk of financial loss through cryptocurrency scams. As of the latest verification, mexc.monster has been taken offline, though users who interacted with it while active remain at risk.

Technical analysis shows mexc.monster was flagged by 2 of 95 security vendors on VirusTotal, including CRDF and Gridinsoft, which assigned a trust score of 0 out of 100. The domain appears on one security blocklist, PhishDestroy, and was registered on August 31, 2025, through Gname.com Pte. Ltd. It resolved to the IP address 45.192.98.52, hosted in Hong Kong under AS401701 (cognetcloud INC), with no SSL certificate issued. The observed page title matched the legitimate MEXC branding in Chinese, reinforcing the impersonation attempt.

Users who accessed mexc.monster should immediately change any passwords or credentials entered on the site and enable two-factor authentication on their legitimate MEXC accounts. For cryptocurrency-related exposure, revoke any token approvals granted to unknown contracts and consider transferring funds to a new wallet. Report the phishing domain to the impersonated brand (MEXC) via their official support channels, and submit it to platforms like Google Safe Browsing, PhishTank, or local cybersecurity authorities for further action.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Captura armazenada · 2 captures

Observed page title
MEXC 是您获取加密货币的最简单方式。探索世界领先的加密货币交易所,购买、交易和赚取加密货币。交易比特币BTC、以太坊ETH 以及多种代币。
Automated brand references
Mexc

Domain details

Domínio
URLScan verdict Análise concluída score 0 report ↗
Reputação do IP abuse score 22/100 4 reports Port ScanBrute-Force checked 30/09/2026
OTX tags 2025-09activeall-domainsblocklistcontentcryptodomíniosdrainerfraudmonthlyphishdestroyphishingscam
Registrador Gname SG(SG)
Contato para abusosabuse@name.com
Registro da ICANNICANN Lookup (RDAP) →
RegistroCriado 31/08/2025 — Expires 10/09/2025
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez09/09/2025
DOM Analysisanalyzed 20/10/2026score 81/1001 brand signal
Submitted URLhttps://mexc.monster/
Favicon Hash
ICANN OVERSIGHT

Credenciamento e contexto 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 Nada é enviado automaticamente.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
45.192.98.52
Network ASN
AS401696
Organization
AS401701 cognetcloud INC
Observed location
Hong Kong, HK
Server header
nginx

Servidores de nomes 1

  • 1

Location describes the IP network.

Latest Classified Outcome 2026-10-20 08:21:37 UTC

Primary outcome DNS inativo reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Desconhecido Probe Inconclusive 20% 2026-10-19 22:18:17 UTC
RDAP registration Desconhecido
Observed timeline last reachable: 2026-09-15 22:18:04 UTC current episode first observed: 2026-10-02 16:16:28 UTC observed RIP window: 2026-09-15 22:18:04 UTC → 2026-10-02 16:16:28 UTC · 401.97h midpoint estimate ≈ 2026-09-24 07:17:16 UTC · precision low · basis bounded
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.
Denunciar este domínio Envie evidências e ajude a proteger outras pessoas

Análise do VirusTotal

3 / Os fornecedores de segurança 91 sinalizaram este domínio
View on VT
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
Chong Lua Dao
Gridinsoft
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
401.97
Estimate basis
Bounded by observations
Estimate precision
Low

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.

No cloaking flag in this check

unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='mexc.monster', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S

mexc.monster
Resultado salvo
Cloaked / Filtered
Stored observation history16

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

    Desconhecido→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

Earlier observations 11
  1. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  9. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    Desconhecido→dns_inactive

    dns_nxdomain

  11. Availability monitor · Recorded state

    https://radar.cloudflare.com/scan/3ffece3e-a7b1-4c72-b310-0dba11a5409a

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    3/91 engine detections

    View source
  3. AlienVault OTX

    11 community references

    View source
  4. URLScan

    Page captured

    View source
  5. Added to PhishDestroy

    mexc.monster

    View source

Denúncias da comunidade

Denunciado por 1 membro da comunidade; visto pela primeira vez em 09/09/2025

Denúncias armazenadas
1
URLs únicas denunciadas
1
Aceita1

Evidências e relatórios externos

Análise aprofundada
Help & reporting

Você foi afetado por este site?

4 evidence signal groups linked 0 stored notification records Não verificado

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.

Se você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.

Official reporting routes

Cuidado com os golpistas que prometem recuperação! Os criminosos podem entrar em contato novamente com as vítimas fingindo ser investigadores, advogados ou agentes de recuperação. Não pague taxas antecipadas nem compartilhe credenciais. Saiba mais sobre fraudes relacionadas à recuperação →

Notifique as autoridades locais

Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.

Diretório de 97 países

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

Rascunho assistido por IA – os detalhes do incidente são processados pelo provedor de IA · Revise e envie você mesmo
After a phishing incident

Recomendações e orientações para as vítimas

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

O que devo fazer agora mesmo?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Alterar todas as senhas — e-mail, contas do Exchange, qualquer coisa que use a mesma senha
  • Ativar a autenticação de dois fatores usando um aplicativo autenticador (não por SMS). Desative a recuperação por SMS
  • Cartões de congelamento se você inseriu dados bancários no site de phishing

Que informações devo coletar para o meu relatório?

Diretrizes do 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.
  • Datas e horários exatos — de cada transação e do primeiro contato com o golpista
  • Capturas de tela — sites fraudulentos, mensagens de bate-papo, e-mails, transações em carteiras digitais, redes sociais
  • Todas as URLs e domínios utilizado pelo golpista (incluindo mexc.monster)
  • Comunicações — e-mails, mensagens de texto, números de telefone e nomes de usuário que o golpista utilizou

Mesmo que você não tenha todos os detalhes — registre uma ocorrência mesmo assim. Mesmo informações parciais ainda ajudam nas investigações.

A quem devo denunciar o golpe?

  • FBI IC3 — Centro de Denúncias de Crimes na Internet (sistema federal de denúncias dos EUA)
  • Europol — Relatórios sobre crimes cibernéticos na Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polícia local — cria um registro oficial, mesmo que não possam agir imediatamente

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?

  • Sites falsos — clones idênticos, até o último pixel, de sites legítimos, com domínios ligeiramente alterados
  • Abate de suínos — confiança construída ao longo de semanas pelo Telegram, WhatsApp e aplicativos de namoro; em seguida, o dinheiro foi roubado
  • Golpes relacionados à recuperação — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Golpes baseados em IA — deepfakes, phishing automatizado e sites gerados por IA, o que torna a fraude mais difícil de detectar

Como posso me proteger no futuro?

  • Adicione os sites oficiais aos favoritos — nunca clique em links de e-mails, mensagens diretas ou anúncios
  • Verificar domínios — verificar PhishDestroy antes de interagir. Verifique se o site usa HTTPS, a ortografia e a idade do domínio
  • "Bom demais para ser verdade" = golpe — retornos garantidos, endossos de celebridades, prazos urgentes

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

Mantenha-se informado, mantenha-se seguro

Monitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo

Feed de ameaças em tempo real Recorrer deste anúncio
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

Incorporar este relatório

Compartilhe essas informações sobre ameaças em seu site ou blog

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