This detection identifies the execution of 32-bit self-extracting WinRAR modules, which adversaries frequently leverage to stage payloads and bypass standard file-based defenses during initial access or lateral movement phases. Proactive hunting for this behavior in Azure Sentinel is essential to uncover stealthy extraction activities that may precede the deployment of malicious components often missed by signature-only approaches.
rule WinRAR32bitSFXModule
{
meta:
author="malware-lu"
strings:
$a0 = { E9 [2] 00 00 00 00 00 00 90 90 90 [6] 00 ?? 00 [5] FF }
condition:
$a0 at pe.entry_point
}
This YARA rule can be deployed in the following contexts:
This rule contains 1 string patterns in its detection logic.
Here are 5 specific false positive scenarios for the WinRAR32bitSFXModule detection rule, including suggested filters and exclusions:
Scenario: Automated Deployment of Internal Patching Tools
WinRAR.exe (specifically the 32-bit SFX module) to extract compressed update packages from a shared network drive (\\fileserver\patches) before executing them on endpoints.SCCM, PDQ Deploy, or specific internal PowerShell scripts) where the parent process name matches these tools and the file path is located within a trusted administrative directory (e.g., C:\Program Files\InternalTools\).Scenario: Scheduled Backup of User Home Directories
WinRAR.exe process (32-bit) that are running under the context of the “SYSTEM” or a dedicated service account (e.g., BackupService) and where the command line arguments contain keywords like /a, /ep1, or specific backup job identifiers.Scenario: Installation of Third-Party Productivity Software
.exe installers created with WinRAR SFX. When a user