VirusTotal
18 / 92 engine detections
レポートを開く“Robinhood Wallet - Log In”
Robinhoodなりすまし: robinhoodsafe.com — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 18/92 (ChainPatrol, alphaMountain.ai, BitDefender, CyRadar, ESET); Google…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
18 / 92 engine detections
レポートを開く悪意あり
レポートを開くThreat flag recorded
レポートを開くDBL_PHISH
4 community references
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
robinhoodsafe.com is an impersonation phishing page posing as the sign-in screen for Robinhood Wallet. It targets Robinhood customers and self-custody wallet users. The "safe" in the domain name is meant to suggest a security or account-protection page. PhishDestroy first flagged it on 2026-10-11, and as of 2026-10-19 the site was still online and serving its phishing content.
The page carries the title "Robinhood Wallet - Log In" and copies the look of a legitimate Robinhood access screen. Victims usually arrive through links in messages, ads or fake support contacts, often with a warning that their account needs to be secured. The form then asks for login details, verification codes or a wallet recovery phrase. Anything typed there goes straight to the operators. A stolen recovery phrase lets them empty the wallet from their own device, and stolen account credentials let them take over the account.
Eighteen of 92 VirusTotal engines classified the domain as malicious on 2026-10-16. The flagging vendors include crypto-focused ChainPatrol along with alphaMountain.ai, BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet and G-Data. Google Safe Browsing lists it under social engineering, and Spamhaus carries it in its DBL as a phishing domain. MetaMask and SEAL block it alongside PhishDestroy, and four AlienVault OTX threat pulses reference it. That is broad agreement across browser, wallet and reputation sources.
The domain was registered through Name.com, Inc. on 2026-04-24, almost six months before it was detected. A long gap like this is common for domains held in reserve before a campaign starts. The site is hosted on Google LLC infrastructure in the United States. It uses a Let's Encrypt certificate, so the browser padlock appears, but that says nothing about whether the site is legitimate.
If you typed a Robinhood password or code on this page, change the password immediately on the official app or site. Reset two-factor authentication, sign out all sessions and review recent account activity. If you entered a wallet recovery phrase, treat that wallet as compromised and move any remaining funds to a newly created wallet with a fresh phrase. Robinhood will never ask for your recovery phrase. Security teams should block the domain at DNS and the proxy and search mail and chat logs for links to it. Report the site to Robinhood and to the hosting provider to support takedown.
Last checked
ns4hny.name.comLocation describes the IP network.
e7876654ba26d9f786456595e20924504599497b056746a855d8c7acbbe10303Saved 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 robinhoodsafe.com · checked Oct 12, 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.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
No flag recorded→Flag recorded
Threat flag recorded
View source18/92 engine detections
View source4 community references
View sourcerobinhoodsafe.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
robinhoodsafe.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 ↗
robinhoodsafe.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.