heroui logo

Windows Cmd Command Line With Encoded Character Sequences

Splunk Security Content

View Source
Summary
This detection flags Windows cmd.exe command lines that contain long sequences of encoded characters in the payload. Encodings covered include decimal values (e.g., 12;70;18;…), hexadecimal (0x41,0x42,…), HTML entities, Unicode and octal escapes. Such obfuscated command lines are commonly used by loaders or payload fetchers (e.g., ClickFix-like chains) that decode the next stage at runtime via delayed variable expansion, then launch PowerShell or other stagers. This behavior can enable hidden payload execution or a download cradle, potentially with AMSI/defense evasion. The rule ingests endpoint telemetry (Sysmon EventID 1, Windows Security Log 4688, and CrowdStrike ProcessRollup2) and analyzes endpoint process data to detect cmd.exe invocations with encoded sequences. The search targets the Endpoint data model’s Processes data, filters for cmd.exe, applies a regex that matches repeated encoded token patterns (12 or more tokens), and surfaces a finding with context such as destination host, user, and the involved processes. Tying to MITRE, it maps to T1027.010 (Obfuscated/Compressed Files or Information), T1140 (Deobfuscate/Decode Files or Information), and T1059.003 (Windows Command Shell). References include MITRE technique pages and related threat context. The rule includes a note on potential false positives from legitimate batch files or tooling that pass long numeric or escaped sequences; adjustments to parent process filtering or command-line scope are recommended to reduce noise.
Categories
  • Endpoint
  • Windows
Data Sources
  • Process
  • Command
ATT&CK Techniques
  • T1027
  • T1140
  • T1059
  • T1027.010
  • T1059.003
Created: 2026-11-16