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.
Detection-evasion analysis
Cloaking suspected: scanner and visitor titles differ
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.
Registration (base domain)soo.network · Created Jun 24, 2024 —Expires Jun 24, 2027
HTTP Status403 Forbidden
Technical detailsProvenance & timestamps
First DetectedDec 24, 2025
DOM Analysisanalyzed Mar 11, 2026score 91/100
Submitted URLhttps://comming.soo.network/
Favicon Hash
ICANN OVERSIGHTRegistration: soo.network
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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 observationLive contentOrdinary HTTP content served90%2026-10-12 10:22:06 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-12 10:22:06 UTClast content: 2026-10-12 10:22:06 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 · 4 identified
V
Vercel
PaaSCDN
Cloud platform for frontend deployment, optimized for Next.js.
H
HSTS
Security
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Google Analytics
Analytics
Web analytics service tracking website traffic and user behavior.
Google PageSpeed Insights — mobile performance audit of comming.soo.network· checked Mar 2, 2026
44
Poor
Performance
FCP
7.76s
First Contentful Paint
LCP
10.86s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
526ms
Total Blocking Time
SI
7.76s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
VirusTotal Detections Update2026-03-05 03:06:30 UTC
VirusTotal scanner detections updated from 0 to 0.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
comming.soo.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 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+
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 recordedReachable · access restricted
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 · comming.soo.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.
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/comming.soo.network"title="PhishDestroy threat report for comming.soo.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)
