This detection identifies the execution of files packed with the ASPack v10.1b compressor, a technique often employed by adversaries to obfuscate malicious payloads and evade static analysis. Proactively hunting for this behavior in Azure Sentinel is essential because low-severity packing events can serve as an early indicator of stealthy threats that may bypass signature-based defenses until they exhibit more aggressive runtime activity.
rule ASPackv101bAlexeySolodovnikov
{
meta:
author="malware-lu"
strings:
$a0 = { 60 E8 [4] 5D 81 ED D2 2A 44 ?? B8 CC 2A 44 ?? 03 C5 2B 85 A5 2E 44 ?? 89 85 B1 2E 44 ?? 80 BD 9C 2E 44 }
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 ASPackv101bAlexeySolodovnikov YARA rule, including targeted filters and exclusions:
Scenario: Automated Patch Deployment via Microsoft Endpoint Configuration Manager (SCCM)
ccmsetup.exe or wuauserv.exe where the parent process is SMS_EXECUTIVE. Alternatively, add a file path exclusion for files located in C:\Windows\CCM\Logs\ and C:\Program Files (x86)\Microsoft Configuration Manager\.Scenario: Antivirus Signature Updates via Symantec Endpoint Protection
SymCorp.exe or Rtvscan64.exe. Additionally, exclude file paths containing \Program Files\Symantec Endpoint Protection\Content\Updates\ to ignore transient update artifacts.Scenario: Scheduled Backup Job Execution via Veeam Agent
VeeamAgent.exe or VeeamService.exe. Implement a path-based