sso-robinhoods-m-autth.webflow.io is a Robinhood impersonation page detected by PhishDestroy on 2026-09-11. Risk: critical (92/100). Registrar: Webflow. Status: Content unavailable. Hosting: Cloudflare, Inc. VirusTotal: 14/89 engines flag it. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 14. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
sso-robinhoods-m-autth.webflow.io is a phishing page that impersonated the Robinhood sign-in screen, aimed at people holding stocks or crypto on the platform. The hostname stacks "sso", a pluralized "robinhoods" and a misspelled "autth" to look like a single sign-on address at a glance. PhishDestroy first saw it on 2026-09-11. The site went offline on 2026-09-19 and still served no content when last checked on 2026-10-19.
How the scam works
The page carried the title "Log In | Robinhood® - Sign In to Your Account", so a victim arriving from a phishing email, text or search ad saw what looked like an ordinary Robinhood login prompt. Anything typed into it, such as email, password and often a one-time 2FA code, goes to the operators rather than Robinhood. With those credentials they can log into the real account, sell holdings, move crypto out or change recovery details before the owner notices.
Evidence
On 2026-09-20, 14 of 89 VirusTotal engines flagged the site. They include crypto-focused ChainPatrol alongside BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, Emsisoft, alphaMountain.ai and CyRadar. That mix of general security vendors and a Web3 specialist reaching the same verdict independently strengthens the classification. The domain is also listed on the PhishDestroy, MetaMask and SEAL blocklists, so wallets and browsers using those feeds warn users who try to open it.
Infrastructure
The page was a free subdomain on Webflow's hosted site builder, with Webflow as the registrar. That let the operators publish a polished clone without buying or registering a domain of their own. Traffic was served through a Cloudflare, Inc. address located in Canada, with a Google Trust Services certificate. The padlock in the browser therefore looked normal and did nothing to show that the page was fake. The page was live for about eight days between first detection and going dark.
What to do
If you entered your Robinhood login on this page, change your password from the official app right away and reset 2FA, preferably moving to an authenticator app or security key. Review recent trades, transfers, linked bank accounts and crypto withdrawals, and contact Robinhood support about any activity you do not recognize. Also secure the email account tied to Robinhood, since attackers often target it to block alerts. Defenders should block this hostname and watch for similar Robinhood-themed subdomains on site-builder platforms, reporting new ones to the hosting provider and to Robinhood.
No. PhishDestroy classifies sso-robinhoods-m-autth.webflow.io as a Robinhood impersonation page (risk: critical, 92/100); it was first detected on 2026-09-11. VirusTotal: 14/89 engines flag it. Treat the site as unsafe.
Is sso-robinhoods-m-autth.webflow.io safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on sso-robinhoods-m-autth.webflow.io. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used sso-robinhoods-m-autth.webflow.io?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Registration (base domain)webflow.io · Created May 8, 2013 —Expires May 8, 2028
HTTP Status404 Not Found
Time to First Unavailability8 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 11, 2026
Observed page title
Log In | Robinhood® - Sign In to Your Account
Automated brand references
Robinhood
TLS Certificate
Issued by Google Trust Services / WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.64.151.8
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
journey.ns.cloudflare.com
lamar.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services / WE1
Valid from
2026-07-25 02:21:21
Valid until
2026-10-23 03:21:05
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-18 19:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta4ffdefa8d99689893e2aafdf9588b6f8f2f8ec47698ea534dbfa409dbbde19dCertificate names · 1 SAN
webflow.io
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
4 evidence signal groups linked0 stored notification recordsContent unavailable
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including sso-robinhoods-m-autth.webflow.io)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
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.
(US)
