Linux System Information Discovery via Common Command-Line Utilities

Flags Linux executions of uname, hostname, uptime, lspci, dmidecode, lscpu, and lsmod for system discovery behavior.

FreeReviewedSigma · Informational · v2
Product
linux
Category
process_creation
Author
Ömer Günal, oscd.community (SigmaHQ), DRL 1.1
Published
2020-10-08
Updated
2026-07-31

ATT&CK techniques

Discovery
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies process executions of common Linux commands used to gather system and hardware information, including uname, hostname, uptime, lspci, dmidecode, lscpu, and lsmod. Such discovery activity helps attackers profile the host environment before follow-on exploitation or lateral movement. The detection relies on Linux process creation telemetry by matching the executed image path ending with these utilities.

Related detections9 linkedT1082 — drag to rearrange
Malicious Turla Kopiluwak Reconnaissance Output to Windows Temp via process_creation
Suspicious Windows Defender Support Directory Enumeration via Process Creation
Suspicious System Reconnaissance via Windows Script Host
Suspicious Host Reconnaissance Command Chain via cmd
Malicious DinodasRAT Hidden Config File Creation on Linux (via file_event)
Suspicious System Discovery via WMIC Query Commands (via process_creation)
Suspicious PowerShell Host and Locale Reconnaissance via MuddyWater Tsundere Botnet
Suspicious System Reconnaissance Output Redirected to Temp rad File
Suspicious System Profiler Hardware Reconnaissance via BANSHEE
Linux System Information Discovery via Common Command-Line Utilities
Pivot detection · T1082 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.