VirusTotal
17 / 89 engine detections
Mở báo cáo“Róbinhood Login to My Account”
Giả mạo Robinhood: robinhood-loxgin.gitbook.io — Hoạt động được biết đến lần cuối (HTTP 307). Tóm tắt bằng chứng: VirusTotal 17/89 (ChainPatrol…
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.
17 / 89 engine detections
Mở báo cáo15/100
Mở báo cáono 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
robinhood-loxgin.gitbook.io is a phishing page posing as the Robinhood sign-in screen. It is built on a GitBook subdomain and carries the page title "Róbinhood Login to My Account". It targets Robinhood customers who hold stocks or crypto on the platform. PhishDestroy first flagged it on 2026-09-11. As of 2026-10-19 the site was still online and redirecting visitors.
The name is built to pass a quick glance. "loxgin" stands in for "login", and the title swaps in an accented "Ó" so the brand looks right while dodging simple keyword filters. A victim who lands here, usually from a search ad, social post or message, is asked for their Robinhood email and password, and often a 2FA code. With those, the operator can take over the account, sell positions and move funds or crypto out before the owner notices.
On 2026-09-24, 17 of 89 VirusTotal engines flagged the page, including ESET, BitDefender, Emsisoft, Forcepoint ThreatSeeker, alphaMountain.ai, CyRadar, Chong Lua Dao and the crypto-focused ChainPatrol. That is a clear consensus for a page sitting on a legitimate platform's subdomain. MetaMask and SEAL also list it, alongside PhishDestroy, so wallet users and crypto security tooling already warn about it.
The 2014-03-30 registration date belongs to gitbook.io, the documentation platform, not to the attacker. This is a free subdomain, set up with no domain purchase of their own. It inherits GitBook's reputation and its Cloudflare-fronted hosting, which resolves to a Cloudflare network address in Canada. The valid Google Trust Services certificate comes from the platform, so the padlock says nothing about who runs this page.
If you entered credentials here, change your Robinhood password right away, along with any other account that shares it. Re-enroll two-factor authentication with an authenticator app, and sign out all other sessions from the security settings. Check your recent orders, transfers and linked bank accounts, and contact Robinhood support at once if anything moved without you. Defenders should block this specific subdomain rather than all of gitbook.io and report it to GitBook for removal. They should also watch for lookalike Robinhood subdomains on the same platform.
Last checked
Danh tiếng của Edge-IP không được quy cho tên miền này.
Location describes the IP network.
d76aa1094c3d1ca19014ac824313b04e833289dec61fbca06aa6f92bad9464adgitbook.ioSaved 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 robinhood-loxgin.gitbook.io · checked Sep 11, 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.
robinhood-loxgin.gitbook.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
Không rõ→redirected
http_redirect
14→15
No threat flag
View source17/89 engine detections
View sourcerobinhood-loxgin.gitbook.io
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 ↗
robinhood-loxgin.gitbook.io)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.