This rule detects the presence of PKLite, a lightweight SQLite database engine often embedded in Windows applications, which adversaries may leverage to store stolen data or maintain persistence without the overhead of a full database service. Proactively hunting for this artifact in Azure Sentinel allows the SOC to identify potentially compromised endpoints or unusual data staging activities that standard database monitoring might miss due to its minimal footprint.
rule PKLITEv1501
{
meta:
author="malware-lu"
strings:
$a0 = { 50 B8 [2] BA [2] 05 [2] 3B 06 [2] 72 ?? B4 ?? BA [2] CD 21 B8 [2] CD 21 }
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.
pklite.exe utility from the Windows Resource Kit or a standalone download to defragment a specific user profile or system drive during a maintenance window.
explorer.exe or cmd.exe/powershell.exe and the command line arguments contain specific flags like /f (defragment) or /v (verbose), provided the execution path is in a known administrative tools directory (e.g., C:\Program Files\Windows Resource Kit\).pklite.exe to clean up temporary files or defragment the C: drive for all users at 2:00 AM daily.
svchost.exe (specifically the Task Scheduler service) or Taskeng.exe, and the full path of the executable matches a known trusted location such as C:\Windows\System32\ or a dedicated maintenance folder like C:\AdminTools\.pklite.exe to optimize disk space on newly imaged workstations before user sign-in.
ccmexec.exe (SCCM), IntuneAgent.exe, or pdqdeploy.exe, and the working directory is within the deployment staging area (e.g., C:\Windows\CCM\ or C:\ProgramData\Intune\).