usdc.website is a credential phishing page that used the USDC stablecoin name to lure crypto users into a fake Google sign-in. Its page title, "usdc.website | Google-login crypto payments", presented it as a payment service you could log into with a Google account. PhishDestroy first flagged it on 2026-08-31. The site went offline on 2026-09-11 and was still dead, with no active DNS, when last checked on 2026-10-19.
How the scam works
The pitch combines two familiar things: a stablecoin brand and the convenience of signing in with Google. Instead of a real Google login, the visitor gets a lookalike form that sends the email, password and often a one-time 2FA code straight to the operators. A captured Google account rarely stops at email. It can unlock password resets, saved passwords, cloud files and any exchange or wallet service where the victim signs in with Google. That is the real prize, not a payment.
Evidence
Six of 91 VirusTotal engines flagged the domain on 2026-08-31: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and Kaspersky. Most engines did not flag it on that date. Spamhaus lists the domain in its DBL as phishing. The crypto-specific blocklists of MetaMask and SEAL also carry it, alongside PhishDestroy. Three AlienVault OTX threat pulses reference it, so several independent researchers tracked it separately.
Infrastructure
The domain was registered through Name.com, Inc. on 2026-06-23, about ten weeks before PhishDestroy detected it. That gap fits a domain held in reserve before a campaign began. The site was hosted on Amazon.com, Inc. infrastructure in the United States. It lasted only eleven days after detection before going offline.
What to do
If you entered your Google credentials on this site, change your Google password now. Then check your 2-Step Verification settings, recovery email and recovery phone for changes you did not make. In your Google security page, sign out of unfamiliar sessions and remove third-party apps you do not recognise. Next, review every exchange, wallet service or other account you access through Google sign-in, plus any account that shares the same password, and change those credentials. Defenders should block the domain and search DNS and proxy logs for past lookups. Any user who resolved it should be treated as possibly compromised and have their Google account reviewed.
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:13:31 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-08-31 22:16:17 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-31 22:16:17 UTC → 2026-09-30 16:14:55 UTC · 713.98hmidpoint estimate ≈ 2026-09-15 19:15:36 UTC · precision 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.
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.
