Detect Stripped Payloads in Sumo Logic CSE
Adversaries may attempt to make a payload difficult to analyze by removing symbols, strings, and other human readable information. Scripts and executables may contain variable names and other strings that help developers document code functionality. Symbols are often created by an operating system's linker when executable payloads are compiled. Adversaries use stripped payloads to make malware analysis more difficult. Stripped payload formats include run-only AppleScripts (compiled and stripped AppleScript), stripped ELF binaries on Linux, and stripped PE files on Windows. Cuckoo Stealer and macOS.OSAMiner are notable examples using stripped formats. Golang malware is frequently stripped to remove symbol tables.
MITRE ATT&CK
- Tactic
- Defense Evasion
- Technique
- T1027 Obfuscated Files or Information
- Sub-technique
- T1027.008 Stripped Payloads
- Canonical reference
- https://attack.mitre.org/techniques/T1027/008/
Sumo Detection Query
(_sourceCategory=*endpoint* OR _sourceCategory=*syslog* OR _sourceCategory=*osquery* OR _sourceCategory=*edr*)
| where commandLine matches "(?i)osacompile\s+-x"
OR commandLine matches "(?i)osascript.*run-only"
OR commandLine matches "(?i)\bstrip\b.*(--strip-all|\s-s\s)"
OR commandLine matches "(?i)go\s+build.*-ldflags.*(-s|-w)"
OR commandLine matches "(?i)(gcc|g\+\+)\s+.*\s-s(\s|$)"
OR commandLine matches "(?i)pdbremove"
OR commandLine matches "(?i)cv2pdb"
| fields _time, hostname, src_user, process_name, commandLine
| sort by _time descSumo Logic query detecting T1027.008 stripped payload creation across endpoint and syslog data sources. Uses Java regex via the 'matches' operator on process command line fields to identify osacompile run-only AppleScript compilation, Linux ELF binary stripping, Go and GCC symbol-stripping compiler flags, and Windows PE symbol removal tools. Compatible with Cloud SIEM Enterprise normalized field names.
Data Sources
Required Tables
False Positives & Tuning
- Developer workstations and CI systems running Go release builds with -ldflags '-s -w' to reduce binary size — extremely common in containerized application pipelines and Docker multistage builds
- Build automation systems (Ansible playbooks, CMake install targets, Makefile post-install rules) invoking strip on compiled artifacts as a standard deployment step
- Security researchers and red teamers on authorized assessments using osacompile -x or strip to prepare test payloads for approved engagements
Other platforms for T1027.008
Testing Methodology
Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Create Run-Only AppleScript (macOS Stripped Payload)
Expected signal: Process creation events for osacompile (twice) and osascript. File creation events for compiled.scpt and runonly.scpt. The runonly.scpt will fail osadecompile, confirming stripped (run-only) status.
- Test 2Strip Symbols from Linux Binary with strip Command
Expected signal: Process creation for cp, strip, file, and nm commands. File creation and modification events for /tmp/stripped_ls. The 'file' output will show 'stripped', and nm will return 'no symbols'.
- Test 3Compile Go Binary with Symbol Stripping Flags
Expected signal: Process creation for go build with -ldflags '-s -w' arguments. File creation of stripped_go in /tmp. Execution of stripped_go from /tmp. The 'file' command shows stripped ELF.
- Test 4Verify Stripped Binary Cannot Be Analyzed with Standard Tools
Expected signal: Process creation events for cp (twice), strip, and nm (twice). This test demonstrates the before/after comparison an analyst would perform to confirm stripping.
References (4)
- https://attack.mitre.org/techniques/T1027/008/
- https://www.sentinelone.com/labs/fade-dead-adventures-in-reversing-malicious-run-only-applescripts/
- https://www.intezer.com/blog/malware-analysis/executable-linkable-format-101-part-2-symbols/
- https://www.mandiant.com/resources/blog/golang-internals-symbol-recovery
Unlock Pro Content
Get the full detection package for T1027.008 including response playbook, investigation guide, and atomic red team tests.