cyberstrikeus T1001.001 Junk Data
Sub-technique of: T1001
High-Level Description
Adversaries may add junk data to protocols used for command and control to make detection more difficult. By adding random or meaningless data to the protocols used for command and control, adversaries can prevent trivial methods for decoding, deciphering, or otherwise analyzing the traffic. Examples may include appending/prepending data with junk characters or writing junk characters between significant characters.
Kill Chain Phase
- Command and Control (TA0011)
Platforms: ESXi, Linux, macOS, Windows
What to Check
- Identify if Junk Data technique is applicable to target environment
- Check ESXi systems for indicators of Junk Data
- Check Linux systems for indicators of Junk Data
- Check macOS systems for indicators of Junk Data
- Verify mitigations are bypassed or absent (1 known mitigations)
- Assess detection coverage (1 detection strategies)
How to Test
Manual Testing
Identify Attack Surface: Determine if the target environment is susceptible to Junk Data by examining the target platforms (ESXi, Linux, macOS).
Assess Existing Defenses: Review whether mitigations for T1001.001 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
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
M1031 Network Intrusion Prevention
Network intrusion detection and prevention systems that use network signatures to identify traffic for specific adversary malware can be used to mitigate some obfuscation activity at the network level.
Detection
Detecting Junk Data in C2 Channels via Behavioral Analysis
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| Junk Data technique applicable | High | Command And Control |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-300 | Channel Accessible by Non-Endpoint |