This hunt targets the execution of binaries packed with UPX compression to identify potential obfuscation efforts by adversaries aiming to evade static analysis and signature-based detection. Proactively hunting for these indicators in Azure Sentinel is essential because UPX-packed executables often mask malicious payloads that could bypass initial security controls, necessitating deeper behavioral investigation despite their low severity classification.
rule UPXHiTv001DJSiba
{
meta:
author="malware-lu"
strings:
$a0 = { 94 BC [3] 00 B9 ?? 00 00 00 80 34 0C ?? E2 FA 94 FF E0 61 }
condition:
$a0
}
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 UPXHiTv001DJSiba detection rule, which identifies executables packed with the UPX (Ultimate Packer) utility:
Scenario: Deployment of Microsoft Office Updates via SCCM
OfficeC2RClient.exe or similar update agents execute, they trigger this rule.OfficeC2RClient.exe, Setup.exe) located in C:\Program Files\Microsoft Office\Updates\. Alternatively, exclude the SCCM client process (ccmexec.exe) when spawning child processes with UPX signatures.Scenario: Scheduled Antivirus Definition Updates
FalconSensor.exe updater module) to perform the installation silently during off-hours, triggering the detection logic upon execution.NT SERVICE\CrowdStrikeService) or filter based on the file path C:\Program Files\CrowdStrike\FalconAgent\ where UPX-packed update binaries reside.Scenario: Execution of Third-Party RMM Tools