huntrule

Windows Process Creation: Sysinternals PsService (PsService*.exe) Execution

Alerts on execution of Sysinternals PsService (PsService*.exe) on Windows, which can support service discovery and tampering.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-06-16
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Persistence → Priv Esc

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags process creation events where the executable name corresponds to Sysinternals PsService variants (psservice.exe and PsService*.exe). Attackers may use PsService to perform service-oriented discovery or to prepare for tampering as part of broader privilege escalation or persistence efforts. It relies on Windows process creation telemetry, matching the process image/original filename. Legitimate administrative use can also trigger the alert.

Reporting behind it

Related detections9 linkedT1543.003 — drag to rearrange
Malicious Abyss Locker wmihelper SSH Backdoor Deployment (via file_event)
Malicious AuKill EDR Killer Kernel Driver Load via Process Explorer Driver (via image_load)
Suspicious TermService ServiceDll Hijack via Registry (via registry_set)
Suspicious Service Creation Named RDP-Controller via sc.exe (via process_creation)
Suspicious Service or Task Named windowsinspectionupdate (via process_creation)
Malicious Service Persistence via sc.exe Creating msdnetsvc
Suspicious Stately Taurus Masqueraded Service and Task Persistence via process_creation
Malicious Vulnerable Driver Load for EDR Evasion (via image_load)
Malicious Gelsemium OwlProxy wmipd DLL Load via image_load
Windows Process Creation: Sysinternals PsService (PsService*.exe) Execution
Pivot detection · T1543.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.