Try in Splunk Security Cloud

Description

The following analytic utilizes PowerShell Script Block Logging (EventCode=4104) to identify suspicious PowerShell execution. Script Block Logging captures the command sent to PowerShell, the full command to be executed. Upon enabling, logs will output to Windows event logs. Dependent upon volume, enable no critical endpoints or all.
This analytic identifies GetProcAddress in the script block. This is not normal to be used by most PowerShell scripts and is typically unsafe/malicious. Many attack toolkits use GetProcAddress to obtain code execution.
In use, $var_gpa = $var_unsafe_native_methods.GetMethod(GetProcAddress and later referenced/executed elsewhere.
During triage, review parallel processes using an EDR product or 4688 events. It will be important to understand the timeline of events around this activity. Review the entire logged PowerShell script block.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2021-06-08
  • Author: Michael Haag, Splunk
  • ID: a26d9db4-c883-11eb-9d75-acde48001122

Annotations

ATT&CK
ID Technique Tactic
T1059 Command and Scripting Interpreter Execution
T1055 Process Injection Defense Evasion, Privilege Escalation
T1059.001 PowerShell Execution
Kill Chain Phase
  • Exploitation
NIST
CIS20
CVE
1
2
3
4
5
`powershell` EventCode=4104 Message=*getprocaddress* 
| stats count min(_time) as firstTime max(_time) as lastTime by OpCode ComputerName User EventCode Message 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `powershell_fileless_process_injection_via_getprocaddress_filter`

Macros

The SPL above uses the following Macros:

Note that powershell_fileless_process_injection_via_getprocaddress_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required field

  • _time
  • Message
  • OpCode
  • ComputerName
  • User
  • EventCode

How To Implement

To successfully implement this analytic, you will need to enable PowerShell Script Block Logging on some or all endpoints. Additional setup here https://docs.splunk.com/Documentation/UBA/5.0.4.1/GetDataIn/AddPowerShell#Configure_module_logging_for_PowerShell.

Known False Positives

Limited false positives. Filter as needed.

Associated Analytic story

RBA

Risk Score Impact Confidence Message
48.0 60 80 A suspicious powershell script contains GetProcAddress API in $Message$ with EventCode $EventCode$ in host $ComputerName$

Reference

Test Dataset

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 1