Linux Process Execution of bpftrace with the --unsafe Option

Alerts when bpftrace is executed with the --unsafe option on Linux.

FreeReviewedSigma · Medium · v3
Product
linux
Category
process_creation
Author
Andreas Hunkeler (@Karneades) (SigmaHQ), DRL 1.1
Published
2022-02-11
Updated
2026-07-31

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags process executions where the command line for bpftrace includes the --unsafe option. The unsafe flag enables behavior that can increase risk and may be used by an attacker to bypass safeguards when running bpftrace. It relies on process creation telemetry capturing the executed image path ending with bpftrace and the command-line arguments.

Related detections9 linkedT1059.004 — drag to rearrange
Suspicious Reverse Shell via Dev TCP or Netcat
Suspicious Base64 Decoded Payload Piped to Shell
Suspicious Shell Spawned by ActiveMQ Java Process
Suspicious Bad Apples Reverse Shell via socat pty
Suspicious Axios NPM macOS Persistence Masquerading as Apple Service
Malicious Shell Payload Piped from curl to zsh
Possible Bitbucket Pre-Auth RCE via git archive exec Null-Byte Injection (CVE-2022-36804) (via webserver)
Malicious TeamTNT Docker Gatling Gun Initialization Script (via process_creation)
Suspicious Shell Spawned by PostgreSQL Server Process (via process_creation)
Linux Process Execution of bpftrace with the --unsafe Option
Pivot detection · T1059.004 · 9 related

Changelog

v3
  1. v3
    Candidate ingested via manual entry.2026-07-31
  2. v2
    Candidate ingested via manual entry.2026-07-31
  3. v1
    No changelog recorded for this version.2026-07-30

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