updating name

Author: patel-bhavin

…jection_into_commonly_abused_process.yml …ction_into_commonly_abused_processes.ymldetections/endpoint/windows_process_injection_into_commonly_abused_process.yml renamed to detections/endpoint/windows_process_injection_into_commonly_abused_processes.yml detections/endpoint/windows_process_injection_into_commonly_abused_process.yml renamed to detections/endpoint/windows_process_injection_into_commonly_abused_processes.yml

@@ -1,4 +1,4 @@
-name: Windows Process Injection into Commonly Abused Process
+name: Windows Process Injection into Commonly Abused Processes
 id: 1e1dedc6-f6f3-41a0-9dd7-a1245904fe75
 version: 1
 date: '2025-03-19'
@@ -21,7 +21,7 @@ search: '`sysmon` EventCode=10 TargetImage IN ("*\\notepad.exe", "*\\wordpad.exe
   | `security_content_ctime(firstTime)` 
   | `security_content_ctime(lastTime)` 
   | table firstTime lastTime dest user SourceImage TargetImage GrantedAccess CallTrace count
-  | `windows_process_injection_into_commonly_abused_process_filter`'
+  | `windows_process_injection_into_commonly_abused_processes_filter`'
 how_to_implement: To successfully implement this search, you need to be ingesting
   logs with the process name, parent process, and command-line executions from your
   endpoints. If you are using Sysmon, you must have at least version 6.0.4 of the