Microsoft is warning of a new social engineering campaign targeting users of the WhatsApp for Windows desktop application. The attack does not exploit a software vulnerability but instead relies on tricking users into executing a malicious Visual Basic Script (.vbs) file sent as an attachment. The script initiates a multi-stage infection using "living off the land" (LOTL) techniques to evade detection. The ultimate goal is to install remote access software, granting the attacker persistent control over the victim's computer. This campaign highlights the enduring threat of social engineering and the need for user vigilance, even on encrypted messaging platforms.
The attack begins with a classic social engineering lure. The attacker sends a message via WhatsApp containing a malicious attachment, likely disguised as a document or image, which is actually a .vbs file. The infection chain proceeds as follows once the user is tricked into opening the file:
.vbs file, executing the script via the Windows Script Host (wscript.exe).bitsadmin or certutil) into a hidden folder and renames them to evade simple detection rules.This campaign is a prime example of defense evasion using LOTL TTPs:
T1566.001 - Spearphishing Attachment: The initial delivery mechanism is a malicious attachment sent via a messaging service.T1204.002 - User Execution: Malicious File: The attack is entirely dependent on the user executing the initial .vbs file.T1059.005 - Command and Scripting Interpreter: Visual Basic: The initial payload is a VBScript file.T1218 - System Binary Proxy Execution: The use of renamed, legitimate Windows binaries to download malware is a classic LOTL technique.T1548.002 - Abuse Elevation Control Mechanism: Bypass User Account Control: The malware modifies UAC settings to operate with fewer restrictions and avoid alerting the user.T1547.001 - Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder: This is the method used to achieve persistence on the compromised machine.While this campaign appears to target individual users rather than large enterprises, a successful compromise can have severe consequences:
Detection:
wscript.exe with a .vbs file argument, especially when originating from a chat application's download folder. This can be achieved through D3-PA: Process Analysis.HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA) and autostart locations.Response:
M1017 - User Training): The most critical defense is user awareness. Train users to never open unexpected attachments, especially script files (.vbs, .js, .ps1), even if they appear to come from a known contact..vbs files from the Windows Script Host to a simple text editor like Notepad.exe. This prevents accidental execution via double-clicking. This is a form of D3-ACH: Application Configuration Hardening.M1038 - Execution Prevention): Use application control policies to block the execution of scripting engines like wscript.exe and cscript.exe for most users.document.pdf.vbs is actually a script, not a PDF.The primary defense is training users to be suspicious of any unexpected attachments, especially script files.
Change the default file handler for .vbs files to a text editor to prevent accidental execution.
Mapped D3FEND Techniques:
Use application control to block scripting hosts like wscript.exe for all non-administrative users.
Mapped D3FEND Techniques:
A highly effective and simple countermeasure against this specific VBScript-based attack is to change the default file association for .vbs files on all Windows endpoints. By default, double-clicking a .vbs file executes it with the Windows Script Host (wscript.exe). By using Group Policy or an endpoint management tool, change this default behavior to open .vbs files with Notepad.exe instead. This action completely neutralizes the initial execution vector, as a user double-clicking the malicious attachment would simply see its source code in a text editor rather than running it. This prevents the infection chain from ever starting and requires no sophisticated detection capabilities, directly hardening the OS against this common social engineering tactic.
Deploy an EDR solution and configure it to monitor for the specific process behaviors used in this attack. Create a high-priority alert for the process chain where WhatsApp.exe spawns wscript.exe. Additionally, monitor for legitimate Windows binaries like bitsadmin.exe or certutil.exe being executed from unusual locations (e.g., C:\Users\<user>\AppData\Local\Temp\) or under a different name. Baselining normal system activity will allow for the detection of these 'living off the land' techniques, which are designed to blend in with normal operations. This provides a crucial detection-in-depth capability if the initial social engineering trick succeeds.

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