Malicious VoidLink Fileless Execution via memfd via Memory (via process_creation)

PremiumReviewedSigma · High · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-07-21
Updated
2026-08-28

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects processes executing from an anonymous in-memory file descriptor on Linux hosts. The VoidLink rootkit loader uses memfd_create and execveat to run its payload entirely from memory without touching disk. Execution backed by a memfd path is a strong indicator of fileless malware staging.

Related detections9 linkedT1620 — drag to rearrange
PowerShell Reflective Shellcode Loader via Dynamic API Delegates (via ps_script)
Obfuscated XE Group Reflective Loader via PowerShell Spawned by IIS Worker Process (via process_creation)
Suspicious Reflective Assembly Load in PowerShell (via ps_script)
Suspicious PowerShell Reflective Assembly Load Invoking VAI Method (via process_creation)
PowerShell In-Memory Shellcode Execution via Memory Allocation APIs (via ps_script)
Malicious Fileless Execution via memfd Anonymous File on Linux Cloud Workload (via process_creation)
Windows PowerShell: In-Memory Assembly Loading via Reflection.Assembly
Windows PowerShell: Base64 Encoded Reflective .NET Assembly Load
PowerShell Script Block WinAPI Calls Indicative of Injection or Token Abuse (Windows)
Malicious VoidLink Fileless Execution via memfd via Memory (via process_creation)
Pivot detection · T1620 · 9 related

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