ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@digitalocean.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
launcher.robinhoodnascat.fun is a phishing page that uses the Robinhood name to pass itself off as "NASCAT Launcher," a tool for launching tokens on Robinhood Chain. It targets crypto users and would-be token creators who trust the Robinhood brand and want early access to a new chain. PhishDestroy first flagged it on 2026-09-15. As of 2026-10-19 the site was still online and serving its content, so it remains a live risk.
How the scam works
The page title, "NASCAT Launcher — launch a token on Robinhood Chain," frames the site as an official-looking launchpad tied to Robinhood. Fake launchpads like this usually ask visitors to connect a wallet and then sign transactions or pay a "launch" or "listing" fee. Those requests can hand over funds or grant token spending permissions to the operators. Anything sent or approved goes to the scammers, not to Robinhood, and on-chain transfers generally cannot be reversed.
Evidence
On 2026-09-25, 11 of 91 VirusTotal engines flagged the domain. They included the crypto-focused ChainPatrol alongside BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, CRDF and alphaMountain.ai. That is a minority of engines, but the backing goes beyond VirusTotal. MetaMask and SEAL, both centred on Web3 threats, list the domain, as does PhishDestroy. Spamhaus also lists it in its Domain Block List as DBL_PHISH, which means mail and network filters that use Spamhaus treat it as phishing.
Infrastructure
The domain was registered through Name.com, Inc. on 2026-07-10, about two months before PhishDestroy detected it. That gap suggests it was set up ahead of time rather than thrown together the same day. The site runs on DigitalOcean cloud hosting in the United States. The "launcher" subdomain on a brand-themed .fun domain mimics the naming of real token launch tools.
What to do
Do not connect a wallet or pay any launch, listing or gas fee on this site. If you already connected, use a token approval checker to revoke any permissions granted during the visit. Move remaining assets to a fresh wallet if you signed anything you did not understand. Never type a seed phrase into a site like this; if you did, treat that wallet as compromised and empty it right away. Defenders should block the domain at DNS and the mail gateway, and report sightings to the hosting provider and registrar.
DOM Analysisanalyzed 2026年9月15日score 95/10016 brand signals
IoC Extractionscanned 2026年9月16日20 wallet · 2 Telegram IoCs
Submitted URLhttp://launcher.robinhoodnascat.fun/
Favicon Hash
案件 ID
ICANN OVERSIGHTRegistration: robinhoodnascat.fun
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
For the registrable domain robinhoodnascat.fun behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-19 22:30:54 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-19 22:35:34 UTClast content: 2026-10-19 22:30:54 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
技术 · 2 identified
U
Ubuntu
Operating systems
Ubuntu is a free and open-source operating system on Linux for the enterprise server, desktop, cloud, and IoT.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
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?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
