Security researchers at Kaspersky have uncovered an ongoing malware campaign exploiting the trust inherent in WhatsApp communications. Threat actors are using compromised WhatsApp accounts to send malicious VBScript attachments to victims' contacts. The scripts are disguised as legitimate documents to trick users into executing them. The ultimate goal of the attack is to install a legitimate Remote Monitoring and Management (RMM) tool, ManageEngine Endpoint Central, on the victim's computer. This "living off the land" technique provides the attackers with persistent, legitimate-looking remote access for data theft, surveillance, or deploying further malware. The campaign is active across at least 11 countries, with a significant concentration of victims in Malaysia.
The attack chain leverages social engineering and abuses a legitimate enterprise tool:
.vbs) file to multiple contacts. The file is given a deceptive name (e.g., invoice.vbs, report.vbs) to appear as a business document.This campaign relies on a combination of social engineering and the abuse of legitimate software.
T1566.001 - Spearphishing Attachment): The attack is a form of spearphishing, using the compromised account of a trusted contact to deliver the malicious payload.T1204.002 - Malicious File): The success of the attack hinges on the user being tricked into executing the .vbs file.T1059.005 - Visual Basic): The attackers use VBScript, a native Windows scripting language, to initiate the infection. This avoids the need to drop an executable file initially, which might be flagged by antivirus software.T1105 - Ingress Tool Transfer): The VBScript dropper downloads the main RMM installer from an external source.T1219 - Remote Access Software): This is the core of the attack. By using a legitimate, signed RMM tool like ManageEngine Endpoint Central, the attackers' activity can blend in with normal administrative traffic, making it difficult for security tools to detect.Once the RMM tool is installed, the attackers have near-total control over the victim's computer. They can silently monitor user activity, access files, steal credentials, install further malware (like ransomware or spyware), and use the compromised machine as a pivot point to attack other systems on the same network. For a corporate user, this could lead to a full-scale enterprise breach originating from a single employee's compromised WhatsApp account. The use of a legitimate RMM tool complicates detection and attribution, as the network traffic generated by the tool is encrypted and appears legitimate to firewalls and other network security appliances.
No specific file hashes, domains, or IP addresses were provided in the source articles.
Security teams can hunt for signs of this activity within their environments. The following patterns could indicate related activity:
wscript.exe or cscript.exepowershell.exe or making network connections.*.vbsManageEngine Endpoint Central AgentUEMS.exe, dcagent.exe) on systems where it is not an officially deployed tool..vbs files by default, or at least to prompt users with a stern warning before they are run. This aligns with D3FEND's D3-EDL - Executable Denylisting.wscript.exe or cscript.exe initiates network connections or downloads executable files. Use D3FEND's D3-PA - Process Analysis to detect these suspicious process chains.M1017 - User Training).M1042 - Disable or Remove Feature or Program).New details on VBScript obfuscation and multi-stage infection tactics revealed for the WhatsApp malware campaign.
Educate users to be highly suspicious of unsolicited attachments, even from trusted contacts, and to verify them via another channel.
Use application control or Group Policy to block or restrict the execution of script files like .vbs from user-writable locations.
Maintain an allowlist of approved software and alert on or block the installation of any unapproved applications, especially RMM tools.
Use EDR to monitor for suspicious process chains, such as the Windows Script Host downloading and running executables.
A primary defense against this WhatsApp campaign is to use Executable Denylisting to prevent the initial execution of the VBScript dropper. Most corporate users have no legitimate business need to run .vbs files. Organizations should configure application control policies (like AppLocker on Windows) to block the execution of files with .vbs, .vbe, and .js extensions from all locations, especially user-writable directories like 'Downloads' and 'AppData'. If certain legacy applications require VBScript, exceptions can be made for specific, signed scripts located in protected directories. This simple, policy-based control breaks the attack chain at the very first step (User Execution), rendering the social engineering attempt inert. It is a highly effective, low-cost mitigation for a wide range of script-based malware.
For environments where blocking scripts entirely is not feasible, Process Analysis via an EDR tool is the next line of defense. A detection rule should be created to flag the specific behavior of this attack: the Windows Script Host (wscript.exe or cscript.exe) spawning a child process (like powershell.exe or msiexec.exe) that makes an outbound network connection to download a file. This is anomalous behavior. The EDR should be able to correlate the initial script execution with the subsequent download and installation of the ManageEngine RMM tool. By creating a behavioral signature for this process tree, security teams can detect the attack even if the attackers change the script's content or the download URL. This focuses on the 'how' of the attack, not just the 'what', making it a more resilient detection strategy.
Organizations with mature security operations can leverage Dynamic Analysis in a sandbox environment to automatically vet attachments. When a file like the malicious .vbs script is downloaded via WhatsApp Web, an integrated security solution could automatically forward it to a sandbox for detonation before the user can access it. The sandbox would execute the script and observe its behavior: the network connections it makes, the files it drops, and the processes it spawns. Upon observing the script downloading and installing the ManageEngine RMM tool, the sandbox would flag the original file as malicious, quarantine it, and generate an alert. This automates the detection process, removing the fallible human element and providing a verdict on suspicious files in near real-time.
Kaspersky reports on the active WhatsApp malware campaign.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.