The domain collab-dapp-nodes.online is a generic phishing site targeting cryptocurrency users. It presents itself as a 'Secure Crypto Wallet Management' platform but is designed to steal credentials or funds through fraudulent means. No specific brand or drainer kit was identified, and the site is currently taken offline, though it previously posed an elevated risk as a cryptocurrency scam.
Technical indicators confirm the malicious nature of collab-dapp-nodes.online. The domain was flagged by 3 of 95 VirusTotal security vendors, including ADMINUSLabs, Gridinsoft, and SOCRadar, and appears on 1 security blocklist (PhishDestroy). Registered through Spaceship, Inc. on November 12, 2025, it resolves to the IP address 216.198.79.1, hosted on Amazon.com, Inc.'s AS16509 in the US. The domain lacks an SSL certificate, and its observed page title was 'COLLAB DAPP NODES - Secure Crypto Wallet Management'. Gridinsoft assigned it a trust score of 0/100, and the site returned an HTTP 429 status before being taken offline. Nameservers are launch1.spaceship.net and launch2.spaceship.net.
Users who interacted with collab-dapp-nodes.online should immediately revoke any token approvals granted to unknown contracts and transfer funds to a new wallet. Enable two-factor authentication on all accounts and monitor for unauthorized transactions. Report the domain to platforms like Google Safe Browsing, PhishTank, or local cybercrime authorities to aid in takedown efforts.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='collab-dapp-nodes.online', port=80): Max retries exceeded with url: / (Caused by NewConnec
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 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:09:13 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-16 10:26:08 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-16 10:26:08 UTC → 2026-09-30 16:14:55 UTC · 2,549.81hmidpoint estimate ≈ 2026-08-08 13:20:31 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.
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 互联网档案馆 — historical evidence archived
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.
(US)
