Detection: PowerShell Loading DotNET into Memory via Reflection

Description

The following analytic detects the use of PowerShell to load .NET assemblies into memory via reflection, a technique often used in malicious activities such as those by Empire and Cobalt Strike. It leverages PowerShell Script Block Logging (EventCode=4104) to capture and analyze the full command executed. This behavior is significant as it can indicate advanced attack techniques aiming to execute code in memory, bypassing traditional defenses. If confirmed malicious, this activity could lead to unauthorized code execution, privilege escalation, and persistent access within the environment.

Search

1`powershell` EventCode=4104 ScriptBlockText IN ("*[system.reflection.assembly]::load(*","*[reflection.assembly]*", "*reflection.assembly*") 
2| stats count min(_time) as firstTime max(_time) as lastTime by Opcode Computer UserID EventCode ScriptBlockText 
3| `security_content_ctime(firstTime)` 
4| `security_content_ctime(lastTime)` 
5| `powershell_loading_dotnet_into_memory_via_reflection_filter`

Data Source

Name	Platform	Sourcetype	Source	Supported App
Powershell Script Block Logging 4104	Windows	'xmlwineventlog'	'XmlWinEventLog:Microsoft-Windows-PowerShell/Operational'	N/A

Macros Used

Annotations

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Implementation

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

False positives should be limited as day to day scripts do not use this method.

Associated Analytic Story

• AgentTesla

• AsyncRAT

• Data Destruction

• Hermetic Wiper

• Malicious PowerShell

• Winter Vivern

Risk Based Analytics (RBA)

References

• https://docs.microsoft.com/en-us/dotnet/api/system.reflection.assembly?view=net-5.0

• 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/

Detection Testing

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: GitHub | Version: 4