VirusTotal
0 / 92
engines flag the domain
“onkeyon”
0 / 92
engines flag the domain
No threat flag
Not on Google threat lists at check time
0
threat pulses mention the domain
Online · HTTP 200
Cloudflare · 188.114.96.1 · TLS: Google Trust Services
Each check shows its own collection time. Zero detections do not guarantee safety.
冒充 Google: usdc331.com — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 2/92 (Forcepoint ThreatSeeker, LevelBlue); PhishDestroy score 73/100. 注册商: Gname.
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
2 / 92 engine detections
打开报告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
usdc331.com is an impersonation phishing site whose name borrows the USDC stablecoin ticker plus a number, a pattern meant to look like an official or promotional USDC address to stablecoin holders. PhishDestroy first flagged it on 2026-10-09. The site has been offline since 2026-10-14, and its content was blocked by the provider as of 2026-10-19. The page title reads "onkeyon", which does not match the USDC branding in the domain, while we classified the site as impersonation phishing.
Sites that trade on a stablecoin's name usually pose as an official USDC portal, a reward claim, or a high-yield savings offer. The victim is then pushed to connect a wallet and sign a transaction, enter a recovery phrase, or send USDC as a deposit or "activation" payment. Each route ends the same way: the funds or the wallet's control pass to the operators. Stablecoin transfers settle quickly and cannot be reversed by the issuer on the victim's behalf.
Independent detection was thin. On 2026-10-13 only 2 of 92 VirusTotal engines flagged the domain, Forcepoint ThreatSeeker and LevelBlue, so most security products would have let it load without warning. PhishDestroy is the only blocklist carrying it. The domain does appear in 4 AlienVault OTX threat pulses, which shows other researchers tracked it.
The domain was registered on 2025-11-09 through Gname.com Pte. Ltd. It sat for about eleven months before PhishDestroy detected it, which fits an address registered in advance and switched on for a campaign later. It was served through Cloudflare's network with a Canadian location, so the hosting IP hides the real origin server. Its Google Trust Services certificate was an ordinary automated issue, so the browser padlock said nothing about whether the site was legitimate.
If you connected a wallet to usdc331.com, review and revoke its token approvals with a reputable approval checker, and move remaining assets to a new wallet if you signed anything you did not understand. If you typed your recovery phrase into the site, treat that wallet as compromised and transfer funds to a freshly generated wallet at once. Any USDC sent as a deposit or fee is gone. Ignore follow-up "recovery" offers, which are a common second scam. Defenders should block the domain and similar numbered USDC lookalikes, and check proxy logs for visits around 2026-10-09 to 2026-10-14.
Edge-IP 声誉不属于此域。
drake.ns.cloudflare.comsofia.ns.cloudflare.comLocation describes the IP network.
5a8e8f7845c1e06066c50c740897d45270e13643446da30de22fe1e9a18a7ac9Saved 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.usdc331.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of usdc331.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
usdc331.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 source2/92 engine detections
View source4 community references
View sourceusdc331.com
View sourcePage captured
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
usdc331.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
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.