VirusTotal
7 / 89 engine detections
レポートを開く“GFO-X”
フィッシング: gfo-xb.com — コンテンツが利用できません. 証拠の概要: VirusTotal 7/89 (alphaMountain.ai, Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, Fortinet); 2 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
7 / 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-xb.com is an impersonation phishing page that carried the title "GFO-X" and borrowed the name of the digital-asset derivatives venue. It targeted traders and account holders who might mistake the extra "-xb" for a legitimate regional or product subdomain. PhishDestroy first flagged it on 2026-09-15. The site has been offline since 2026-09-22 and was still unreachable when last checked on 2026-10-19.
Lookalike pages like this copy a trusted brand's name and styling so that visitors arriving from ads, messages or search results believe they are on the real platform. Once trust is established, the page asks for whatever unlocks the victim's money. That can be login credentials and 2FA codes, a wallet connection or recovery phrase, or a deposit into an account the operators control. Because the page presented itself simply as "GFO-X", nothing on screen warned the visitor that the domain was not the genuine one.
On 2026-09-16, the day after our first sighting, 7 of 89 VirusTotal engines flagged the domain: alphaMountain.ai, Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That is a modest count, but it comes from vendors with independent detection methods. The domain also appears on the MetaMask and SEAL blocklists alongside PhishDestroy, which means crypto-focused defenders reached the same verdict separately. It is referenced in 4 AlienVault OTX threat pulses.
The domain was registered on 2026-04-13 through Cloudflare, Inc., about five months before it surfaced as a phishing page. That delay suggests it was held in reserve rather than used immediately. Traffic was served through Cloudflare's network, geolocated to Canada, so the visible IP belongs to the proxy rather than the operators' origin server. Its Let's Encrypt certificate gave the site a padlock, which proves only that the connection was encrypted, not that the site was legitimate.
If you entered a password or 2FA code on gfo-xb.com, change the password on the real GFO-X account and any account that reuses it, reset 2FA, and review recent logins and withdrawals. If you typed in a wallet recovery phrase, treat that wallet as compromised and move its funds to a newly created wallet immediately. Do not send further deposits or "verification" payments to anyone who contacted you through this site. Security teams should block the domain and close lookalike variants of the GFO-X name, and they should alert users that the hyphenated "-xb" form is not an official address.
Last checked
Edge-IP の評判はこのドメインに起因しません。
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
8b6a7b9b3c6c348e05a8b62b79bf888361e8d1ffb1b9c0a011b33586b9c0e60d*.gfo-xb.comgfo-xb.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-xb.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-xb.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能→利用不可
6→7
到達可能
No threat flag
View source4 community references
View source7/89 engine detections
View sourcegfo-xb.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 ↗
gfo-xb.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.