ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
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.
usdc227.com is an impersonation phishing site whose name borrows the USDC stablecoin brand, aimed at people who hold or trade stablecoins. PhishDestroy first flagged it on 2026-10-09, and it was still online with live content when last checked on 2026-10-19. The page title reads "onkeyon", which does not match the USDC branding in the domain, while we classify the site as impersonation phishing.
How the scam works
Sites built around a stablecoin name usually pose as an official USDC portal, a yield or staking product, or a reward claim, so that a numbered domain looks like a legitimate service. The visitor is pushed to connect a wallet and sign a transaction, or to send USDC as a deposit or activation step. A signed token approval lets the operator move funds out of the wallet later without asking again. Deposits sent to the site do not come back, and requests for more money to unlock a balance are part of the scheme.
Evidence
Six of 92 VirusTotal engines flag the domain as of 2026-10-17: CRDF, Forcepoint ThreatSeeker, Fortinet, LevelBlue, SOCRadar and VIPRE. Most engines do not yet flag it, but these are independent vendors that reached the same conclusion. The domain also appears in four AlienVault OTX threat pulses, so other analysts are tracking it too. PhishDestroy lists it on its own blocklist.
Infrastructure
The domain was registered on 2025-11-09 through Gname.com Pte. Ltd., about eleven months before PhishDestroy detected it. A registered domain left unused for that long can be held back for a later campaign. The site sits behind Cloudflare, with an edge address in Canada, so the real origin server is hidden from visitors and researchers.
What to do
If you connected a wallet to usdc227.com, review its token approvals with a revocation tool and cancel any granted to unfamiliar contracts. Move remaining funds to a fresh wallet if you signed anything you did not understand. Never type a seed phrase into this or any similar site. Do not send further payments to unlock or withdraw a balance, and report any transfers to your exchange and local authorities. Defenders should block the domain at DNS and proxy level, search logs for past visits, and report it to Cloudflare and the registrar for takedown.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-19 22:41:03 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-19 22:41:03 UTClast content: 2026-10-19 22:41:03 UTC
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.
Recorded subdomains1
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.usdc227.comDomain record
The original observation time is not recorded for these hostnames.
技术 · 4 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.
(KH)
