This rule detects the presence of ASPack v1.07b, a legacy packer frequently used by threat actors to compress and obfuscate malicious executables to evade static analysis. Proactively hunting for this specific signature allows the SOC team to identify potentially compromised hosts or dormant payloads that may have been overlooked by standard AV detections due to their low severity classification.
rule ASPackv107bAlexeySolodovnikov
{
meta:
author="malware-lu"
strings:
$a0 = { 60 E8 [4] 5D 81 ED [4] B8 [4] 03 C5 2B 85 ?? 0B DE ?? 89 85 17 DE [2] 80 BD 01 DE }
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.
Legacy Application Deployment via Group Policy
C:\Program Files\, C:\Program Files (x86)\) that match the specific vendor name or known good hash (SHA-256) of the deployed legacy application. Alternatively, exclude processes initiated by gpupdate.exe or ccmexec.exe if the rule is process-based.Scheduled Backup or Maintenance Jobs
schtasks.exe or svchost.exe running the task engine), and the packed executable is loaded into memory, matching the YARA signature.schtasks.exe, svchost.exe (specifically the task scheduler service), or taskeng.exe. Additionally, whitelist the specific file path of the maintenance utility (e.g., C:\Scripts\Maintenance\clean_logs.exe) if it is a known internal tool.Third-Party Security or Monitoring Agents