VirusTotal
6 / 91 engine detections
打开报告“Teams Calendar Confirmation”
冒充 MetaMask: teams-meeting-calendar-event-schedule.online — 内容不可用. 证据摘要: VirusTotal 6/91 (alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Gridinsoft…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
6 / 91 engine detections
打开报告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
teams-meeting-calendar-event-schedule.online is an impersonation phishing page dressed up as a Microsoft Teams meeting confirmation, titled "Teams Calendar Confirmation". Its long, keyword-stuffed name is built to look like a routine scheduling link to anyone expecting a call. Its listing by MetaMask and SEAL points to crypto holders and teams in the space as a key audience. PhishDestroy first flagged it on 2026-08-18. The site has been offline since 2026-09-11, and its DNS was still inactive at the last check on 2026-10-19.
Fake meeting invites rely on urgency. A victim gets what looks like a calendar link for a scheduled call, lands on a page styled as a Teams confirmation, and is pushed to act before joining. That step is usually signing in with Microsoft or other account credentials, or approving something the attacker asks for. Lures of this kind aimed at crypto users can also push a fake "meeting app" or plugin download. Whatever the victim types or installs gives the operators a way into email, work accounts or wallets.
Six of 91 VirusTotal engines flagged the domain as of 2026-08-30: alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, LevelBlue and SOCRadar. That count is modest, but the vendors are independent of each other. The domain is also blocked by PhishDestroy, MetaMask and SEAL, so wallet users with those protections were warned before loading it. Four AlienVault OTX threat pulses reference it, which shows other researchers tracked it as part of active campaigns.
The domain was registered through NAMECHEAP INC on 2026-08-17, one day before PhishDestroy caught it. That timing fits a disposable domain bought for a single campaign. It resolved to 68.65.122.52 on US hosting. It used a certificate from SSL.com, so it displayed a normal padlock, which shows that an encrypted connection says nothing about who runs a page.
If you entered a Microsoft or other password on this page, change it right away, sign out all active sessions, and check your 2FA methods and mail forwarding rules for anything you did not add. If you downloaded a file presented as a meeting tool, do not run it again. Scan the device or reimage it, then move any crypto from wallets on that machine to a fresh wallet created on a clean device. Treat any unexpected Teams invite on an odd domain as hostile, and confirm meetings through the official app. Defenders should block the domain and its IP and search mail logs for invite links pointing to it.
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.namecheaphosting.comdns2.namecheaphosting.commx1-hosting.jellyfish.systemspriority 5mx2-hosting.jellyfish.systemspriority 10mx3-hosting.jellyfish.systemspriority 20Location describes the IP network.
8dd1de6d1fe37ff4864540ed84423b2444b9c46cde32942434665fa974966cccwww.teams-meeting-calendar-event-schedule.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.teams-meeting-calendar-event-schedule.onlineDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of teams-meeting-calendar-event-schedule.online · checked Aug 18, 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.
teams-meeting-calendar-event-schedule.online
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
可访问→不可用
4→5
0→4
可访问
6/91 engine detections
View source4 community references
View sourceNo threat flag
View sourceteams-meeting-calendar-event-schedule.online
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 ↗
teams-meeting-calendar-event-schedule.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.