VirusTotal
12 / 91 engine detections
レポートを開く“Mixer USDC Network — Private USDC Routing”
フィッシング: mixer-usdc.network — コンテンツが利用できません. 証拠の概要: VirusTotal 12/91 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet); URLQuery 2 det.…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
12 / 91 engine detections
レポートを開く2 det.
レポートを開く4 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
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.
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.
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.
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.
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.
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.
Edge-IP の評判はこのドメインに起因しません。
charles.ns.cloudflare.comharleigh.ns.cloudflare.comLocation describes the IP network.
e0013c768e2b168e1669ac2ee71fdf73302e6c3d988b73c56d5f4375dc8603daSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of mixer-usdc.network · checked Aug 18, 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.
mixer-usdc.network
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
到達可能→利用不可
2→4
0→2
到達可能
12/91 engine detections
View source4 community references
View sourceNo threat flag
View sourcePD-20260818-C048B7
mixer-usdc.network
View sourcePage captured
View sourcePD-20260818-C048B7 Recipient: abuse@ownregistrar.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 ↗
mixer-usdc.network)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.