Detections

Explore public detection logic contributed by the community across SIEM and rule languages.

151 detections

Detects command-line arguments that are characteristic of Cobalt Strike modules or commands, which may indicate an operator error where these commands are accidentally typed into a command prompt instead of the Cobalt Strike console. This rule specifically looks for common 'Invoke-' PowerShell module names and other Cobalt Strike related keywords executed via 'cmd.exe'.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
1014
This rule detects the execution of rundll32.exe with command-line arguments indicative of Cobalt Strike's StartW function being used to load DLLs. Specifically, it looks for 'rundll32.exe' or 'rundll32 ' in the command line, along with a '.dll' file and either ' StartW' or ',StartW' as the ending argument. This behavior is commonly associated with Cobalt Strike for defense evasion and execution of malicious payloads.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0014
Detects suspicious execution of rundll32.exe without any command-line parameters, which is a known technique used by Cobalt Strike beacons for defense evasion. The rule specifically filters out common legitimate parent processes to reduce false positives.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0013
This rule detects the use of Gpg4win's gpg.exe or gpg2.exe for file decryption. It specifically looks for command-line arguments that include both '-d' (for decrypt) and 'passphrase', indicating an attempt to decrypt a file using a passphrase. This activity can be indicative of malicious actors decrypting sensitive data or malware components.
avatar
SigmaHQ Detections@sigmaHQ
avatar
SigmaHQ
2 years ago
0012
Page 8 of 8