VirusTotal
12 / 89 engine detections
打开报告“Coinexes · USDC貯蓄”
The sent-report ledger records the first outgoing report at .
The recorded recipient is report@abuseradar.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
冒充 Coinex: coinexes.us — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 12/89 (alphaMountain.ai, BitDefender, Certego, CRDF, ESET); URLQuery 1 alert; URLScan…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
12 / 89 engine detections
打开报告1 threat-system alert
打开报告15/100
打开报告DBL_PHISH
恶意
打开报告4 community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | coinexes.us |
malicious | Sinkholed |
PhishDestroy threat report
coinexes.us poses as Coinex and presents itself as a USDC savings service. Its page title, "Coinexes · USDC貯蓄", pairs a near-copy of the brand with the CJK word for savings, which points at Asian-language users looking to park stablecoins for interest. PhishDestroy first flagged it on 2026-09-11. As of 2026-10-19 the site was still online and serving its content.
Fake exchange savings pages borrow a trusted name and offer attractive returns on USDC deposits. Victims are steered to send stablecoins or connect a wallet and fund a "savings" balance. The dashboard may show growing interest, but withdrawals are blocked or tied to new fees, taxes or verification deposits that are also kept. Whatever is sent to the site goes straight to the operators, and stablecoin transfers cannot be reversed.
On 2026-09-21, 12 of 89 VirusTotal engines flagged the domain, including BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, Certego and CRDF. That is a modest share, but the backing comes from established, unrelated vendors. urlscan.io rated the page malicious and matched it to the Coinex brand. Spamhaus lists it in its DBL as phishing, MetaMask and SEAL block it alongside PhishDestroy, and four AlienVault OTX pulses reference it.
The domain was registered on 2026-09-07 through Cloudflare, Inc. and was caught just four days later. A short gap like that is typical of throwaway domains bought for a single campaign. The site is hosted in the United States on MULTACOM CORPORATION's network. It was still reachable more than a month after detection.
Do not deposit anything through coinexes.us, and do not pay any "withdrawal fee" or "unlock" charge it demands. Those payments only add to the loss. If you connected a wallet, check and revoke any token approvals granted while on the site. If you entered Coinex login details, change your password and reset 2FA from the official app. Record transaction hashes and report the theft to the real Coinex support and your local police. Defenders should block the domain and the brand look-alike pattern at DNS and proxy level, and warn users that savings offers reached through unofficial links are a common trap.
Last checked
melody.ns.cloudflare.comremy.ns.cloudflare.comLocation describes the IP network.
11341ac052e56b736b110324b109e89878d55478ceda143f64565e4ff0294785www.coinexes.usSaved 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.coinexes.usDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of coinexes.us · checked Sep 11, 2026
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.
coinexes.us
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
可访问
4 community references
View sourceNo threat flag
View source12/89 engine detections
View sourcePD-20260911-0F210F
coinexes.us
View sourcePage captured
View sourcePD-20260911-0F210F Recipient: report@abuseradar.com 如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
coinexes.us)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.