asteroidog[.]xyz
“Asteroid - The SpaceX Mascot”
Evidence Summary
The domain asteroidog.xyz was registered on July 29, 2026 through NICENIC INTERNATIONAL GROUP CO., LIMITED. It resolves to the IPv4 address 104.21.62.4 and uses Cloudflare authoritative nameservers aliza.ns.cloudflare.com and ken.ns.cloudflare.com. Since its inception the domain has been observed on three independent security blocklists and is actively blocked by PhishDestroy, MetaMask, and SEAL. VirusTotal analysis shows that 13 of 91 scanning engines have flagged the domain as malicious, indicating a consensus of suspicious activity across multiple vendors.
The current risk assessment classifies the campaign as high, with the status listed as active as of the report date, August 03, 2026. Infrastructure analysis confirms the use of a widely shared hosting provider, suggesting the operator may be leveraging Cloudflare's CDN services to obscure the true origin of the payload. No SSL certificate details, HTTP response codes, or page title information have been published, leaving the content of the landing page unverified. Consequently, the exact impersonated brand or visual cues employed in the phishing lure remain unknown.
Defenders are advised to incorporate asteroidog.xyz into domain deny‑lists, enforce DNS‑based blocking, and monitor outbound connections to the associated IP address. Additional scrutiny of traffic patterns to Cloudflare edge nodes may reveal related malicious activity. Continuous re‑evaluation of the domain on VirusTotal and other reputation services is recommended, as further detections could surface with expanded scanning. Organizations should also consider notifying users of the emerging threat to mitigate credential harvesting attempts.
Submitted Evidence Snapshot
- Sent
- Ledger records
- 1
- Case ID
PD-20260803-FC178B- PDF artifact
- PDF evidence
Full evidence text
Policy Violations: “Services may be used only for lawful purposes… fraud, abuse and illegal activity prohibited. Violations may result in immediate suspension.” + dedicated abuse handling and takedown
Applicable Laws: Crimes Ordinance Cap.200 (Fraud), Theft Ordinance Cap.210 §16A (fraud by deception), Personal Data (Privacy) Ordinance Cap.486
Data Coverage
Network Security Intelligence
Threat Response Pipeline
Blocklist coverage
10 monitored external feeds · stored snapshot Aug 12, 2026
7 monitored external feeds No match
Stored outcome evidence
Outcome & takedown attribution
- Outcome
held- Availability
unreachable- Cause
registry_server_hold- Mechanism
server_hold- Confidence
- 95%
- First observation
- Latest observation
Estimated unavailability
Time to unavailability: 0 hEvidence SHA-256 87acff484e10
Detection timeline
-
First recorded
First stored value: Reachable
-
Availability
First stored value: DNS inactive
f93a11f87e4d -
Availability
DNS inactive → Unknown
22c635271d62 -
Domain status
Reachable → Unreachable
-
Availability
Unknown → DNS inactive
a1c9b80332fd -
Availability
DNS inactive → Held
8129111dd53c -
Availability
Held → DNS inactive
f52d526b76a1 -
Availability
DNS inactive → Unknown
3406faad42d5 -
Availability
Unknown → Held
4639d13253e0 -
Availability
Held → Unknown
be5962fb2c36
Show all (11)
-
Availability
Unknown → DNS inactive
6dfe9145995c -
Availability
DNS inactive → Held
386a05afaa8b -
Availability
Held → DNS inactive
641ed81dc4d5 -
Availability
DNS inactive → Unknown
303ac4d76e84 -
Availability
Unknown → Held
ca560b4b72a4 -
Availability
Held → Unknown
d145f1d5d6da -
Availability
Unknown → DNS inactive
d0b7046e8c2f -
Availability
DNS inactive → Held
cec394090603 -
Availability
Held → DNS inactive
ca9ed662b468 -
Availability
DNS inactive → Unknown
ab2ee29a8205 -
Availability
Unknown → Held
87acff484e10
Financial Infrastructure
Addresses extracted from the phishing page.
Wallet addresses
Telegram
Community reports
Reported by 0 community members, first seen Aug 3, 2026
- Unique reported URLs
- 1
Stored Capture
Domain Intelligence
Technical detailsDNS, TLS names and timestamps
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, 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.
Technologies
3 high-confidence technologies identified
VirusTotal Analysis
Archived Evidence
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of asteroidog.xyz · checked Aug 3, 2026
Were You Affected by This Site?
If a wallet, seed phrase, or account was exposed, report the incident immediately. Revoke approvals and move remaining assets to a new wallet created on a trusted device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive
Recommendations & Advice for Victims
An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with asteroidog.xyz — act now.
What should I do immediately?
Urgent
- Revoke token approvals — use revoke.cash to remove access granted to malicious smart contracts
- Move remaining funds to a brand-new wallet. The compromised wallet is no longer safe
- 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
According to the FBI, the most important details are transaction data:
- Cryptocurrency addresses — scammer's wallet (e.g.,
0x5856...35985) - Amount & crypto type — exact amount (e.g., 1.02345 ETH, 0.5 BTC, 500 USDT)
- Transaction ID (hash) — the unique blockchain transaction identifier
- 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
asteroidog.xyz) - 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)
- Chainabuse — flag scam wallets across exchanges & platforms
- Your crypto exchange — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
- 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 crypto scams typically work?
- Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
- Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
- 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
- Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
- AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
- Use a hardware wallet (Ledger, Trezor). Never store large amounts in browser wallets
- Bookmark official sites — never click links from emails, DMs, or ads
- Read every approval — verify permissions before signing. Reject unlimited approvals
- Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
- "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines