FortiSIEM Rules

Windows: HackTool - winPEAS Execution

Rule ID


Default Status



WinPEAS is a script that search for possible paths to escalate privileges on Windows hosts. The checks are explained on This rule is adapted from







Discovery consists of techniques an adversary may use to gain knowledge about the system and internal network. These techniques help adversaries observe the environment and orient themselves before deciding how to act. They also allow adversaries to explore what they can control and what’s around their entry point in order to discover how it could benefit their current objective. Native operating system tools are often used toward this post-compromise information-gathering objective.

MITRE ATT&CK® Techniques


System Information Discovery

An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture. Adversaries may use the information from during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions. Tools such as Systeminfo can be used to gather detailed system information. A breakdown of system data can also be gathered through the macOS "systemsetup" command, but it requires administrative privileges. Infrastructure as a Service (IaaS) cloud providers such as AWS, GCP, and Azure allow access to instance and virtual machine information via APIs. Successful authenticated API calls can return data such as the operating system platform and status of a particular instance or the model view of a virtual machine.



Data Source

Windows Sysmon via FortiSIEM Agent



Remediation Guidance

No remediation guidance specified

Time Window

If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.

300 seconds

Trigger Conditions

If the following defined pattern/s occur within a 300 second time window.


SubPattern Definitions

SubPattern Name: Filter

This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.

SubPattern Query

This is the query logic that matches incoming events

eventType="Win-Sysmon-1-Create-Process" AND (srcFileName="winPEAS.exe" OR procName REGEXP "\\winPEASany\.exe$|\\winPEASany_ofs\.exe$|\\winPEASx64\.exe$|\\winPEASx64_ofs\.exe$|\\winPEASx86\.exe$|\\winPEASx86_ofs\.exe$" OR command REGEXP ".* applicationsinfo.*|.* browserinfo.*|.* eventsinfo.*|.* fileanalysis.*|.* filesinfo.*|.* processinfo.*|.* servicesinfo.*|.* windowscreds.*" OR command REGEXP ".*https://github\.com/carlospolop/PEASS-ng/releases/latest/download/.*" OR parentCommand REGEXP " -linpeas$" OR command REGEXP " -linpeas$")

Group by Attributes

This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID


Aggregate Constraint

This is most typically a numerical constraint that defines when the rule should trigger an incident

COUNT(*) >= 1

Incident Attribute Mapping

This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.

The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern

command = Filter.command,
hostName = Filter.hostName,
parentCommand = Filter.parentCommand,
procName = Filter.procName,
srcFileName = Filter.srcFileName