VirusTotal
3 / 89 engine detections
打开报告“WEB3.AI”
冒充 MetaMask: websxe.com — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 3/89 (alphaMountain.ai, Gridinsoft, Kaspersky); Spamhaus DBL_PHISH; 2 external blocklist…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
3 / 89 engine detections
打开报告DBL_PHISH
4 community references
打开报告provider verdict: clean
打开报告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
websxe.com presents itself as WEB3.AI. The page title carries that name, while the domain itself has nothing to do with it. PhishDestroy classifies it as an impersonation phishing page aimed at crypto users, and first flagged it on 2026-09-15. As of 2026-10-19 the site was still online and serving its content, more than a month after it was first reported.
Impersonation pages like this copy the look and name of a crypto project so visitors believe they are on the official site. Once that trust is in place, the page asks for something valuable, typically a wallet connection, a signature, a recovery phrase or login details, in exchange for a promised feature, reward or account access. Anything handed over goes straight to the operators. With wallet access or a seed phrase, they can move funds out with no way to reverse the transfers. The WEB3.AI branding is the bait, and the unrelated domain name is the clearest sign that this is not the real project.
On 2026-09-15, only 3 of 89 VirusTotal engines flagged the site: alphaMountain.ai, Gridinsoft and Kaspersky. That count is low, so a clean scan from most tools does not mean the site is safe. Stronger confirmation comes from the crypto-specific blocklists. The site is listed by MetaMask and SEAL alongside PhishDestroy, and Spamhaus carries it in its DBL as a phishing domain. It also appears in 4 AlienVault OTX threat pulses, which means other researchers have tracked it independently.
The domain was registered on 2026-07-03 through Cloudflare, Inc., about ten weeks before PhishDestroy detected it. That gap suggests it was set up in advance rather than spun up the same day. Traffic passes through Cloudflare's network, with the visible IP geolocating to Canada, so the origin server stays hidden behind the proxy. The certificate is a standard automated one from Google Trust Services. The padlock icon only shows that the connection is encrypted and says nothing about who runs the site.
If you connected a wallet to websxe.com or signed anything there, revoke the token approvals granted from that wallet. Then move the remaining assets to a new wallet you control. If you typed in a recovery phrase, treat that wallet as compromised and abandon it entirely. If you entered a password, change it wherever it is reused and turn on two-factor authentication. Security teams should block the domain at DNS and proxy level, and add it to filtering for messages that mention WEB3.AI.
Last checked
Edge-IP 声誉不属于此域。
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
70ebd0c6605a307264b739379330f7380cacceda06289242331abd852941fe55websxe.com*.websxe.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of websxe.com · checked Sep 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.
websxe.com
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
未知→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
未知→live_content
content_served
可访问
4 community references
View sourceNo threat flag
View source3/89 engine detections
View sourcewebsxe.com
View sourcePage captured
View source已存储 79 个仿冒域名
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 ↗
websxe.com)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.