Default Executable Paths
c:\Program Files\WindowsPowerShell\Modules\Pester\<VERSION>\bin\Pester.batIntegrity & Metadata
Documented in LOLBAS project by Oddvar Moe.
Monitor process creation events where FileName is "Pester.bat" or command line references known attack arguments.
Executive Summary & AI Quick Reference
Pester.bat is a native utility pre-installed on Windows systems. Threat actors and red teams abuse Pester.bat as a Living-off-the-Land Binary (LOLBin) to achieve Execute without triggering traditional antivirus file-hash alerts. Legitimate system administrators use it for routine administration, making behavioral command-line telemetry essential for differentiation.
Weaponized Parameters & Proof-of-Concepts
Documented attack commands, parameter flags, and privilege prerequisites.
Execute code using Pester. The third parameter can be anything. The fourth is the payload.
Pester.bat [/help|?|-?|/?] "$null; {CMD}"Execute code using Pester. Example here executes specified executable.
Pester.bat ;{PATH:.exe}SIEM & EDR Detection Rules
Production telemetry rules configured for Microsoft Defender, Sigma, and Splunk.
Telemetry & SIEM Detection Suite (Pester.bat)
Validated against MITRE T12161// Microsoft Defender XDR / Microsoft Sentinel2// Tactic: Execute3DeviceProcessEvents4| where FileName =~ "Pester.bat"5| where ProcessCommandLine has_any ("Pester")6| project7 Timestamp,8 DeviceName,9 AccountName,10 InitiatingProcessParentFileName,11 InitiatingProcessFileName,12 InitiatingProcessCommandLine,13 FileName,14 FolderPath,15 ProcessCommandLine,16 MD5,17 SHA25618| sort by Timestamp descMitigation, Hardening & Prevention
Recommended defensive controls to block or constrain Pester.bat abuse.
Enforce Windows Defender Application Control (WDAC) or AppLocker publisher rules to prevent execution outside approved enterprise administration scripts.
Enable ASR rules: Block executable content from email client and webmail and Block Office applications from creating child processes spawning Pester.bat.
Deploy the KQL, Sigma, and Splunk detection queries below. Alert on anomalous child processes, web requests to unrated external IPs, or encoded payload strings.
Frequently Asked Questions (FAQ) • Pester.bat
Key operational questions and defensive answers about Pester.bat LOLBin tradecraft.
What is Pester.bat and why is it classified as a LOLBin?
Pester.bat is a legitimate, pre-installed or trusted utility on Windows. It is classified as a Living-off-the-Land Binary (LOLBin) because adversaries abuse its built-in functionality to perform malicious operations—such as Execute—without dropping custom malware binaries on disk.
How do threat actors abuse Pester.bat in cyber intrusions?
Adversaries leverage Pester.bat to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "Pester.bat [/help|?|-?|/?] "$null; {CMD}"" to achieve Execute, masquerading behind legitimate system process lineage.
How can SOC analysts detect suspicious Pester.bat activity?
Detection engineers monitor process creation events (Windows Event ID 4688 or Sysmon Event ID 1; Linux auditd EXECVE; macOS Endpoint Security) inspecting anomalous command line arguments, unusual parent-child process relationships (e.g. Office apps or web servers spawning Pester.bat), and unexpected network connections.
What MITRE ATT&CK techniques does Pester.bat map to?
Pester.bat maps to MITRE ATT&CK technique(s): T1216. These techniques cover adversary actions across tactics such as Defense Evasion, Execution, Persistence, and Command and Control.
How can organizations mitigate and restrict Pester.bat?
Mitigation strategies include implementing Application Control policies (AppLocker or Windows Defender Application Control - WDAC), enforcing Attack Surface Reduction (ASR) rules, configuring strict privilege separation (disallowing standard users from running sensitive switches), and alerting on execution from non-standard directories.
Other High-Traffic WINDOWS LOLBins
Certutil.exe is a command-line program installed as part of Certificate Services. Attackers frequently abuse it to download arbitrary files from remote URLs, encode/decode Base64 payloads to evade detection, and hash files.
Microsoft HTML Application (MSHTA) host executes .hta files and scripts embedded inside web pages. Attackers abuse mshta to execute malicious inline VBScript or JScript directly from the command line or remote HTTP servers.
The Rundll32 program loads and runs 32-bit and 64-bit Dynamic Link Libraries (DLLs). Threat actors use it to execute exported functions from arbitrary DLLs, run scriptlets, or execute code via MSHTML protocol handlers.
Background Intelligent Transfer Service (BITS) administrator tool manages asynchronous, throttled background transfers. Attackers use BITS to stage remote downloads that survive reboots and evade conventional network monitoring.