Analysis of comming.soo.network indicates an active infrastructure employed to harvest cryptocurrency credentials. The domain resolves to the IP address 216.150.1.193, which belongs to Amazon.com, Inc. (AS16509) and is geolocated in the United States. DNS is served by four Amazon Route 53 name servers, three of which are enumerated as ns-155.awsdns-19.com, ns-1096.awsdns-09.org and ns-671.awsdns-19.net; the fourth entry is truncated in the available data. The web server presents a valid Let's Encrypt R12 certificate and forces HTTPS via HSTS. HTTP requests return status code 200 and the page title reads “COMMing SOON NFT Mint”, matching the observed NFT‑Mint phishing kit. The site is built on Vercel and includes analytics from Google Analytics and Fathom, confirming a typical hosting stack for fast‑deployment scam pages.
Threat intelligence classifies the activity as a crypto drainer, specifically leveraging a Wallet Connect abuse kit to trick victims into approving unauthorized token transfers. The domain appears on a single security blocklist and is listed as blocked by PhishDestroy. Gridinsoft assigns a trust score of 0 / 100, reinforcing the malicious rating. VirusTotal has scanned the site with 93 antivirus engines and reported no detections; however, the absence of detections does not constitute validation of safety. Registration was performed through NameCheap, Inc., a registrar frequently used by malicious actors.
Uncertainty remains regarding the full set of malicious payloads hosted behind the page, as only the page title and kit attribution are publicly observable. No additional indicators such as malicious scripts or compromised wallets have been disclosed. Defenders should block the domain at network perimeter, monitor DNS queries for the listed name servers, and flag any outbound connections to the resolved IP.
For the registrable domain soo.network 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:29:05 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-19 22:29:05 UTClast content: 2026-10-19 22:29:05 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.
技术 · 4 identified
V
Vercel
PaaSCDN
Cloud platform for frontend deployment, optimized for Next.js.
H
HSTS
安全
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Google Analytics
Analytics
Web analytics service tracking website traffic and user behavior.
您的加密货币交易所 — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
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.
加密货币诈骗通常是如何运作的？
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
恶意批准 — “连接钱包”的提示会使攻击者获得无限的代币消费权限
猪的屠宰 — 通过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.
(US)
