VirusTotal
8 / 92 engine detections
打开报告“www.join-web-meeting.online”
冒充 MetaMask: join-web-meeting.online — 未验证. 证据摘要: VirusTotal 8/92 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, G-Data); 2 external blocklist…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
8 / 92 engine detections
打开报告Suspicious
打开报告3 community references
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
join-web-meeting.online is an impersonation phishing page that poses as a generic online meeting link. Its name is built to look like an invite to a video call. Wallet-security blocklists flag it, which points to crypto users as the intended audience. PhishDestroy first caught it on 2026-10-07. As of 2026-10-19 the site was still listed as alive, but its DNS was inactive, so the phishing content was no longer resolving.
Fake meeting links are a common lure against people in crypto. A supposed investor, recruiter or project partner arranges a call and sends a join link like this one. The page title shows nothing more than the domain itself, so the lure depends on the address looking like a routine meeting invite. Schemes of this type typically claim the call needs a client update or a wallet check before you can join. That pushes the victim to install malicious software or connect a wallet, either of which can hand over credentials, seed phrases or funds.
On 2026-10-07, eight of 92 VirusTotal engines flagged the domain. The vendors were alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, G-Data, Gridinsoft, Kaspersky and VIPRE. That count is modest, but these are independent vendors and they agree. The domain also appears on the MetaMask and SEAL blocklists alongside PhishDestroy's own, meaning wallet-focused defenders reached the same conclusion. Three AlienVault OTX pulses reference it as well.
The domain was registered on 2026-10-03 through NAMECHEAP INC, just four days before PhishDestroy detected it. That short gap fits a disposable domain stood up for a specific campaign. It sits at 192.64.119.166 on Namecheap, Inc. network space in the US, so registration and hosting run through the same provider.
If you opened this link from a meeting invite, treat the person who sent it as hostile and stop the conversation. If you downloaded anything the page offered, disconnect the device and assume any wallets or browser-saved passwords on it are exposed. Then move your funds to a new wallet created on a clean device. If you connected a wallet or signed anything, revoke the token approvals granted to unfamiliar addresses. Change passwords and 2FA for any accounts you entered. Defenders should block the domain, warn staff and community members about fake meeting invites, and hunt for related domains registered through the same channel.
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.
dns1.registrar-servers.comdns2.registrar-servers.comeforward1.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward3.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location describes the IP network.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→dns_inactive
dns_nxdomain
未知→redirected
http_redirect
可访问
No threat flag
View source3 community references
View source8/92 engine detections
View sourcejoin-web-meeting.online
View sourcePage captured
View source已存储 79 个仿冒域名
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
join-web-meeting.online
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 ↗
join-web-meeting.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.