VirusTotal
6 / 89 engine detections
レポートを開く“GFO-X”
MetaMaskなりすまし: gfo-xc.com — コンテンツが利用できません. 証拠の概要: VirusTotal 6/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); 2 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 89 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
gfo-xc.com is a phishing page built to pass as GFO-X, a crypto derivatives trading venue. Its page title reads simply "GFO-X", and the domain adds a stray "-xc" to the brand name so it looks plausible in a link or search result. It targets crypto traders who expect to log in to or fund an account with GFO-X. PhishDestroy first flagged it on 2026-09-15. The site has been offline since 2026-09-22 and was still unreachable on 2026-10-19.
Impersonation pages like this copy the look and name of a trusted trading platform and wait for visitors who arrive through ads, direct messages or lookalike search results. The fake GFO-X front end typically asks for account credentials, prompts a deposit to an address the operators control, or invites the visitor to connect a wallet. Anything typed in goes to the attackers, and crypto sent to the page cannot be recovered. Because the site's operators control the whole interface, any balance or "pending withdrawal" shown there means nothing.
Six of 89 VirusTotal engines flagged the domain as of 2026-09-17: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That is a modest count, but the vendors are independent of one another and agree on the verdict. The domain also appears on the MetaMask and SEAL blocklists alongside PhishDestroy's own. Both are crypto-focused lists, which puts it squarely in front of wallet users. Four AlienVault OTX threat pulses reference it as well.
The domain was registered on 2026-04-13 through Cloudflare, Inc., about five months before PhishDestroy detected it. The page was active for only a week after detection before going dark. Traffic was served through Cloudflare's network, with the IP geolocating to Canada, so the address shown is a proxy rather than the operators' real server. The Let's Encrypt certificate means the padlock icon proved nothing about who ran the site.
If you entered a GFO-X username or password on this domain, change it on the genuine platform. Change it on any other service where you reused it, and turn on app-based two-factor authentication. If you sent a deposit, record the transaction details and report them to your exchange and local authorities. Ignore anyone who later offers to recover the funds for a fee. If you connected a wallet, check for and revoke any token approvals you granted, and move assets to a fresh wallet if you signed anything unfamiliar. Defenders should block the domain and lookalike variants of the GFO-X name, and alert users who trade derivatives.
Last checked
Edge-IP の評判はこのドメインに起因しません。
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
ef1aaf8164fa6c595b77829c6b304400537d6c4b025c8fb3390aac905fc35c0f*.gfo-xc.comgfo-xc.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of gfo-xc.com · checked Sep 15, 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.
gfo-xc.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能→利用不可
到達可能
No threat flag
View source6/89 engine detections
View source4 community references
View sourcegfo-xc.com
View sourcePage captured
View source保存された類似ドメイン:79 件
Listed 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 ↗
gfo-xc.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.