MITRE ATT&CK / Techniques / T1574.014

Hijack Execution Flow: AppDomainManager

ID
T1574.014
Tactics
TA0002 Execution, TA0005 Stealth
Sub-technique of
T1574 Hijack Execution Flow
Platforms
Windows
Data sources
Process Creation, File Creation, Module Load
Source
attack.mitre.org
MITRE last modified
12 May 2026

Adversaries may execute their own malicious payloads by hijacking how the .NET AppDomainManager loads assemblies. The .NET framework uses the AppDomainManager class to create and manage one or more isolated runtime environments (called application domains) inside a process to host the execution of .NET applications. Assemblies (.exe or .dll binaries compiled to run as .NET code) may be loaded into an application domain as executable code.[1]

Known as "AppDomainManager injection," adversaries may execute arbitrary code by hijacking how .NET applications load assemblies. For example, malware may create a custom application domain inside a target process to load and execute an arbitrary assembly. Alternatively, configuration files (.config) or process environment variables that define .NET runtime settings may be tampered with to instruct otherwise benign .NET applications to load a malicious assembly (identified by name) into the target process.[2][3][4]

Detection

Mitigations (1)

M1022 Restrict File and Directory Permissions

Install .NET applications and related software in write-protected locations. Set directory access controls to prevent file writes to the search paths for .NET applications, both in the folders where applications are run from and the standard resources folders.

Groups (1)

Software (1)

References

  1. Microsoft App Domains
  2. PenTestLabs AppDomainManagerInject
  3. PwC Yellow Liderc
  4. Rapid7 AppDomain Manager Injection