huntrule

Linux OS Architecture Discovery Using grep

Flags grep executions on Linux whose command line ends with known CPU/architecture identifiers.

FreeReviewedSigma · Low · v2
Product
linux
Category
process_creation
Author
Joseliyo Sanchez, @Joseliyo_Jstnk (SigmaHQ), DRL 1.1
Published
2023-06-02
Updated
2026-07-31
AnalysisDetection

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. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags Linux process executions where the binary name ends with '/grep' and the command line ends with architecture identifiers such as aarch64, arm, i386, i686, mips, or x86_64. Attackers use this kind of quick local system profiling to determine compatibility before payload selection or follow-on actions. It relies on process creation telemetry that includes the process image path and the full command line.

Reporting behind it

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 OS Architecture Discovery Using grep
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.