Rootkit T1014

Events covered

3 catalog events are tagged with this technique by at least one rule.

Authoring guide

Patterns shared across the 30 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (31 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

Top indicator values (403 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.

Exclusions (272 distinct)

Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Sigma 2 rules

• Suspicious Kernel Extension Names
• Triple Cross eBPF Rootkit Install Commands

Elastic 22 rules

• BPF Program or Map Load via bpftool
• BPF Program Tampering via bpftool
• Kernel Driver Load
• Kernel Driver Load by non-root User
• Kernel Instrumentation Discovery via kprobes and tracefs
• Kernel Load or Unload via Kexec Detected
• Kernel Module Load from Unusual Location
• Kernel Module Load via Built-in Utility
• Kernel Object File Creation
• Kernel Seeking Activity
• Kernel Unpacking Activity
• Loadable Kernel Module Configuration File Creation
• Network Activity Detected via Kworker
• Potential Persistence via File Modification
• Suspicious File Creation via Kworker
• Suspicious Kworker UID Elevation
• Suspicious Usage of bpf_probe_write_user Helper
• Tainted Kernel Module Load
• Tainted Out-Of-Tree Kernel Module Load
• UID Elevation from Previously Unknown Executable
• Unusual Execution from Kernel Thread (kthreadd) Parent
• Unusual Kill Signal

Splunk 5 rules

• Linux Auditd Kernel Module Enumeration
• Linux Kernel Module Enumeration
• Linux Medusa Rootkit
• Windows Driver Load Non-Standard Path
• Windows Drivers Loaded by Signature

Panther 1 rule

• OSSEC Rootkit Detected via Osquery