VirusTotal
7 / 89 engine detections
打开报告“GFO-X”
冒充 MetaMask: gfo-xu.com — 内容不可用. 证据摘要: VirusTotal 7/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); 2 external blocklist matches…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
7 / 89 engine detections
打开报告3 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-xu.com is a phishing page that impersonated GFO-X and displayed the page title "GFO-X". The domain adds a single "u" to the brand name, so it can pass a quick glance in a search result, ad or chat link. It targeted crypto traders who believed they were reaching the genuine platform. PhishDestroy first detected it on 2026-09-15. The site went offline on 2026-09-22 and was still unreachable when last checked on 2026-10-19.
Impersonation pages like this copy a trading brand's name and look, then put a familiar login, sign-up or deposit flow in front of the visitor. Usernames, passwords and one-time codes typed there go straight to the operators, who can use them on the real account. Deposits sent to addresses shown on the clone cannot be recovered. A prompt to connect a wallet can lead to signatures or approvals that let the attacker move tokens.
MetaMask's and SEAL's blocklists both list the domain alongside PhishDestroy, so two independent crypto-security teams reached the same verdict. On 2026-09-17, VirusTotal showed 7 of 89 engines flagging it: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, LevelBlue and SOCRadar. That count is modest, so many standard browser and antivirus filters would not have warned visitors. Three AlienVault OTX threat pulses also reference the domain, which ties it to wider threat reporting.
The domain was registered on 2026-04-13 through Cloudflare, Inc., about five months before PhishDestroy detected it. That gap suggests it was registered and held in reserve rather than used straight away. Its address resolved to Cloudflare's network, geolocated to Canada, which means Cloudflare's proxy hid the true origin server. A free Let's Encrypt certificate gave the page a padlock, which shows only that the connection was encrypted, not that the site was legitimate. It stayed online for roughly a week after first detection.
If you signed in on gfo-xu.com, change your GFO-X password at once and update it anywhere you reused it. Reset two-factor authentication and review active sessions and API keys on the real account. If you sent funds to an address shown on the site, record the transaction details and report them to the genuine platform and your local authorities. If you connected a wallet, revoke any approvals you granted and move assets out if you signed anything unfamiliar. Defenders should block the domain and lookalike variants of the GFO-X name, and check logs for visits from mid-September 2026.
Last checked
Edge-IP 声誉不属于此域。
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
e01207b0ec1614f07007921c99c300c1a514ae61cd5fa3d8d33e5893b16ef141*.gfo-xu.comgfo-xu.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-xu.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.
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 source7/89 engine detections
View source3 community references
View sourcegfo-xu.com
View sourcePage captured
View source已存储 79 个仿冒域名
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
gfo-xu.com
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-xu.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.