VirusTotal
11 / 91 engine detections
打开报告“My Blog – My WordPress Blog”
Web3Nodes.online is a fraudulent crypto platform luring users with fake 'nodes' promotions to steal wallet private keys.
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
11 / 91 engine detections
打开报告1/100
打开报告Threat flag recorded
打开报告checked — no detections recorded
打开报告checked — no match recorded
23 community references
打开报告provider verdict: clean
打开报告12 已检查 — 未发现拦截
No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy identifies web3nodes.online as an active cryptocurrency phishing domain posing as a Web3 infrastructure service to harvest wallet credentials and private keys. The threat involves fake 'node' promotions and fraudulent wallet connection requests designed to deceive users into surrendering sensitive blockchain access. As of the current investigation, the domain remains unflagged by automated security systems despite active operations targeting crypto investors. This domain was flagged by 8 of 95 VirusTotal security vendors, operates through IP address 67.223.118.134, and was registered through NAMECHEAP INC on April 13, 2026. The combination of zero detections, recently created domain age, and association with cryptocurrency scams indicates a high-risk threat landscape requiring immediate user awareness and preventive action. The absence of blocklist entries suggests either evasion tactics or insufficient threat intelligence coverage in mainstream security databases. Current status shows active deployment with SSL certification from Sectigo Limited, indicating the operators maintain basic security protocols to appear legitimate. PhishDestroy recommends users immediately block the domain web3nodes.online at network and DNS levels, avoid any cryptocurrency-related interactions with this service, and report wallet addresses or transaction hashes to relevant blockchain security communities. Users who may have engaged with this site should revoke all connected wallet permissions immediately and transfer remaining assets to a cold storage solution. Enhanced monitoring of outgoing connections to 67.223.118.134 is advised as this IP may host additional phishing infrastructure.
Last checked
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.
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.
dns2.namecheaphosting.commx1-hosting.jellyfish.systemspriority 5mx2-hosting.jellyfish.systemspriority 10mx3-hosting.jellyfish.systemspriority 20Location describes the IP network.
2bb5d8d5ae9459bcc7a55648f976bd9ee300748f804c7f4fa7b0a95471d525d9www.web3nodes.onlineSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.web3nodes.onlineDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of web3nodes.online · checked Apr 15, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy; server=LiteSpeed
web3nodes.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
No flag recorded→Flag recorded
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
Threat flag recorded
View source23 community references
View source11/91 engine detections
View sourceweb3nodes.online
View source由 1 名社区成员报告;首次发现于 2026年4月15日
Listed domains receive at least one abuse report; this entry has no retained notification history.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
web3nodes.online)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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.