This detection identifies potential adversary activity involving fake or malicious AS Pack components that mimic legitimate system behavior to evade initial scrutiny. A proactive hunt is essential in Azure Sentinel to uncover stealthy lateral movement or persistence mechanisms that may bypass standard signature-based defenses despite their low severity classification.
rule MSLRHv032afakeASPack212emadicius
{
meta:
author="malware-lu"
strings:
$a0 = { 60 E8 03 00 00 00 E9 EB 04 5D 45 55 C3 E8 01 00 00 00 EB 5D BB ED FF FF FF 03 DD 81 EB 00 A0 02 EB 05 E8 EB 04 40 00 EB FA E8 0A 00 00 00 E8 EB 0C 00 00 E8 F6 FF FF FF E8 F2 FF FF FF 83 C4 08 74 04 75 02 EB 02 EB 01 81 50 E8 02 00 00 00 29 5A 58 6B C0 03 E8 02 00 00 00 29 5A 83 C4 04 58 74 04 75 02 EB 02 EB 01 81 0F 31 50 0F 31 E8 0A 00 00 00 E8 EB 0C 00 00 E8 F6 FF FF FF E8 F2 FF FF 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 4 specific false positive scenarios for the detection rule MSLRHv032afakeASPack212emadicius, along with recommended filters and exclusions tailored for a legitimate enterprise environment:
Scenario: Automated Endpoint Protection Scans
Process Name matches C:\Program Files\CrowdStrike\FalconSensor\csfalcon.exe, C:\Program Files\Microsoft Defender\MsMpEng.exe, or C:\Program Files\SentinelOne\SentinelOne\SentinelService.exe.Scenario: Patch Management and Software Deployment
Parent Process is ccmexec.exe (System Center Configuration Manager) or installshield.exe, specifically when the event timestamp falls within the defined maintenance window (e.g., Sundays 02:00–04:00 UTC).Scenario: Backup and Archiving Operations