T1559: Inter-Process Communication
Tactics: Execution. Platforms: Linux, macOS, Windows.
Adversaries may abuse inter-process communication (IPC) mechanisms for local code or command execution.
MITRE's description
Adversaries may abuse inter-process communication (IPC) mechanisms for local code or command execution. IPC is typically used by processes to share data, communicate with each other, or synchronize execution. IPC is also commonly used to avoid situations such as deadlocks, which occurs when processes are stuck in a cyclic waiting pattern. Adversaries may abuse IPC to execute arbitrary code or commands.
Telemetry that detects it
- File Access
- Named Pipe Metadata
- Process Access
- Process Creation
- Script Execution
Mitigations
- Application Developer Guidance
- Enable the Hardened Runtime capability when developing applications. Do not include the com.apple.security.get-task-allow entitlement with the value set to any variation of true.
- Behavior Prevention on Endpoint
- On Windows 10, enable Attack Surface Reduction (ASR) rules to prevent DDE attacks and spawning of child processes from Office programs.
- Privileged Account Management
- Modify Registry settings (directly or using Dcomcnfg.exe) in HKEY_LOCAL_MACHINE\\SOFTWARE\\Classes\\AppID\\{AppID_GUID} associated with the process-wide security of individual COM…
- Software Configuration
- Consider disabling embedded files in Office programs, such as OneNote, that do not work with Protected View.
- Application Isolation and Sandboxing
- Ensure all COM alerts and Protected View are enabled.
Procedure examples
- During the 3CX Supply Chain Attack, AppleJeus's VEILEDSIGNAL creates and listens on a Windows named pipe to exchange messages between modules.
- Cyclops Blink has the ability to create a pipe to enable inter-process communication.
- The Havoc SMB demon can use named pipes for communication through a parent demon.
- HyperStack can connect to the IPC$ share on remote machines.
18 documented uses in all. These are a sample.
MITRE ATT&CK Enterprise 19.2. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.