1200kmSECURITY RESEARCH

1200KM / sigma-rule

BPFtrace Unsafe Option Usage — Sigma Rule

Sigma rule f8341cb2-ee25-43fa-a975-d8a5a9714b39. BPFtrace Unsafe Option Usage — Sigma Rule. Detects the usage of the unsafe bpftrace option

Rule metadata and linked tags

Author: Andreas Hunkeler (@Karneades). Source status: test; severity: medium. Source dates: 2022-02-11 / not supplied.

{
  "category": "process_creation",
  "product": "linux"
}

Pinned original Sigma rule · Detection Rule License 1.1

Source SHA-256: 15bedde784838bea41642c8556578f20fa4ce34eef100bb2a650565a051a27ff

Detection logic

Original source YAML. Source-tag agreement is not proof of complete semantic coverage. This rule has not been compiled for a SIEM backend or validated against live telemetry here.

title: BPFtrace Unsafe Option Usage
id: f8341cb2-ee25-43fa-a975-d8a5a9714b39
status: test
description: Detects the usage of the unsafe bpftrace option
references:
    - https://embracethered.com/blog/posts/2021/offensive-bpf-bpftrace/
    - https://bpftrace.org/
author: Andreas Hunkeler (@Karneades)
date: 2022-02-11
tags:
    - attack.execution
    - attack.t1059.004
logsource:
    category: process_creation
    product: linux
detection:
    selection:
        Image|endswith: 'bpftrace'
        CommandLine|contains: '--unsafe'
    condition: selection
falsepositives:
    - Legitimate usage of the unsafe option
level: medium

Original YAML and metadata in JSON

False positives

  • Legitimate usage of the unsafe option

Source references

Connected ecosystem references

Exact source-tagged techniques

Telemetry review

Read the original logsource above, then inspect the linked detection workspaces for technique-level sensor context. No per-rule telemetry equivalence is inferred.

Pinned research references. No browser attack runner, live simulation result or validated detector is asserted. Source mappings and validation limits are preserved. ATT&CK / Atomic provenance · Detection provenance.