Suspicious Process Execution via Renamed PsExec Executable
Identifies suspicious psexec activity which is executing from the psexec service that has been renamed, possibly to evade detection.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersESXiIaaSLinuxmacOSWindows
The rule states no platform. This is derived from the 3 ATT&CK techniques it maps to.
- Log source category
- event_index
No references are available for this detection.
From the source
- At source
- Open at source
- Upstream identifier
- e2f9fdf5-8076-45ad-9427-41e0e03dc9c2
- Tagged by the source as
- Data Source: CrowdstrikeData Source: Elastic DefendData Source: Elastic EndgameData Source: Microsoft Defender XDRData Source: SysmonDomain: EndpointNoise: MediumOS: WindowsPerformance: NormalPlatform: WindowsResources: Investigation GuideRule Type: Event Correlation (EQL)Tactic: Defense EvasionTactic: ExecutionUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3