Skip to security report
Analytics Dashboard
Domain security report
launcher.robinhoodnascat.fun favicon

launcher.robinhoodnascat.fun

“NASCAT Launcher — launch a token on Robinhood Chain”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 11/91 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: Robinhood
Sep 15, 2026 Robinhood 1 Report Sent
API
Registrar
Name.com
Resolved IP
162.243.1.51
Registered
Jul 10, 2026
3 sources
The capture source is temporarily unavailable.
1 / 3
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 11. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
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.

Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-20260915-FEB965
Current status
HTTP 200 at latest stored check

Additional indicators at a glance

Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
11 det.
URLScan
URLScan
Report ↗
ScamAdviser
Scamadviser
80/100Likely Safe
TLS Certificate
Within stored validity dates
Let's Encrypt / YE1 · Hostname coverage not recorded
Age
3 mo
Observed status
Last known active 200
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

10 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

11 / 91

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

Public blocklists

2 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLQuery

checked — no detections recorded

Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Scamadviser

80/100

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
VirusTotal
11/91
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

launcher.robinhoodnascat.fun returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The same record set includes a page performance score of 91 from a PageSpeed check dated 2026-09-15.

Recorded Evidence

The domain was first observed on 2026-09-15, the same date as the SSL scan that identified Let's Encrypt / YE1 as the certificate issuer. The HTTP check on 2026-10-01 recorded IP address 162.243.1.51, located in the US and associated with Digital Ocean. VirusTotal, checked on 2026-09-25, reported 11 detections across 91 scanners. The external blocklist check on 2026-10-01 listed the domain on MetaMask and SEAL, with an external blocklist count of 2. PhishDestroy's internal listing is recorded as true.

Interpretation

The MetaMask and SEAL blocklist entries and the PhishDestroy internal listing were recorded on 2026-10-01, while the VirusTotal scan is dated 2026-09-25 and the SSL and PageSpeed observations are from 2026-09-15. Because these sources were checked on different dates, their findings describe separate points in time rather than a single synchronized snapshot. The earlier SSL and PageSpeed records and the later blocklist and VirusTotal records therefore cannot be directly compared as if they were collected together.

Recommended Actions

Reviewers should retain the dated records for launcher.robinhoodnascat.fun, including the 2026-10-01 HTTP check, the 2026-09-25 VirusTotal result and the 2026-09-15 SSL scan, so later observations can be compared against them. Any subsequent check of launcher.robinhoodnascat.fun should be logged with its own date and source. During review, avoid submitting passwords, payment details or other sensitive information to the domain until the recorded concerns are resolved.

Data coverage & collection

22 · datasets with records / 9 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
11 / 91 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
Stored source record
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
2 · external matches
Cloudflare Radar
cleanCollection time not recorded
Scamadviser
80/100 · provider trust scoreCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
Name.com, Inc.Collection time not recorded
Network & DNS
162.243.1.51 · 2 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / YE1
Page captures
3 · retained captures
Page analysis
16 · automated brand labels
Observed indicators
21 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
91/100 · mobile performance
Response records
1 · outgoing report records
Availability history
28 · stored state changes
Source observation history
2 · stored source events
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 9

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • HTML archives
  • Site configuration files
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
  • Chainabuse records
Download the dated observations and supporting metadata.
Extracted from stored page analysis

Observed indicators

20 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

ETH
0x03DfbBE0AC4E7bCDaFd08eD41A400326B77D8c80Format validated · Domain analysis
ETH
0x05a3d1Cd21d0C88145E82600E62e7E496e0F222BFormat validated · Domain analysis
ETH
0x05b37Fb53A299a1b874A619e1c4C404D52C36F4CFormat validated · Domain analysis
ETH
0x0Bd7D308f8E1639FAb988df18A8011f41EAcAD73Format validated · Domain analysis
ETH
0x0b5fb4031cae9163db10B169Ee72685F0EdC8545Format validated · Domain analysis
ETH
0x0f17206447090e464C277571124dD2688E48AEA9Format validated · Domain analysis
ETH
0x116F00968269B7bfbaD4109cE591d6E74c0601d4Format validated · Domain analysis
ETH
0x117cc2133c37B721F49dE2A7a74833232B3B4C0CFormat validated · Domain analysis
ETH
0x12e3c047bf9AeCAF9dDC98c05C31BFD1dd043993Format validated · Domain analysis
ETH
0x12f190a9F9d7D37a250758b26824B97CE941bF54Format validated · Domain analysis
ETH
0x156E175DD063a8cE274C50654eF40e0032b3fbcFFormat validated · Domain analysis
ETH
0x1AF6446f07eb1d97c546AFC8c9544cBDF3AD5137Format validated · Domain analysis
ETH
0x1Cdad396DB64BDa184d5182A97Dd9B3C62100b7DFormat validated · Domain analysis
ETH
0x1D11f0496982706C5e14A514D4E79F2e6BdE4516Format validated · Domain analysis
ETH
0x1b0E319c6A659F002271B69dB8A7df2F911c153EFormat validated · Domain analysis
ETH
0x232B8ed6377BE97813853B0Ac104c4Cda8378d1BFormat validated · Domain analysis
ETH
0x237c16D66590F67B886d978ACD362EAeaD8B18c7Format validated · Domain analysis
ETH
0x28bABD556b60E53663B8615036479a29c2CDd1BfFormat validated · Domain analysis
ETH
0x2D3186185956F332F26C63A9823c731d362340b8Format validated · Domain analysis
ETH
0x2D427692E928fa156ec22acfaBaFA0447C5805B7Format validated · Domain analysis
Telegram
https://t.me/NascatRHCStored page reference

