MITRE ATT&CKtechnique

T1205 Traffic Signaling

Published 2018-04-18 Modified 2026-05-12 Official page ↗
Domain
enterprise
Tactics
Stealth, Persistence, Command And Control
Platforms
Linux, macOS, Network Devices, Windows
Version
3.0
Created
2018-04-18

Description

Adversaries may use traffic signaling to hide open ports or other malicious functionality used for persistence or command and control. Traffic signaling involves the use of a magic value or sequence that must be sent to a system to trigger a special response, such as opening a closed port or executing a malicious task. This may take the form of sending a series of packets with certain characteristics before a port will be opened that the adversary can use for command and control. Usually this series of packets consists of attempted connections to a predefined sequence of closed ports (i.e. Port Knocking), but can involve unusual flags, specific strings, or other unique characteristics. After the sequence is completed, opening a port may be accomplished by the host-based firewall, but could also be implemented by custom software. Adversaries may also communicate with an already open port, but the service listening on that port will only respond to commands or trigger other malicious functionality if passed the appropriate magic value(s). The observation of the signal packets to trigger the communication can be conducted through different methods. One means, originally implemented by Cd00r , is to use the libpcap libraries to sniff for the packets in question. Another method leverages raw sockets, which enables the malware to use ports that are already open for use by other programs. On network devices, adversaries may use crafted packets to enable Network Device Authentication for standard services offered by the device such as telnet. Such signaling may also be used to open a closed service port such as telnet, or to trigger module modification of malware implants on the device, adding, removing, or changing malicious capabilities. Adversaries may use crafted packets to attempt to connect to one or more (open or closed) ports, but may also attempt to connect to a router interface, broadcast, and network address IP on the same port in order to achieve their goals and objectives. To enable this traffic signaling on embedded devices, adversaries must first achieve and leverage Patch System Image due to the monolithic nature of the architecture. Adversaries may also use the Wake-on-LAN feature to turn on powered off systems. Wake-on-LAN is a hardware feature that allows a powered down system to be powered on, or woken up, by sending a magic packet to it. Once the system is powered on, it may become a target for lateral movement.

Related

Tactic · MITRE ATT&CK (3)

Referenced by MITRE ATT&CK · mitigates (2)

  • M1037 Filter Network Traffic mitigation
  • M1042 Disable or Remove Feature or Program mitigation

Referenced by MITRE ATT&CK · subtechnique of (2)

Referenced by MITRE ATT&CK · uses (23)

  • S9043 Mini Shai-Hulud software (malware)
  • S9011 BRUSHFIRE software (malware)
  • S1239 TONESHELL software (malware)
  • S1228 PUBLOAD software (malware)
  • C0056 RedPenguin campaign
  • S1219 REPTILE software (malware)
  • G1048 UNC3886 group
  • S1203 J-magic software (malware)
  • S1201 TRANSLATEXT software (malware)
  • S1118 BUSHWALK software (malware)
  • C0029 Cutting Edge campaign
  • S1114 ZIPLINE software (malware)
  • S0664 Pandora software (malware)
  • S0641 Kobalos software (malware)
  • G0129 Mustang Panda group
  • S0587 Penquin software (malware)
  • S0519 SYNful Knock software (malware)
  • S0446 Ryuk software (malware)
  • S0430 Winnti for Linux software (malware)
  • G0094 Kimsuky group
  • S0220 Chaos software (malware)
  • S0221 Umbreon software (malware)
  • S0022 Uroburos software (malware)

Referenced by Compliance · mitigates (12)

  • CIS-13.4 Perform Traffic Filtering Between Network Segments CIS Safeguard v8.1
  • CIS-4.4 Implement and Manage a Firewall on Servers CIS Safeguard v8.1
  • CIS-4.5 Implement and Manage a Firewall on End-User Devices CIS Safeguard v8.1
  • NIST-AC-3 Access Enforcement NIST 800-53 control
  • NIST-AC-4 Information Flow Enforcement NIST 800-53 control
  • NIST-CA-7 Continuous Monitoring NIST 800-53 control
  • NIST-CM-2 Baseline Configuration NIST 800-53 control
  • NIST-CM-6 Configuration Settings NIST 800-53 control
  • NIST-CM-7 Least Functionality NIST 800-53 control
  • NIST-SC-7 Boundary Protection NIST 800-53 control
  • NIST-SI-15 Information Output Filtering NIST 800-53 control
  • NIST-SI-4 System Monitoring NIST 800-53 control

References