This detection identifies the presence of specific Pklite library versions (114, 115, and 120) often associated with legitimate software but potentially leveraged by adversaries for persistence or data exfiltration. Proactive hunting in Azure Sentinel is recommended to distinguish these benign instances from anomalous usage patterns that could indicate early-stage compromise or supply chain attacks within the environment.
rule PKLITEv114v115v1203
{
meta:
author="malware-lu"
strings:
$a0 = { B8 [2] BA [2] 05 [2] 3B [3] 72 ?? B4 09 BA ?? 01 CD 21 CD 20 4E 6F }
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 PKLITEv114v115v1203 detection rule, along with recommended filters and exclusions:
Scenario: Microsoft Office Click-to-Run Updates
OfficeClickToRun.exe process when it downloads or installs cumulative updates (versions 114, 115, or 120). These executables often contain embedded PKLite signatures that match the detection logic.OfficeClickToRun.exe and the file path is located within C:\Program Files\Microsoft Office\root\Office16.Scenario: Scheduled Antivirus Definition Updates
FalconSensor.exe (CrowdStrike) or Rtvscan64.exe (Symantec) running under the SYSTEM account during the defined maintenance window (e.g., 02:00 – 04:00).Scenario: System Center Configuration Manager (SCCM/MECM) Deployment
ccmsetup.exe or WuaUla.exe processes often unpack compressed payloads containing PKLite components. This is common during large-scale patching cycles involving version 114-120 updates.