1200KM / sigma-rule
PowerShell Scripts Installed as Services — Sigma Rule
Sigma rule a2e5019d-a658-4c6a-92bf-7197b54e2cae. PowerShell Scripts Installed as Services — Sigma Rule. Detects powershell script installed as a Service
Rule metadata and linked tags
Author: oscd.community, Natalia Shornikova. Source status: test; severity: high. Source dates: 2020-10-06 / 2022-12-25.
{
"product": "windows",
"service": "system"
}Pinned original Sigma rule · Detection Rule License 1.1
Source SHA-256: db4e9b40abc87785cb924559de65de64b506cc2ac8a746522ce20d0d51737b6c
Detection logic
Original source YAML. Source-tag agreement is not proof of complete semantic coverage. This rule has not been compiled for a SIEM backend or validated against live telemetry here.
title: PowerShell Scripts Installed as Services
id: a2e5019d-a658-4c6a-92bf-7197b54e2cae
status: test
description: Detects powershell script installed as a Service
references:
- https://speakerdeck.com/heirhabarov/hunting-for-powershell-abuse
author: oscd.community, Natalia Shornikova
date: 2020-10-06
modified: 2022-12-25
tags:
- attack.execution
- attack.t1569.002
logsource:
product: windows
service: system
detection:
selection:
Provider_Name: 'Service Control Manager'
EventID: 7045
ImagePath|contains:
- 'powershell'
- 'pwsh'
condition: selection
falsepositives:
- Unknown
level: high
False positives
- Unknown
Source references
Connected ecosystem references
Exact source-tagged techniques
Telemetry review
Read the original logsource above, then inspect the linked detection workspaces for technique-level sensor context. No per-rule telemetry equivalence is inferred.
Pinned research references. No browser attack runner, live simulation result or validated detector is asserted. Source mappings and validation limits are preserved. ATT&CK / Atomic provenance · Detection provenance.