Powershell Processing Stream Of Data

Try in Splunk Security Cloud

Description

The following analytic detects suspicious PowerShell script execution involving compressed stream data processing, identified via EventCode 4104. It leverages PowerShell Script Block Logging to flag scripts using IO.Compression, IO.StreamReader, or decompression methods. This activity is significant as it often indicates obfuscated PowerShell or embedded .NET/binary execution, which are common tactics for evading detection. If confirmed malicious, this behavior could allow attackers to execute hidden code, escalate privileges, or maintain persistence within the environment.

• Type: TTP

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

• Last Updated: 2024-05-16
• Author: Teoderick Contreras, Splunk
• ID: 0d718b52-c9f1-11eb-bc61-acde48001122

Annotations

ATT&CK

ATT&CK

ID	Technique	Tactic
T1059	Command and Scripting Interpreter	Execution

T1059.001

PowerShell

Execution

Kill Chain Phase

• Installation

NIST

• DE.CM

CIS20

• CIS 10

CVE

Search

`powershell` EventCode=4104 ScriptBlockText = "*IO.Compression.*" OR ScriptBlockText = "*IO.StreamReader*" OR ScriptBlockText = "*]::Decompress*" 
| stats count min(_time) as firstTime max(_time) as lastTime by EventCode ScriptBlockText Computer UserID 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `powershell_processing_stream_of_data_filter`

Macros

The SPL above uses the following Macros:

• powershell
• security_content_ctime

powershell_processing_stream_of_data_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
• EventCode
• ScriptBlockText
• Computer
• UserID
• Score

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

powershell may used this function to process compressed data.

Associated Analytic Story

• Malicious PowerShell
• AsyncRAT
• Hermetic Wiper
• Data Destruction
• IcedID

RBA

Risk Score	Impact	Confidence	Message
40.0	50	80	A suspicious powershell script contains stream command in $ScriptBlockText$ commonly for processing compressed or to decompressed binary file with EventCode $EventCode$ in host $Computer$

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://medium.com/@ahmedjouini99/deobfuscating-emotets-powershell-payload-e39fb116f7b9
• 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
• https://thedfirreport.com/2023/05/22/icedid-macro-ends-in-nokoyawa-ransomware/

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