IoC extraction recorded 2026-09-16 04:00:14 UTC

Blocklist records

2 · external source matches

Public Blocklist Status

Domain, network & archive

Name.com, Inc. · 162.243.1.51 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
Observed indicators20 wallet · 1 Telegram — full values ↗
IP Reputation abuse score 0/100 0 reports checked Oct 15, 2026
Registrar (base domain) Name.com (Unknown)
Abuse contactabuse@digitalocean.com, abuse@name.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for robinhoodnascat.fun →
Registration (base domain)robinhoodnascat.fun · Created Jul 10, 2026 (98d) — Expires Jul 10, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 15, 2026
DOM Analysisanalyzed Sep 15, 2026score 95/10016 brand signals
IoC Extractionscanned Sep 16, 202620 wallet · 2 Telegram IoCs
Submitted URLhttp://launcher.robinhoodnascat.fun/
Favicon Hash
Case ID
ICANN OVERSIGHT Registration: robinhoodnascat.fun

Accreditation and RAA context
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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
162.243.1.51
Network ASN
AS14061
Organization
Digital Ocean
Observed location
Secaucus, US
Server header
nginx/1.24.0 (Ubuntu)
Nameservers 2
  • ns1.vercel-dns.com
  • ns2.vercel-dns.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-09-15 12:12:02
Valid until
2026-12-14 12:12:01
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-11 01:03:39 UTC
Collection source
PhishDestroy collector
Certificate fingerprint1fae03874c13707ee2fc3c91d6d641291b2611eb24b3c09c714390b9501afe50

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 162.243.1.51rapiddns.io

Latest Classified Outcome 2026-10-16 22:27:56 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-16 22:27:56 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-16 10:27:36 UTC last content: 2026-10-16 10:27:36 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.
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

11 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 9 detections
ChainPatrol
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
SOCRadar
VIPRE

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of launcher.robinhoodnascat.fun · checked Sep 15, 2026

91
Good
Performance
FCP
1.05s
First Contentful Paint
LCP
1.05s
Largest Contentful Paint
CLS
0.194
Cumulative Layout Shift
TBT
32ms
Total Blocking Time
SI
2.35s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
nginx/1.24.0 (Ubuntu)

Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.24.0 (Ubuntu)

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Cloaked / Filtered

Timeline & response

1 · outbound report records

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. VirusTotal Detections Update 2026-09-16 17:25:02 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 6 to 9. Added scanner alerts: CRDF, Gridinsoft, alphaMountain.ai.
  2. Threat First Observed 2026-09-15 14:36:18 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 162.243.1.51.
Stored observation history30

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 25
  1. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  17. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  18. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  19. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  20. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  21. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  22. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  23. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  24. VirusTotal · Detection count

    6→9

  25. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
launcher.robinhoodnascat.fun detected and queued for full analysis
Sep 15, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Oct 16, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Sep 15, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Sep 23, 2026
VirusTotal
11/91 recorded on VirusTotal
Sep 25, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 17, 2026
Brand Impersonation
Impersonation of Robinhood
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Sep 15, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
VT Detection +3
+3 new detections (6 → 9): CRDF, Gridinsoft, alphaMountain.ai
Sep 16, 2026
Sent Report Recorded
Stored outgoing record associated with registrar Name.com, Inc., 2 abuse contacts
abuse@digitalocean.comabuse@name.com
Sep 15, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Sep 15, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 11 det. ChainPatrol URLQuery Report stored Scamadviser 80 trust SSL Labs Hostname coverage not recorded CF Radar Open report WOT Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260915-FEB965 Recipient: abuse@digitalocean.com
Page title stored with report: NASCAT Launcher — launch a token on Robinhood Chain
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider 
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Last known active
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.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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 launcher.robinhoodnascat.fun)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: launcher.robinhoodnascat.fun

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “NASCAT Launcher — launch a token on Robinhood Chain”. Apparent target: Robinhood.

VirusTotal detections for launcher.robinhoodnascat.fun: 11 (2026-09-25 02:07:16 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/launcher.robinhoodnascat.fun"
  title="PhishDestroy threat report for launcher.robinhoodnascat.fun"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>