Suspicious Process Execution via Renamed PsExec Executable
Elastic Stack Serverless Security
Identifies suspicious psexec activity which is executing from the psexec service that has been renamed, possibly to evade detection.
Rule type: eql
Rule indices:
- winlogbeat-*
- logs-endpoint.events.*
- logs-windows.*
- endgame-*
Severity: medium
Risk score: 47
Runs every: 5m
Searches indices from: now-9m (https://www.elastic.co/guide/en/elasticsearch/reference/current/common-options.html#date-math[Date Math format], see also Additional look-back time)
Maximum alerts per execution: 100
References: None
Tags:
- Elastic
- Host
- Windows
- Threat Detection
- Execution
- Elastic Endgame
Version: 103
Rule authors:
- Elastic
Rule license: Elastic License v2
process where event.type == "start" and
process.pe.original_file_name : "psexesvc.exe" and not process.name : "PSEXESVC.exe"
Framework: MITRE ATT&CKTM
Tactic:
- Name: Execution
- ID: TA0002
- Reference URL: https://attack.mitre.org/tactics/TA0002/
Technique:
- Name: System Services
- ID: T1569
- Reference URL: https://attack.mitre.org/techniques/T1569/
Sub-technique:
- Name: Service Execution
- ID: T1569.002
- Reference URL: https://attack.mitre.org/techniques/T1569/002/