VirusTotal
3 / 91 engine detections
Відкрити звіт“MEXC 是您获取加密货币的最简单方式。探索世界领先的加密货币交易所,购买、交易和赚取加密货币。交易比特…”
підробка під Mexc: mexc.monster — Неперевірений. Зведення доказів: VirusTotal 3/91 (alphaMountain.ai, Chong Lua Dao, Gridinsoft); PhishDestroy score 81/100.…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
3 / 91 engine detections
Відкрити звіт11 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
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.
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.
1Location describes the IP network.
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.
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
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
https://radar.cloudflare.com/scan/3ffece3e-a7b1-4c72-b310-0dba11a5409a
No threat flag
View source3/91 engine detections
View source11 community references
View sourcePage captured
View sourcemexc.monster
View sourceПовідомив 1 учасник спільноти; уперше помічено 09.09.2025
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 ↗
mexc.monster)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
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.