mixer-usdc.network presented itself as "Mixer USDC Network — Private USDC Routing," a supposed privacy service for the USDC stablecoin. It targeted holders who wanted to obscure the trail of their transfers. PhishDestroy first flagged it on 2026-08-18 and classifies it as impersonation phishing. The site has been offline since 2026-09-11, and its DNS was still inactive when last checked on 2026-10-19.
How the scam works
The page title advertises a private USDC routing service. We classified the site as impersonation phishing. Fake mixers typically ask users to send stablecoins to a deposit address, or to connect a wallet, with the promise that clean funds will come back from a separate pool. Nothing is returned. Users who seek privacy are also unlikely to report the loss, which makes them convenient targets. A victim stands to lose everything deposited, along with any tokens a connected wallet was tricked into authorizing.
Evidence
When checked on 2026-08-26, VirusTotal showed 12 of 91 engines flagging the domain. The vendors included alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. That is a modest share, but these are independent engines from different vendors reaching the same verdict. The domain also appears in four AlienVault OTX threat pulses, so other researchers were tracking it too. PhishDestroy is the only blocklist in our set that lists it.
Infrastructure
The domain was registered on 2026-07-09 through OwnRegistrar, Inc., about 40 days before PhishDestroy detected it. That gap is consistent with a site set up in advance and then promoted. It ran behind Cloudflare in the US, which hides the real origin server from visitors. Its certificate came from Google Trust Services, so the browser padlock only meant the connection was encrypted, not that the operator could be trusted.
What to do
If you sent USDC to this site for "mixing," do not pay any fee or extra deposit you are offered to release it, because that is a common second-stage tactic. Record the transaction hashes and the deposit address, then report them to your exchange and to local cybercrime authorities. If you connected a wallet, check its token approvals with a revocation tool and revoke any unfamiliar spenders. Move remaining funds to a fresh wallet if you signed anything you did not understand. Defenders should keep blocking the domain and watch for lookalike mixer domains reusing the same branding.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-19 01:12:56 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-08-20 22:15:33 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-20 22:15:33 UTC → 2026-09-30 16:14:55 UTC · 977.99hmidpoint estimate ≈ 2026-09-10 07:15:14 UTC · precision very 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.
技术 · 5 identified
H
HSTS
安全
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
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?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
