SigmaHQ/rules/windows/powershell/powershell_suspicious_keywords.yml
Thomas Patzke 924e1feb54 UUIDs + moved unsupported logic
* Added UUIDs to all contributed rules
* Moved unsupported logic directory out of rules/ because this breaks CI
  testing.
2019-12-19 23:56:36 +01:00

32 lines
1.2 KiB
YAML

title: Suspicious PowerShell Keywords
id: 1f49f2ab-26bc-48b3-96cc-dcffbc93eadf
status: experimental
description: Detects keywords that could indicate the use of some PowerShell exploitation framework
date: 2019/02/11
author: Florian Roth, Perez Diego (@darkquassar)
references:
- https://posts.specterops.io/entering-a-covenant-net-command-and-control-e11038bcf462
- https://github.com/PowerShellMafia/PowerSploit/blob/master/CodeExecution/Invoke-ReflectivePEInjection.ps1
- https://github.com/hlldz/Invoke-Phant0m/blob/master/Invoke-Phant0m.ps1
tags:
- attack.execution
- attack.t1086
logsource:
product: windows
service: powershell
definition: 'It is recommended to use the new "Script Block Logging" of PowerShell v5 https://adsecurity.org/?p=2277. Monitor for EventID 4104'
detection:
keywords:
Message:
- "System.Reflection.Assembly.Load"
- "[System.Reflection.Assembly]::Load"
- "[Reflection.Assembly]::Load"
- "System.Reflection.AssemblyName"
- "Reflection.Emit.AssemblyBuilderAccess"
- "Runtime.InteropServices.DllImportAttribute"
- "SuspendThread"
condition: keywords
falsepositives:
- Penetration tests
level: high