The update that arrives inside the meeting
The I4C's warning on malicious files in video conferences: Zoom, Teams and Meet each update through the app you already have, and a first install belongs on the platform's own site - an installer handed to you in a meeting is a reason to check independently, not to click. The fake update play, the real update routes, and what to do if you already ran the file.
You are about to join the meeting, and something tells you that you cannot - not yet. First download this update, install this component, open this document. India's cyber-crime coordination centre, the I4C, named the pattern in its advisories listing of 2 February 2022: malicious executable files distributed during video conferences, aimed at the government offices, educational institutions and businesses that moved their meetings online. The file that arrives inside the meeting is the payload, and the meeting is only the delivery room.
The play, as the I4C describes it
The advisory's modus operandi runs in steps. The criminals get inside virtual meetings and classes by compromising email addresses belonging to the target organizations or participants - so the invitation or the in-meeting message can come from an address you recognize. Once inside, they drop executable files disguised as a related, important document, counting on the meeting's own momentum: everyone is waiting, the file seems to belong to the agenda. Opened, the file installs malware or a trojan that gives the criminals remote access to the device - and the advisory notes the quieter outcome too: meetings recorded, and the data shared inside them, read by someone who was never announced. Its suggestions for meeting hosts are worth taking seriously: password-based entry, waiting rooms, keeping track of who joins, and never posting meeting details on public platforms.
The 2026 shape of the same play
Microsoft's Defender research team described phishing campaigns observed in February 2026 that used meeting-invitation lures: emails impersonating meeting invites pushed downloads with names like msteams.exe, zoomworkspace.clientsetup.exe and invite.exe. The files carried a valid Extended Validation digital signature issued to a company called TrustConnect Software PTY LTD, and once run they installed remote monitoring and management tools - ScreenConnect, Tactical RMM, Mesh Agent - giving the attackers persistent access and a way to move deeper into the organization. Microsoft's own conclusion: familiar branding and trusted digital signatures can be abused to bypass suspicion. Malwarebytes, in the same month, documented a convincing fake Zoom waiting room whose "update" silently installed a legitimate commercial monitoring product, abused for unauthorized surveillance; when the first domain was suspended after community reporting, a parallel site re-ran the identical playbook dressed as Google Meet, complete with a fake Microsoft Store page and a fabricated publisher name. A valid signature, a copied logo and a professional page are all surface: this year's documented campaigns ran genuinely signed malware and abused a legitimate signed product behind imitated branding.
The real routes, platform by platform
Zoom's own update guide says the desktop app updates from inside itself: sign in, click your profile picture, and Check for Updates - or download the newest version from Zoom's Download Center, and on phones from the app stores. (If your work device was set up by an IT team with the MSI installer, updates come through them.) Microsoft's Teams page says Teams auto-updates when the app is idle, or shows an update banner at the top of the Teams window you can click yourself; the web app, it notes, is always updated. Google's Meet help says the optional desktop app is a Progressive Web App installed from the address bar on meet.google.com itself, and it updates automatically with Chrome - the meeting itself runs in the browser. None of these documented routes begins with a file handed to you inside a meeting. A first install is a different case from an update, and it can legitimately start on the platform's own pages - Zoom's join flow on zoom.us can offer the desktop app to someone who does not have it yet. What the legitimate routes share is that they stay on the platform's own site and move at your pace; what they do not do is hand you a file inside a meeting chat or rush you through a lookalike page while the meeting waits. So when a meeting seems to demand software, treat the file as a suspect rather than convicting it on sight: leave it unopened, open the platform's official app or site yourself, and on a work device check with your IT team.
The tells that need no technical eye
An installer that arrives by invitation - in a meeting chat, an email thread, a message about the meeting - is the first tell; the documented routes do not work that way. An executable dressed as a document is the second: the I4C's advisory describes files disguised as related important documents, so a "minutes.pdf" that is actually an .exe, or a "join" page whose only button downloads a program. A countdown helps the play, not you: the meeting is starting, everyone is waiting, install quickly. And remember what the surface is worth: a valid digital signature is not proof that software is safe or that it belongs to the claimed vendor - this year's documented campaigns used genuinely signed malware and a legitimate signed product pushed by impostor pages. None of these tells proves who sent the file, and an installation-first join page is not automatically a trap - that is not the test. They are reasons to stop, and to switch to the route you control: the platform's official app or site, opened by you, or your IT team's word on a work device.
If you already ran the file
Containment comes first, and speed matters more than composure. Disconnect the device from the network - Wi-Fi off, cable out - to cut any remote session. On a work device, tell your IT team immediately and say exactly what you ran: the documented campaigns aim for persistent access and lateral movement, and your report protects colleagues, not just you. Then clean up with trusted guidance: scan the device with a reputable security tool and remove what it finds, change your important passwords from a different, clean device, and watch your bank statements. If money moved, call 1930 - the national financial-fraud helpline - immediately and inform your bank. Report the incident itself at cybercrime.gov.in, as the I4C's advisory asks; keep the installer file name, the invite, the messages and the page address, because that is the evidence investigators can use. No removal step is a guarantee on its own, so get qualified technical help if you are unsure - and treat the episode as a reason to review what the device can reach.
The shape worth remembering
A meeting is a room you were invited into, and software that arrives by invitation inherits that room's urgency. Zoom, Teams and Meet each maintain themselves through the app you already have or their own site - that is the documented route, and it never requires a stranger's file. When a meeting hands you software, the meeting can wait: open the app yourself, and let the file stay unopened.
Sources: the national cybercrime portal's advisories page - official listing of the I4C advisory "Malicious Executable Files distributed during Video Conferences (VCs)" (2 February 2022); the advisory's full text, hosted by Haryana Police - the modus operandi and the suggestions; Microsoft Security Blog, 3 March 2026 - the February 2026 campaigns: meeting-invitation lures, EV-signed msteams.exe and zoomworkspace.clientsetup.exe, and the RMM tools they installed; Malwarebytes, 26 February 2026 - the fake Zoom waiting-room update installing monitoring software, and the Google Meet variant with the fake Microsoft Store page; Zoom's update guide, Microsoft's Teams update page and Google's Meet desktop app help - the real update routes. Fraud reporting: 1930 and cybercrime.gov.in.
Frequently asked questions
The installer was digitally signed and used the platform's branding. Isn't that proof it is real?
No - the signature itself may be perfectly real and still prove nothing about safety. Microsoft described malware carrying a valid Extended Validation certificate issued to a front company, and Malwarebytes described a legitimate, genuinely signed product installed by impostor Zoom and Google Meet pages. A signature shows a certificate was issued to someone; it does not show the software is safe, or that it comes from the platform it imitates. The check is the route, not the wrapping: updates for Zoom, Teams and Meet arrive through the app you already have, so close the page and update from there - and on a work device, ask your IT team.
The invite came from a colleague's real email address. How can it be dangerous?
The I4C's advisory describes exactly this entry point: criminals compromise email addresses belonging to organizations and participants to get inside meetings and make their files look expected. A familiar address proves the account sent the message; it does not prove your colleague was operating it. If a file or link arrives unexpectedly, confirm through a channel you choose - call or message the person directly before opening anything.
Do I ever need to install something to join a meeting?
Sometimes, once, and from a route you choose: Zoom's desktop app comes from Zoom's own Download Center or the app stores, Google's optional Meet desktop app installs from the address bar on meet.google.com itself, and Teams also runs in the browser. A first install can legitimately start on the platform's own pages - Zoom's join flow can offer the desktop app, and its downloads come from Zoom's own Download Center or the app stores. The difference worth holding: a legitimate first install happens on the platform's own site, at your pace, while the play hands you a file inside the meeting or on a lookalike page with the meeting already waiting. When you cannot tell which you are looking at, close the page and open the platform's official site yourself - or ask your IT team on a work device.