T1027.009_embedded-payloads

T1027.009 Embedded Payloads

Sub-technique of: T1027

High-Level Description

Adversaries may embed payloads within other files to conceal malicious content from defenses. Otherwise seemingly benign files (such as scripts and executables) may be abused to carry and obfuscate malicious payloads and content. In some cases, embedded payloads may also enable adversaries to Subvert Trust Controls by not impacting execution controls such as digital signatures and notarization tickets.

Adversaries may embed payloads in various file formats to hide payloads. This is similar to Steganography, though does not involve weaving malicious content into specific bytes and patterns related to legitimate digital media formats.

For example, adversaries have been observed embedding payloads within or as an overlay of an otherwise benign binary. Adversaries have also been observed nesting payloads (such as executables and run-only scripts) inside a file of the same format.

Embedded content may also be used as Process Injection payloads used to infect benign system processes. These embedded then injected payloads may be used as part of the modules of malware designed to provide specific features such as encrypting C2 communications in support of an orchestrator module. For example, an embedded module may be injected into default browsers, allowing adversaries to then communicate via the network.

Kill Chain Phase

• Defense Evasion (TA0005)

Platforms: Linux, macOS, Windows

What to Check

• Identify if Embedded Payloads technique is applicable to target environment
• Check Linux systems for indicators of Embedded Payloads
• Check macOS systems for indicators of Embedded Payloads
• Check Windows systems for indicators of Embedded Payloads
• Verify mitigations are bypassed or absent (2 known mitigations)
• Assess detection coverage (1 detection strategies)

How to Test

Manual Testing

1. Identify Attack Surface: Determine if the target environment is susceptible to Embedded Payloads by examining the target platforms (Linux, macOS, Windows).

2. Assess Existing Defenses: Review whether mitigations for T1027.009 are in place. If defenses are absent or misconfigured, this technique may be exploitable.

3. Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.

Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.

Remediation Guide

M1049 Antivirus/Antimalware

Anti-virus can be used to automatically detect and quarantine suspicious files.

M1040 Behavior Prevention on Endpoint

On Windows 10, enable Attack Surface Reduction (ASR) rules to prevent execution of potentially obfuscated scripts.

Detection

Detection Strategy for Embedded Payloads

Risk Assessment

CWE Categories

References

• GitHub PSImage
• Malware Analysis Report ComRAT
• Trend Micro
• Securelist Dtrack2
• Microsoft Learn
• SentinelLabs reversing run-only applescripts 2021
• Sentinel Labs
• Atomic Red Team - T1027.009
• MITRE ATT&CK - T1027.009