Google Safe Browsing
No threat flag
Not on Google threat lists at check time
“onkeyon”
No threat flag
Not on Google threat lists at check time
0
threat pulses mention the domain
Online · HTTP 200
Cloudflare · 172.67.187.237 · TLS: Google Trust Services
Each check shows its own collection time. Zero detections do not guarantee safety.
冒充 Google: usdc052.com — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 2/92 (Gridinsoft, LevelBlue); PhishDestroy score 81/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
usdc052.com is an impersonation phishing site whose domain uses the USDC stablecoin name with a numeric suffix. That pattern is meant to look like a legitimate USDC portal to people holding or trading the token. PhishDestroy first flagged it on 2026-10-09. The site has been offline since 2026-10-14, its content blocked at the provider level, and it was still down when last checked on 2026-10-19.
Sites like this borrow the credibility of a well-known asset to lure visitors into a fake service. Typical lures are a fake balance, a bonus or a "verification" step. The victim is then asked to connect a wallet and sign transactions, enter a recovery phrase, or send USDC as a deposit. Any of these can hand control of the funds to the operator, and stablecoin transfers cannot be reversed. The page itself carried the title "onkeyon", which does not match the USDC branding in the domain, while our classification is impersonation phishing.
Independent detection is thin. On 2026-10-13, 2 of 92 VirusTotal engines (Gridinsoft and LevelBlue) marked the domain as malicious. PhishDestroy is the only blocklist carrying it, so most browsers and security tools will not warn a visitor. Four AlienVault OTX threat pulses reference the domain, which shows other researchers have linked it to suspicious activity.
The domain was registered through Gname.com Pte. Ltd. on 2025-12-29, more than nine months before PhishDestroy caught it. That gap suggests the name was held in reserve or used quietly before this campaign surfaced. It sat behind Cloudflare, with the edge address geolocated to Canada, so the actual origin server is hidden. Its certificate came from Google Trust Services (WE1), an automated issuer, so the padlock said nothing about who ran the site.
If you connected a wallet to usdc052.com, check your token approvals and revoke any you do not recognize, especially unlimited USDC allowances. If you typed in a recovery phrase, treat that wallet as compromised and move the remaining assets to a new wallet created on a clean device. Do not send more funds to "unlock" or "verify" a balance, because those requests are part of the theft. Security teams should block the domain, search DNS and proxy logs for past visits, and watch for other USDC-named domains with numeric suffixes.
Edge-IP 声誉不属于此域。
drake.ns.cloudflare.comsofia.ns.cloudflare.comLocation describes the IP network.
7758616e3c1d3bb3f11369ade1fd73931b71993779b445a5f3738dff7929e922Saved 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.usdc052.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of usdc052.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
usdc052.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 sourceusdc052.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 ↗
usdc052.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.