Potentially Suspicious PowerShell Child Processes
Last updated on:
In this page
About the rule
Rule Type
Standard
Rule Description
Detects potentially suspicious child processes spawned by PowerShell. Use this rule to hunt for potential anomalies initiating from PowerShell scripts and commands.
Severity
Trouble
Rule Requirement
Criteria
Action1: actionname = "Process started" AND (PARENTPROCESSNAME endswith "\powershell_ise.exe,\powershell.exe,\pwsh.exe" AND PROCESSNAME endswith "\bash.exe,\bitsadmin.exe,\certutil.exe,\cscript.exe,\forfiles.exe,\hh.exe,\mshta.exe,\regsvr32.exe,\rundll32.exe,\schtasks.exe,\scrcons.exe,\scriptrunner.exe,\sh.exe,\wmic.exe,\wscript.exe") AND ((PROCESSNAME notendswith "\certutil.exe" OR COMMANDLINE notcontains "-verifystore ") AND (PROCESSNAME notendswith "\wmic.exe" OR COMMANDLINE notcontains "qfe list,diskdrive ,csproduct ,computersystem , os ,")) AND (PARENTPROCESSCOMMANDLINE notcontains "\Program Files\Amazon\WorkspacesConfig\Scripts" OR COMMANDLINE notcontains "\Program Files\Amazon\WorkspacesConfig\Scripts") select Action1.HOSTNAME,Action1.MESSAGE,Action1.COMMANDLINE,Action1.FILE_NAME,Action1.PROCESSNAME,Action1.USERNAME,Action1.PARENTPROCESSNAME
Detection
Execution Mode
realtime
Log Sources
Windows
Author
Florian Roth (Nextron Systems), Tim Shelton
