This detection identifies potential anti-virus evasion or vaccination behaviors where adversaries modify security tools to prevent malware analysis and execution. SOC teams should proactively hunt for this activity in Azure Sentinel to uncover stealthy threats that bypass standard signature-based defenses by manipulating antivirus components before malicious payloads are fully deployed.
rule AntiVirusVaccinev103
{
meta:
author="malware-lu"
strings:
$a0 = { FA 33 DB B9 [2] 0E 1F 33 F6 FC AD 35 [2] 03 D8 E2 }
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 AntiVirusVaccinev103 detection rule, along with recommended filters and exclusions:
Scenario: Symantec Endpoint Protection (SEP) Client Auto-Update Service
SepClient.exe process initiates a scheduled update job every morning at 06:00 AM to download the latest virus definition signatures. This activity often triggers the YARA rule due to the specific binary signature of the vaccine package being downloaded and executed by the client service.Symantec Endpoint Protection Client Service (PID range or hash) running under the NT SERVICE\SepClientService account, specifically when the file path matches C:\Program Files\Symantec Endpoint Protection\Bin\SepClient.exe.Scenario: Microsoft Defender Antivirus (MSRT) Scheduled Scan
Image path contains \Program Files\Windows Defender\MsMpEng.exe and the command line arguments include /scan. Additionally, filter out alerts generated during the configured maintenance window (e.g., 02:00 – 04:00).Scenario: CrowdStrike Falcon Sensor Policy Update
FalconSensorService process executes these updates, which the YARA rule interprets as a generic antivirus vaccine injection event due to overlapping binary characteristics.