VirusTotal
4 / 92 engine detections
レポートを開く“Home”
The sent-report ledger records the first outgoing report at .
The recorded recipient is complaint@gname.com.
The latest stored availability evidence still shows the domain reachable; 11 days 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.
Googleなりすまし: usdc023.com — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 4/92 (Forcepoint ThreatSeeker, Gridinsoft, LevelBlue, SOCRadar); PhishDestroy score…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 92 engine detections
レポートを開くScan report
レポートを開く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
usdc023.com is an impersonation phishing site whose name borrows the USDC stablecoin brand, with a number tacked on so it looks like one of many official-sounding mirrors. It targets people who hold or trade USDC and might trust a site that seems tied to the token. PhishDestroy first flagged it on 2026-10-09. The site has been offline since 2026-10-14, and the hosting provider was still blocking its content on 2026-10-19.
Sites built on a stablecoin's name usually pose as an official USDC platform, rewards program or staking service. They push visitors to connect a wallet, approve a transaction, or send USDC as a deposit. What the victim loses is the crypto itself, either transferred directly or drained later through a signed approval. The page carried only the bland title "Home", which gives no hint of the USDC theme the domain name sets up.
On 2026-10-13, 4 of 92 VirusTotal engines marked the domain malicious: Forcepoint ThreatSeeker, Gridinsoft, LevelBlue and SOCRadar. That is a small share, typical of short-lived scam domains that go offline before most engines catch up. It still means four independent vendors reached the same verdict. The domain also appears in 4 AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered on 2025-12-29 through Gname.com Pte. Ltd., more than nine months before PhishDestroy detected it. That gap suggests it was bought early and held in reserve, or rotated in quietly before anyone noticed. Traffic ran through Cloudflare, Inc., with a Canadian network location, so the real origin server was hidden behind the proxy.
If you sent USDC or other tokens to this site, record the transaction hashes and report them to the platform you sent from. Do not pay any further "unlock" or "verification" fees, because these are a common follow-up in this kind of scheme. If you connected a wallet or signed anything, revoke the token approvals you granted, and move remaining assets to a fresh wallet if you entered a seed phrase. Security teams should block the domain and look for similarly numbered USDC-themed domains that may share the same registrar and Cloudflare setup.
Edge-IP の評判はこのドメインに起因しません。
drake.ns.cloudflare.comsofia.ns.cloudflare.comLocation describes the IP network.
859e1b8ceef97e8353cb18239d9a9e80f2fd58c3714f9b8f88ce210e04fe3ef5Saved 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.usdc023.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of usdc023.com · checked Oct 9, 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
usdc023.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
live_content→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
No threat flag
View source4/92 engine detections
View source4 community references
View sourcePD-20261009-8C8C5F
usdc023.com
View sourcePage captured
View sourcePD-20261009-8C8C5F Recipient: complaint@gname.com Registrar: Gname.com Pte. Ltd. (Singapore) Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
usdc023.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.