Security engines reporting a detection: 6. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
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.
RegistrationCreated Jun 23, 2026 (118d)—Expires Jun 23, 2027
Time to First Unavailability11 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 31, 2026
Submitted URLhttp://usdc.website/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
216.150.16.65
Network ASN
AS16509
Organization
Vercel, Inc
Observed location
Walnut, US
Server header
Vercel
Edge-IP reputation is not attributed to this domain.
Nameservers 2
ns1.vercel-dns.com
ns2.vercel-dns.com
Location describes the IP network.
TLS certificate
Issuer
YR1
Collection time
2026-08-31 10:02:08 UTC
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-19 01:13:31 UTC
RDAP registrationUnknown
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.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · usdc.website
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
7 evidence signal groups linked1 stored notification recordsContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
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.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including usdc.website)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
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?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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.
