Malicious Powershell Process - Execution Policy Bypass

Description

This search looks for PowerShell processes started with parameters used to bypass the local execution policy for scripts. These parameters are often observed in attacks leveraging PowerShell scripts as they override the default PowerShell execution policy.

Content Mapping

This content is not mapped to any local saved search. Add mapping


Use Case

Security Monitoring

Category

Malware

Alert Volume

This search looks for PowerShell processes started with parameters used to bypass the local execution policy for scripts. These parameters are often observed in attacks leveraging PowerShell scripts as they override the default PowerShell execution policy.

SPL Difficulty

None

Journey

Stage 3

MITRE ATT&CK Tactics

Execution

MITRE ATT&CK Techniques

Command and Scripting Interpreter

PowerShell

MITRE Threat Groups

APT19
APT28
APT29
APT3
APT32
APT33
APT39
APT41
BRONZE BUTLER
Blue Mockingbird
Chimera
Cobalt Group
CopyKittens
DarkHydrus
DarkVishnya
Deep Panda
Dragonfly 2.0
FIN10
FIN6
FIN7
FIN8
Frankenstein
Gallmaker
Gorgon Group
Inception
Kimsuky
Lazarus Group
Leviathan
Magic Hound
Molerats
MuddyWater
OilRig
Patchwork
Poseidon Group
Silence
Soft Cell
Stealth Falcon
TA459
TA505
TEMP.Veles
Threat Group-3390
Thrip
Turla
WIRTE
Wizard Spider
menuPass

Kill Chain Phases

Command and Control
Actions On Objectives

   Help

Malicious Powershell Process - Execution Policy Bypass Help

You must be ingesting data that records process activity from your hosts to populate the Endpoint data model in the Processes node. You must also be ingesting logs with both the process name and command line from your endpoints. The command-line arguments are mapped to the "process" field in the Endpoint data model.

   Search

Open in Search