Binary Executed from Shared Memory Directory
editBinary Executed from Shared Memory Directory
editIdentifies the execution of a binary by root in Linux shared memory directories: (/dev/shm/, /run/shm/, /var/run/, /var/lock/). This activity is to be considered highly abnormal and should be investigated. Threat actors have placed executables used for persistence on high-uptime servers in these directories as system backdoors.
Rule type: eql
Rule indices:
- logs-endpoint.events.*
Severity: high
Risk score: 73
Runs every: 5 minutes
Searches indices from: now-9m (Date Math format, see also Additional look-back time)
Maximum alerts per execution: 100
References:
Tags:
- Elastic
- Host
- Linux
- Threat Detection
- Execution
- BPFDoor
Version: 3 (version history)
Added (Elastic Stack release): 8.3.0
Last modified (Elastic Stack release): 8.4.0
Rule authors: Elastic
Rule license: Elastic License v2
Potential false positives
editDirectories /dev/shm and /run/shm are temporary file storage directories in Linux. They are intended to appear as a mounted file system, but uses virtual memory instead of a persistent storage device and thus are used for mounting file systems in legitimate purposes.
Rule query
editprocess where event.type == "start" and event.action == "exec" and user.name == "root" and process.executable : ( "/dev/shm/*", "/run/shm/*", "/var/run/*", "/var/lock/*" ) and not process.executable : ( "/var/run/docker/*")
Threat mapping
editFramework: MITRE ATT&CKTM
-
Tactic:
- Name: Execution
- ID: TA0002
- Reference URL: https://attack.mitre.org/tactics/TA0002/
-
Technique:
- Name: Command and Scripting Interpreter
- ID: T1059
- Reference URL: https://attack.mitre.org/techniques/T1059/
Rule version history
edit- Version 3 (8.4.0 release)
-
-
Updated query, changed from:
process where event.type == "start" and event.action == "exec" and user.name == "root" and process.executable : ( "/dev/shm/*", "/run/shm/*", "/var/run/*", "/var/lock/*" )
-