Analysis of www-clash.network indicates that the domain was used to harvest Revolut wallet credentials and seed phrases. The site was hosted on Cloudflare’s network (AS13335) and resolved to 104.21.41.113, an IP address located in the United States. Nameserver records list ariadne.ns.cloudflare.com and ignacio.ns.cloudflare.com, confirming the use of Cloudflare’s DNS services. No TLS certificate was observed, meaning the site served traffic over plain HTTP or an unencrypted connection.
The page title returned by the server was “GeorgePlaysClashRoyale | Airdrop”, a classic lure for cryptocurrency airdrop scams. Malware and threat‑intelligence scans identified the presence of an “Airdrop Scam” phishing kit and a Solana‑based wallet drainer, consistent with the reported wallet/seed phishing classification. VirusTotal recorded three detections out of ninety‑five scanners, and the domain appears on one external blocklist, indicating limited but non‑trivial detection by security vendors. PhishDestroy has also added the domain to its blocklist, and the site has been taken offline, reducing immediate exposure.
The registration was performed through Cloudflare, Inc., a common registrar for disposable or quickly‑turned‑over malicious infrastructure. Uncertainty remains around the exact time frame of the campaign, the volume of credentials collected, and whether additional infrastructure (e.g., command‑and‑control servers) was associated with the same IP range. Defenders should continue to monitor Cloudflare‑hosted IPs for similar patterns, enforce strict validation of Revolut communications, and block resolution of www-clash.network at the DNS level. Incident response teams should also correlate any reported Revolut seed‑phrase submissions with this indicator, and threat‑intel platforms should enrich the indicator with the observed kit signatures and the Solana drainer payload fingerprint.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Telegram
https://t.me/clash_tokenStored page reference
IoC extraction recorded 2026-08-02 04:36:00 UTC
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='www-clash.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
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 29, 2025
DOM Analysisanalyzed Mar 24, 2026score 25/1002 brand signals
IoC Extractionscanned Aug 2, 20260 wallet · 1 Telegram IoC
Submitted URLhttps://www-clash.network/
ICANN OVERSIGHT
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:12:05 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-04-08 08:01:55 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-08 08:01:55 UTC → 2026-09-30 16:14:55 UTC · 4,208.22hmidpoint estimate ≈ 2026-07-05 00:08:25 UTC · precision very low · basis bounded
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.
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.
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
www-clash.network detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Feb 23, 2026
Time to First Unavailability
3510 hours elapsed from detection to the first unavailable 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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
4 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
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.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Guaranteed crypto recovery is a fraud indicator. 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
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · www-clash.network
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 matches1
Same favicon hash or the same page title as this host.
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
HTML · IFRAME
Embed This Report
Share this threat intelligence on your website or blog
READ-ONLY
embed.html
<iframesrc="https://phishdestroy.io/embed/domain/www-clash.network"title="PhishDestroy threat report for www-clash.network"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>
(US)
