VirusTotal
6 / 92 engine detections
レポートを開く“Home”
Googleなりすまし: usdc026.com — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 6/92 (CRDF, Forcepoint ThreatSeeker, Fortinet, LevelBlue, SOCRadar); PhishDestroy…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 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
usdc026.com is an impersonation phishing page whose domain borrows the USDC stablecoin name, followed by a numeric suffix that suggests a mass-produced series of lookalike domains. It targets people holding or looking to use USDC, presenting itself as something connected to the stablecoin when it is not. PhishDestroy first flagged it on 2026-10-09, and as of 2026-10-19 the site was still online and serving content.
Sites like this rely on a trusted brand to make visitors drop their guard. They then push the visitor to hand over value or control, through a token "claim" or reward, a deposit or staking offer, a wallet connection, or a login form. The browser tab shows only "Home", a generic label that reveals nothing about the page's purpose, which is typical of quickly assembled impersonation pages. Depending on the lure, victims can lose USDC or other tokens sent to the operators, or lose control of a wallet or account whose access they entered.
On 2026-10-17, VirusTotal showed 6 of 92 engines flagging the domain: CRDF, Forcepoint ThreatSeeker, Fortinet, LevelBlue, SOCRadar and VIPRE. That is a low share of engines, but these are independent vendors reaching the same verdict, and most engines give no verdict at all on new phishing pages. The domain also appears in 4 AlienVault OTX threat pulses, which means other researchers are tracking it. Among blocklists, it is currently listed by PhishDestroy.
The domain was registered through Gname.com Pte. Ltd. on 2025-12-29, roughly nine months before PhishDestroy detected it. That gap points to a name held in reserve or used quietly before this campaign surfaced. Traffic passes through Cloudflare (address in Canada), which hides the real origin server from visitors and researchers. The HTTPS padlock comes from a standard Google Trust Services certificate, so it says nothing about whether the site is legitimate.
Do not send any USDC or other funds to this site, and do not act on any "claim", bonus or fee request it shows. If you connected a wallet, revoke any token approvals granted during that session. If you signed anything or typed a seed phrase, move your assets to a newly created wallet immediately. If you entered a password, change it everywhere you reused it and enable 2FA. Security teams should block usdc026.com at DNS and proxy level and watch for sibling domains that follow the same usdc-plus-number naming pattern.
Edge-IP の評判はこのドメインに起因しません。
drake.ns.cloudflare.comsofia.ns.cloudflare.comLocation describes the IP network.
24328292a162acb00029279c59a9c6adf96eaf771559154d68bc11591f2b0850Saved 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.usdc026.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of usdc026.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.
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
usdc026.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
No threat flag
View source6/92 engine detections
View source4 community references
View sourceusdc026.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 ↗
usdc026.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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.