PowerShell Scripts Installed as Services

calendar Apr 14, 2023 · attack.execution attack.t1569.002  ·
Share on: linkedin copy

Detects powershell script installed as a Service

Sigma rule (View on GitHub)

 1title: PowerShell Scripts Installed as Services
 2id: a2e5019d-a658-4c6a-92bf-7197b54e2cae
 3status: test
 4description: Detects powershell script installed as a Service
 5references:
 6    - https://speakerdeck.com/heirhabarov/hunting-for-powershell-abuse
 7author: oscd.community, Natalia Shornikova
 8date: 2020/10/06
 9modified: 2022/12/25
10tags:
11    - attack.execution
12    - attack.t1569.002
13logsource:
14    product: windows
15    service: system
16detection:
17    selection:
18        Provider_Name: 'Service Control Manager'
19        EventID: 7045
20        ImagePath|contains:
21            - 'powershell'
22            - 'pwsh'
23    condition: selection
24falsepositives:
25    - Unknown
26level: high

References

  • Hunting for PowerShell Abuse

    PowerShell is the favorit tool of IT guys, who are responsible for administration of Windows infrastructures. It allows them to manage differen services of the operating system and automate almost anything. But along with administrators, PowerShell also is liked by attackers and malware authors. The reason PowerShell is so attractive for adversaries is quite obvious: it has been included in essentially every Windows operating system by default for a decade, provides access to Windows API, and is rarely constrained, thus allowing adversaries to perform different tasks without risking being blocked. ttackers can use PowerShell to direct the execution of a local script, retrieve and execute remote resources using various network protocols, encode payloads passed via the command line, or load PowerShell into other processes. Because of so prevalence of PowerShell among adversaries for Threat Hunters it is very important to be able to detect malicious uses of PowerShell and defend against it. In the presentation author is going to demostrate an approaches for detection of PowerShell abuses based on different event sources like native Windows logging capabilities as well as usage of additional tools, like Sysmon or EDR solutions. How to collect traces of using PowerShell, how to filter out false positives, and how to find evidence of malicious uses among the remaining after filtering volume of events — all these questions will be answered in the talk for present and future threat hunters.


    Read More

Related rules

to-top