Linux Process Discovery of Container Environment via ls -i on / Directory

Detects Linux commands that list inode information for '/' to probe whether execution is occurring inside a container.

FreeReviewedSigma · Low · v2
Product
linux
Category
process_creation
Author
Seth Hanford (SigmaHQ), DRL 1.1
Published
2023-08-23
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 the 'ls' command with options used to list inode information for the root directory ('/'), which can be used to infer whether the system is running inside a container. Attackers may use this environment checks to adjust behavior, select appropriate exploits, or avoid analysis. The detection relies on process creation telemetry, specifically matching command-line patterns indicating 'ls' usage with directory and inode-related flags and a target of '/'.

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 Process Discovery of Container Environment via ls -i on / Directory
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.