Powershell Fileless Process Injection via GetProcAddress

Try in Splunk Security Cloud

Description

The following analytic detects the use of GetProcAddress in PowerShell script blocks, leveraging PowerShell Script Block Logging (EventCode=4104). This method captures the full command sent to PowerShell, which is then logged in Windows event logs. The presence of GetProcAddress is unusual for typical PowerShell scripts and often indicates malicious activity, as many attack toolkits use it to achieve code execution. If confirmed malicious, this activity could allow an attacker to execute arbitrary code, potentially leading to system compromise. Analysts should review parallel processes and the entire logged script block for further investigation.

• Type: TTP

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

• Last Updated: 2024-05-18
• Author: Michael Haag, Splunk
• ID: a26d9db4-c883-11eb-9d75-acde48001122

Annotations

ATT&CK

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

• Installation
• Exploitation

NIST

• DE.CM

CIS20

• CIS 10

CVE

Search

`powershell` EventCode=4104 ScriptBlockText=*getprocaddress* 
| stats count min(_time) as firstTime max(_time) as lastTime by Opcode Computer UserID EventCode ScriptBlockText 
| rename Computer as dest 
| rename UserID as user 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `powershell_fileless_process_injection_via_getprocaddress_filter`

Macros

The SPL above uses the following Macros:

• powershell
• security_content_ctime

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 fields

List of fields required to use this analytic.

• _time
• ScriptBlockText
• Opcode
• Computer
• UserID
• 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

• Malicious PowerShell
• Hermetic Wiper
• Data Destruction

RBA

Risk Score	Impact	Confidence	Message
48.0	60	80	A suspicious powershell script contains GetProcAddress API on host $dest$

The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

Reference

• https://docs.splunk.com/Documentation/UBA/5.0.4.1/GetDataIn/AddPowerShell#Configure_module_logging_for_PowerShell.
• https://blog.palantir.com/tampering-with-windows-event-tracing-background-offense-and-defense-4be7ac62ac63
• https://static1.squarespace.com/static/552092d5e4b0661088167e5c/t/59c1814829f18782e24f1fe2/1505853768977/Windows+PowerShell+Logging+Cheat+Sheet+ver+Sept+2017+v2.1.pdf
• https://www.crowdstrike.com/blog/investigating-powershell-command-and-script-logging/
• https://www.splunk.com/en_us/blog/security/hunting-for-malicious-powershell-using-script-block-logging.html

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: 3