VirusTotal
2 / 92
engines flag the domain · 1 suspicious
“Home”
2 / 92
engines flag the domain · 1 suspicious
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
malicioussuspicious
Each check shows its own collection time. Zero detections do not guarantee safety.
冒充 Google: usdc028.com — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 4/92 (Forcepoint ThreatSeeker, Gridinsoft, LevelBlue, SOCRadar); PhishDestroy score 81/100.…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
4 / 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
usdc028.com is an impersonation phishing site whose domain uses the USDC stablecoin name plus a numeric suffix, a pattern built to look like an official or regional USDC service. It targets crypto users who hold or trade stablecoins. PhishDestroy first flagged it on 2026-10-09. The site has been offline since 2026-10-14, with its content blocked at the provider level, and was still down at the last check on 2026-10-19.
Impersonation pages like this borrow a trusted crypto brand to make a fake platform feel legitimate. The victim is then steered into whatever the operator wants: connecting a wallet and signing a transaction, entering login details or a recovery phrase, or depositing USDC into an account they will never be able to withdraw from. The page carried only the generic title "Home", which names no brand, while the domain itself is what invokes USDC. Victims typically lose the stablecoins they send or approve, along with any credentials typed into the site.
Four of 92 VirusTotal engines flagged the domain as of 2026-10-13: Forcepoint ThreatSeeker, Gridinsoft, LevelBlue and SOCRadar. That is a small share, which is common for short-lived scam domains that are only scanned after they go live. Four AlienVault OTX threat pulses also reference it, so researchers outside PhishDestroy have independently tracked it. Among the blocklists we checked, only PhishDestroy lists it.
The domain was registered through Gname.com Pte. Ltd. on 2025-12-29, more than nine months before PhishDestroy detected it. That gap suggests it was either held in reserve or ran for a long time before anyone reported it. Traffic passed through Cloudflare, Inc., which places the visible IP in Canada and hides the real origin server behind the proxy.
If you deposited USDC on this site, do not pay any "fee", "tax" or "unlock" charge to get it back. Those demands are a second round of the same theft. If you connected a wallet, revoke any token approvals granted during that session and move remaining funds to a fresh wallet if you signed anything unfamiliar. If you entered a seed phrase, treat that wallet as compromised and empty it immediately. If you reused a password there, change it everywhere and enable 2FA. Defenders should block the domain and watch for other domains that combine "usdc" with numbers, since operators often rotate through these variants.
Edge-IP 声誉不属于此域。
drake.ns.cloudflare.comsofia.ns.cloudflare.comLocation describes the IP network.
49bc1ae0878a86b27721fccd0498ecd17a6fbeacfdaf077126638de3948f813cSaved 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.usdc028.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of usdc028.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
usdc028.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 source4/92 engine detections
View source4 community references
View sourceusdc028.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 ↗
usdc028.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.