adding some more suspicious PS keywords

found in multiple internally analyzed malicious scripts (in the wild and as result of engagements)

rules/windows/powershell/powershell_suspicious_keywords.yml

@@ -2,19 +2,26 @@ title: Suspicious PowerShell Keywords
 status: experimental
 description: Detects keywords that could indicate the use of some PowerShell exploitation framework
 date: 2019/02/11
-author: Florian Roth
+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'
+    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:
-        - 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