Suspicious PowerShell Masquerading as Windows Terminal via process_creation

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-06-09
Updated
2026-08-28

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects a process whose original file name is PowerShell but which executes under the wt.exe Windows Terminal file name. The axios supply chain payload renamed powershell.exe to wt.exe to evade name-based detection, so a mismatch between the internal PowerShell identity and a wt.exe image name indicates a masqueraded interpreter.

Related detections9 linkedT1036.003 — drag to rearrange
Renamed Autohotkey Binary
Suspicious Masqueraded Rundll32 with Mismatched Original Filename (via process_creation)
Suspicious Renamed git Binary gcmd.exe Execution (via process_creation)
Renamed Execution of a Renamed Windows System Utility (via process_creation)
Suspicious Renamed Pythonw Interpreter Execution via XWorm Loader (via process_creation)
Windows Schtasks Execution with Renamed schtasks.exe Binary
Windows RMM Tool MeshAgent Execution with Renamed MeshServiceName
macOS Process Creation: MeshAgent renamed execution via --meshServiceName
Suspicious LOLBIN Copy From Windows System Directories Using Windows Copy Tools
Suspicious PowerShell Masquerading as Windows Terminal via process_creation
Pivot detection · T1036.003 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.