VirusTotal
9 / 89 engine detections
Mở báo cáo“GFO-X”
Lừa đảo: gfo-btc.com — Nội dung không có sẵn. Tóm tắt bằng chứng: VirusTotal 9/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Google Safe…
Phân tích chi tiết của PhishDestroy AI bên dưới được giữ bằng tiếng Anh để bảo toàn hồ sơ pháp chứng gốc.
9 / 89 engine detections
Mở báo cáoDBL_PHISH
4 community references
Mở báo cáoprovider verdict: clean
Mở báo cáoNo threat flag
Mở báo cáoNo malicious flag
Mở báo cáoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
gfo-btc.com is an impersonation phishing page that carried the title "GFO-X" and paired that brand with "btc" in its domain to look like a Bitcoin-related service of the real name. It targeted crypto users who might trust a familiar trading brand. PhishDestroy first caught it on 2026-09-15, the same day the domain was registered. The site has been offline since 2026-09-22 and was still unreachable when last checked on 2026-10-19.
Impersonation pages like this copy the look and name of a known platform, here GFO-X, so visitors believe they are on the genuine service. The goal is to get victims to hand over login credentials, send crypto deposits, or connect and authorize a wallet on a page the attackers control. Anything entered or approved goes straight to the operators. Stolen funds are effectively unrecoverable once sent on-chain.
Nine of 89 VirusTotal engines flagged the domain as of 2026-09-17. They include Google Safe Browsing, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF, Gridinsoft, LevelBlue and SOCRadar. Google Safe Browsing's verdict matters most, because it drives warnings in mainstream browsers. Beyond PhishDestroy, the domain sits on the MetaMask and SEAL blocklists, which shows wallet-security teams treated it as a crypto threat. Spamhaus lists it in its DBL as phishing, and four AlienVault OTX pulses reference it.
The domain was registered and detected on the same day, 2026-09-15, and was offline a week later. That short life is typical of throwaway phishing domains. It was registered through Cloudflare, Inc. and served from Cloudflare's network, geolocated to Canada. That network hides the real origin server. Its Let's Encrypt certificate gave visitors a padlock, which only means the connection was encrypted, not that the site was legitimate.
If you entered a password or 2FA codes on gfo-btc.com, change that password wherever you reused it, reset 2FA, and review your account activity on the genuine platform. If you connected a wallet or signed anything, revoke token approvals with a trusted approval-management tool. Move remaining assets to a fresh wallet if you shared a seed phrase. Never deposit funds through a site you reached by a link; type the official address yourself. Defenders should block the domain at DNS and proxy level and search their logs for past visits.
Last checked
Danh tiếng của Edge-IP không được quy cho tên miền này.
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
8fef3fc5ee139d21554b381499dec6083ca8568cfe29fce2c58bc95a9cc0998cSaved 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-btc.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-btc.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Có thể truy cập→Không có sẵn
0→3
No flag recorded→Flag recorded
Có thể truy cập
No threat flag
View source9/89 engine detections
View source4 community references
View sourcegfo-btc.com
View sourcePage captured
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
Nếu bạn đã nhập thông tin xác thực tài khoản, thông tin cá nhân hoặc thông tin thanh toán hoặc đã tải xuống tệp từ miền này, hãy hành động ngay lập tức. Dưới đây là các nguồn lực giúp bạn báo cáo vụ việc và bảo vệ chính mình.
Chọn quốc gia của bạn để nhận liên hệ tội phạm mạng chính thức hoặc soạn thảo đơn khiếu nại →.
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-btc.com)Dù bạn chưa nắm rõ tất cả các chi tiết — vẫn nên nộp báo cáo. Ngay cả những thông tin không đầy đủ cũng vẫn có ích cho công tác điều tra.
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
Phân tích mối đe dọa bằng cách sử dụng danh sách chặn được lưu trữ, WHOIS, DNS và bằng chứng quét công khai
Quét ngayHãy gửi các tên miền đáng ngờ đến cơ sở dữ liệu mối đe dọa của chúng tôi — để bảo vệ cộng đồng
Báo cáoCác báo cáo lừa đảo gần đây và những thay đổi về tính khả dụng được quan sát thấy
Theo dõiTheo dõi các mối đe dọa đang diễn ra hoặc phản đối danh sách này nếu bạn cho rằng đây là kết quả báo động sai
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.