VirusTotal
15 / 89 engine detections
فتح التقرير“Robinhood Login - Log in to My Account | (Official Website) | Robinhood Login - Log in to My Accoun…”
تصيد بيانات الدخول: robinhoodcomloginx.gitbook.io — آخر نشاط معروف (HTTP 307). ملخص الأدلة: VirusTotal 15/89 (ChainPatrol, alphaMountain.ai, BitDefender…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
15 / 89 engine detections
فتح التقريرضار
فتح التقريرno community references
فتح التقرير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
robinhoodcomloginx.gitbook.io is a credential phishing page that poses as the Robinhood sign-in portal. It targets Robinhood customers who hold stocks or crypto. PhishDestroy first flagged it on 2026-09-11. As of 2026-10-19 the site was still online and redirecting visitors.
The page title repeats "Robinhood Login - Log in to My Account | (Official Website)" over and over. That keyword stuffing is meant to push the page up search results for people typing "Robinhood login". Hosting it on a public documentation platform gives it a familiar-looking address. Anyone who follows it is led to enter their Robinhood email, password and often a one-time code. With those details, operators can take over the brokerage account, sell holdings, move out crypto and harvest personal and identity data.
On 2026-09-24, VirusTotal showed 15 of 89 engines flagging the page. They include crypto-focused ChainPatrol and Chong Lua Dao, along with BitDefender, ESET, Emsisoft, Fortinet, Forcepoint ThreatSeeker and alphaMountain.ai. The domain also sits on the MetaMask and SEAL blocklists next to PhishDestroy. That means wallet-security teams reached the same verdict on their own.
This is a subdomain on gitbook.io, so the 2014-03-30 registration date and the Cloudflare, Inc. registrar belong to the parent platform, not to this page. The operators did not buy a domain. They borrowed the reputation of an established service, which helps the link get past casual suspicion and some filters. Traffic is served through Cloudflare's network from an address located in Canada. The Google Trust Services certificate covers the platform, so the padlock says nothing about whether this page is genuine.
If you typed your Robinhood credentials here, change your password right away from the official app. Turn on or reset app-based two-factor authentication, and sign out all other sessions. Check recent orders, transfers, linked bank accounts and crypto withdrawals, and report anything unfamiliar to Robinhood support straight away. If you reused that password anywhere else, change it there too, and watch for follow-up "support" calls or emails. Defenders should block the hostname, report it to the hosting platform for removal, and warn users to reach Robinhood only through bookmarks or the official app, never through search results.
Last checked
لا تُنسب سمعة Edge-IP إلى هذا المجال.
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 robinhoodcomloginx.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.
robinhoodcomloginx.gitbook.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
غير معروف→redirected
http_redirect
14→16
15→14
13→15
10→13
No threat flag
View source15/89 engine detections
View sourcePage captured
View sourcerobinhoodcomloginx.gitbook.io
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 ↗
robinhoodcomloginx.gitbook.io)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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.