Malicious VoidLink Rootkit Dropper Artifacts via Filesystem (via file_event)

PremiumReviewedSigma · High · v1
Product
linux
Category
file_event
Author
HuntRule
Published
2026-08-05
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 the creation of VoidLink dropper artifacts prefixed with vl in temporary and shared memory directories on Linux hosts. The VoidLink rootkit stages its components as hidden vl_ files under /tmp and /dev/shm before loading its kernel module. Files matching this naming pattern indicate rootkit staging activity.

Related detections9 linkedT1027 — drag to rearrange
Suspicious Encoded PowerShell Using Base64 Stream Decompression Routines (via process_creation)
Suspicious PowerShell In-Memory Execution with AES Decryption
Suspicious Encoded PowerShell Command Execution
Malicious ld.so.preload Hijack Loading libcext by Auto-Color (via process_creation)
Suspicious Loading of Malicious Netfilter Kernel Module for Traffic Signaling
Malicious Kernel Driver Load from User AppData Directory
Suspicious node.exe Executing Compiled JavaScript Bytecode File
Malicious Encoded Payload Decoded and Piped to Shell via xxd or base64 (via process_creation)
Suspicious PEAKLIGHT Memory-Only PowerShell Downloader Flags (via process_creation)
Malicious VoidLink Rootkit Dropper Artifacts via Filesystem (via file_event)
Pivot detection · T1027 · 9 related

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