Suspicious Payload Staging and Execution from Shared Memory

PremiumReviewedSigma · Medium · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-11-01
Updated
2026-11-01

ATT&CK techniques

Execution → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects files being copied into or executed from the /dev/shm shared memory filesystem, a fileless staging location used by Tsunami and related Log4Shell payloads to run components without touching disk. Combined with persistence via crontab this lets attackers maintain access while minimizing forensic artifacts.

Related detections9 linkedT1053.003 — drag to rearrange
Malicious APT36 Crontab Persistence Logging to Shared Memory via Command Line (via process_creation)
Malicious JADEPUFFER Python Beacon via Cron
Malicious Cron Execution of Binary from tmp Directory on Linux (via process_creation)
Suspicious Process Execution from Hidden Outlaw Config Directory
Suspicious Cron Reboot Persistence Pointing to Hidden User Directory on Linux
Suspicious Cron Job Downloading and Executing Payload via GlobalProtect Exploitation
Suspicious Remote Script Download Piped to Shell via 8220 Gang Hadooken
Suspicious Linux Crontab Reboot Persistence to Hidden Sys Cache Binary (via process_creation)
Suspicious Cron Persistence Installing a Downloader via Command Line
Suspicious Payload Staging and Execution from Shared Memory
Pivot detection · T1053.003 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.