Command Shell Activity Started via RunDLL32
Identifies command shell activity started via RunDLL32, which is commonly abused by attackers to host malicious code.
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
- ContainersESXiIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the 3 ATT&CK techniques it maps to.
- Log source category
- event_index
Known benign triggers
- Microsoft Windows installers leveraging RunDLL32 for installation.
No references are available for this detection.
From the source
- At source
- Open at source
- Upstream identifier
- 9ccf3ce0-0057-440a-91f5-870c6ad39093
- Tagged by the source as
- Data Source: Elastic DefendData Source: Elastic EndgameData Source: Microsoft Defender XDRData Source: SentinelOneData Source: SysmonDomain: EndpointNoise: MediumOS: WindowsPerformance: NormalPlatform: WindowsResources: Investigation GuideRule Type: Event Correlation (EQL)Tactic: Credential AccessTactic: Defense EvasionTactic: ExecutionThreat: Living off the LandUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3