This rule detects the presence of the AVPACKv120 YARA signature, which typically identifies specific malware families or packed executables that may be used for initial access or persistence. Proactively hunting for this pattern allows the SOC team to identify dormant or low-noise threats that might evade standard behavioral detections, ensuring early containment before the adversary establishes a foothold in the Azure environment.
rule AVPACKv120
{
meta:
author="malware-lu"
strings:
$a0 = { 50 1E 0E 1F 16 07 33 F6 8B FE B9 [2] FC F3 A5 06 BB [2] 53 CB }
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.
vmware-tools.exe or vmware-toolbox-cmd.exe) during a scheduled patch Tuesday maintenance window. The binary often contains packing stubs that match the AVPACKv120 signature.
vmsvc.exe or the image path matches C:\Program Files\VMware\VMware Tools\.java.exe or jre.exe binaries in newer versions may use packers that trigger this YARA rule, especially when executed by the CcmExec.exe or WUAHandler.exe parent process.
CcmExec.exe, WUAHandler.exe, or TrustedInstaller.exe and the image path contains \jre\ or \jdk\.7zG.exe, WinRAR.exe) when invoked by a user or a scheduled task to unpack application dependencies. These tools are frequently packed to reduce size, and their specific versioning may align with the AVPACKv120 detection.
7zG.exe, 7zFM.exe, WinRAR.exe, or WinRAR.exe and the parent process is explorer.exe or a known service account process.git.exe) or GitHub Desktop background sync processes.