This detection identifies potential adversary activity involving the execution of the PCPECalphapreview process, which may indicate early-stage reconnaissance or the deployment of a specialized preview tool by an attacker. A proactive hunt is recommended to validate whether this low-severity event represents legitimate administrative usage or a stealthy initial foothold that could escalate into more critical threats within the Azure Sentinel environment.
rule PCPECalphapreview
{
meta:
author="malware-lu"
strings:
$a0 = { 53 51 52 56 57 55 E8 00 00 00 00 5D 8B CD 81 ED 33 30 40 00 }
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 PCPECalphapreview detection rule, including suggested filters and exclusions tailored for an enterprise environment:
Scenario: Microsoft Office Background Preview Generation
PCPECalphapreview signature due to its internal rendering engine behavior.WINWORD.EXE, EXCEL.EXE, or POWERPNT.EXE located within the standard Office installation path (e.g., C:\Program Files\Microsoft Office\...).Scenario: Scheduled Indexing by Windows Search Service
SearchFilterHost.exe) runs scheduled jobs to index new or modified documents. During the indexing of rich media files, it invokes preview handlers that trigger this YARA rule. This is common during off-hours maintenance windows when bulk file migrations occur.SearchFilterHost.exe running under the SYSTEM account, specifically when the command line arguments contain /preview or match the known hash of the Windows Search service component.Scenario: Enterprise Document Management System (DMS) Scanning
Groove.exe) or DocuSign often perform background scans to generate document previews for web interfaces. These clients utilize the same preview handler logic detected by the rule, causing alerts whenever a user syncs a folder containing hundreds of documents.