Suspicious WindowsTerminal Child Processes
Last updated on:
In this page
About the rule
Rule Type
Standard
Rule Description
Detects suspicious children spawned via the Windows Terminal application which could be a sign of persistence via WindowsTerminal (see references section)
Severity
Trouble
Rule Requirement
Criteria
Action1: actionname = "Process started" AND (PARENTPROCESSNAME endswith "\WindowsTerminal.exe,\wt.exe" AND (PROCESSNAME endswith "\rundll32.exe,\regsvr32.exe,\certutil.exe,\cscript.exe,\wscript.exe,\csc.exe" OR PROCESSNAME contains "C:\Users\Public\,\Downloads\,\Desktop\,\AppData\Local\Temp\,\Windows\TEMP" OR COMMANDLINE contains " iex , icm,Invoke-,Import-Module ,ipmo ,DownloadString(, /c , /k , /r ")) AND ((COMMANDLINE notcontains "Import-Module" OR COMMANDLINE notcontains "Microsoft.VisualStudio.DevShell.dll" OR COMMANDLINE notcontains "Enter-VsDevShell") AND (COMMANDLINE notcontains "\AppData\Local\Packages\Microsoft.WindowsTerminal_" OR COMMANDLINE notcontains "\LocalState\settings.json") AND (COMMANDLINE notcontains "C:\Program Files\Microsoft Visual Studio" OR COMMANDLINE notcontains "\Common7\Tools\VsDevCmd.bat")) select Action1.HOSTNAME,Action1.MESSAGE,Action1.COMMANDLINE,Action1.FILE_NAME,Action1.PROCESSNAME,Action1.USERNAME,Action1.PARENTPROCESSNAME
Detection
Execution Mode
realtime
Log Sources
Windows
Author
Nasreddine Bencherchali (Nextron Systems)
