FortiSIEM Rules

Windows: Potential Crypto Mining Activity

Rule ID


Default Status



Detects command line parameters or strings often used by crypto miners. This rule is adapted from







Impact consists of techniques that adversaries use to disrupt availability or compromise integrity by manipulating business and operational processes. Techniques used for impact can include destroying or tampering with data. In some cases, business processes can look fine, but may have been altered to benefit the adversaries’ goals. These techniques might be used by adversaries to follow through on their end goal or to provide cover for a confidentiality breach.

MITRE ATT&CK® Techniques


Resource Hijacking

Adversaries may leverage the resources of co-opted systems in order to solve resource intensive problems which may impact system and/or hosted service availability. One common purpose for Resource Hijacking is to validate transactions of cryptocurrency networks and earn virtual currency. Adversaries may consume enough system resources to negatively impact and/or cause affected machines to become unresponsive.(Citation: Kaspersky Lazarus Under The Hood Blog 2017) Servers and cloud-based(Citation: CloudSploit - Unused AWS Regions) systems are common targets because of the high potential for available resources, but user endpoint systems may also be compromised and used for Resource Hijacking and cryptocurrency mining.



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 command REGEXP ".* --algo=rx/0 .*|.* --cpu-priority=.*|.* --nicehash.*|.* -o pool\..*|.*--donate-level=0.*|.*0tZG9uYXRlLWxldmVsP.*|.*LS1kb25hdGUtbGV2ZWw9.*|.*N0cmF0dW0rdGNwOi8v.*|.*N0cmF0dW0rdWRwOi8v.*|.*c3RyYXR1bSt0Y3A6Ly.*|.*c3RyYXR1bSt1ZHA6Ly.*|.*stratum\+tcp://.*|.*stratum\+udp://.*|.*tLWRvbmF0ZS1sZXZlbD.*|.*zdHJhdHVtK3RjcDovL.*|.*zdHJhdHVtK3VkcDovL.*" AND (command NOT REGEXP ".* pool\.c .*|.* pool\.o .*|.*gcc -.*")

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