This rule detects the presence of VProtector V13X, a commercial virtualization-based code obfuscation tool frequently leveraged by adversaries to hide malicious payloads and evade static analysis. Proactively hunting for this signature allows the SOC team to identify potentially obfuscated executables or injected code within Azure Sentinel that may be designed to bypass traditional detection mechanisms.
rule VProtector_V13X_vcasm_additional: PEiD
{
strings:
$a = { 00 00 00 00 55 73 65 72 33 32 2E 64 6C 6C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 47 64 69 33 32 2E 64 6C 6C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4B 65 72 6E 65 6C 33 32 2E 64 6C 6C 00 00 00 00 00 00 00 00 00 }
condition:
$a at pe.entry_point
}
This YARA rule can be deployed in the following contexts:
This rule contains 1 string patterns in its detection logic.
Legacy .NET Application Deployment via ClickOnce or MSI Installers
vcasm signature) is written to disk, triggering the YARA rule.C:\Program Files\, C:\Program Files (x86)\) where the parent process is a known installer service (e.g., msiexec.exe, clickonce.exe) or a specific enterprise deployment tool (e.g., wsus, SCCM).Scheduled Backup or Archiving Jobs for Custom Utilities
Task Scheduler (svchost.exe or taskschd.msi) or cron-like services on a regular schedule. The YARA rule scans the binary on disk or in memory during execution, causing a false positive.svchost.exe (specifically the Schedule service) or taskeng.exe, and where the file path matches known utility directories (e.g., C:\Scripts\, C:\Tools\, C:\Maintenance\).Development and Testing Environments for .NET Teams