Suspicious Whoami Execution With Output Redirected to a File (via process_creation)

ATT&CK techniques

Discovery

Recon
Resource Dev
Initial Access
Execution
Persistence
Priv Esc
Defense Evasion
Cred Access
Discovery
- T1033System Owner/User Discovery
Lateral Movement
Collection
C2
Exfiltration
Impact

What it detects

This rule detects whoami being run with its output redirected into a file, a reconnaissance-and-staging behavior used by loaders such as SocGholish to capture the current user and privilege context for the operator to review. Automated whoami-to-file collection is documented in the Red Canary Threat Detection Report as an early post-compromise step. Because interactive users rarely redirect whoami output to disk, this is a useful indicator of scripted hands-on activity.

Reporting behind it

Related detections9 linkedT1033 — drag to rearrange

Possible Logged-On Session Discovery via Quser or Qwinsta (via process_creation)

Suspicious Reconnaissance Spawned by Injected SearchProtocolHost via process_creation

Windows Process Creation: whoami.exe Executed With /all for Full Identity Enumeration

Linux Process Execution of esxcli Network Commands for ESXi Network Discovery

Linux Process Execution of esxcli VM Listing Commands

Linux ESXi esxcli VSAN Information Discovery via esxcli Command

Linux Process Creation: ESXi esxcli system discovery via system namespace

Linux ESXi esxcli Storage Information Discovery via esxcli storage commands

Windows whoami.exe Group Membership Reconnaissance via /groups Flag

Suspicious Whoami Execution With Output Redirected to a File (via process_creation)

Pivot detection · T1033 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.

Full detection rule

Unlock this rule to view and copy it

The detection logic is included with a plan. Everything else — context, mappings and implementation details — stays free on this page.

Sign in for 3 free unlocks

Signing in gives you 3 unlocks to spend on any rule in the library. No card, and they do not expire.

Also included

Unlocked rules convert on this page — to Splunk SPL or Splunk — Raw Index SPL or Microsoft Sentinel KQL or Microsoft Sentinel ASIM ASIM KQL or Microsoft Defender XDR KQL or Elastic Security KQL or Elastic Security Lucene or Elastic Security ES|QL or CrowdStrike Falcon CQL or SentinelOne PowerQuery or Palo Alto Cortex XDR XQL or Carbon Black Cloud Platform Search or Carbon Black EDR Process Search or Google Security Operations UDM Search or IBM QRadar AQL or Sumo Logic Cloud SIEM Rules expression or Rapid7 InsightIDR LEQL or Graylog Search or OpenSearch Lucene or OpenSearch PPL PPL or Grafana Loki LogQL or SQLite SQL or Zircolite SQLite — with the log-source profile the engine picked, the field map it used, and everything it could not express. Converting a rule you have unlocked costs no further credit.

See it run on a free rule →Convert your own rule →