MITRE ATT&CK Technique
T1480Execution Guardrails
- First Reported
- Mar 15, 2026
- Latest Reported
- Oct 12, 2026
Official Description
Adversaries may use execution guardrails to constrain execution or actions based on adversary supplied and environment specific conditions that are expected to be present on the target. Guardrails ensure that a payload only executes against an intended target and reduces collateral damage from an adversary’s campaign.(Citation: FireEye Kevin Mandia Guardrails) Values an adversary can provide about a target system or environment to use as guardrails may include specific network share names, attached physical devices, files, joined Active Directory (AD) domains, and local/external IP addresses.(Citation: FireEye Outlook Dec 2019)
Guardrails can be used to prevent exposure of capabilities in environments that are not intended to be compromised or operated within. This use of guardrails is distinct from typical [Virtualization/Sandbox Evasion](https://attack.mitre.org/techniques/T1497). While use of [Virtualization/Sandbox Evasion](https://attack.mitre.org/techniques/T1497) may involve checking for known sandbox values and continuing with execution only if there is no match, the use of guardrails will involve checking for an expected target-specific value and only continuing with execution if there is such a match.
Adversaries may identify and block certain user-agents to evade defenses and narrow the scope of their attack to victims and platforms on which it will be most effective. A user-agent self-identifies data such as a user's software application, operating system, vendor, and version. Adversaries may check user-agents for operating system identification and then only serve malware for the exploitable software while ignoring all other operating systems.(Citation: Trellix-Qakbot)
Guardrails can be used to prevent exposure of capabilities in environments that are not intended to be compromised or operated within. This use of guardrails is distinct from typical [Virtualization/Sandbox Evasion](https://attack.mitre.org/techniques/T1497). While use of [Virtualization/Sandbox Evasion](https://attack.mitre.org/techniques/T1497) may involve checking for known sandbox values and continuing with execution only if there is no match, the use of guardrails will involve checking for an expected target-specific value and only continuing with execution if there is such a match.
Adversaries may identify and block certain user-agents to evade defenses and narrow the scope of their attack to victims and platforms on which it will be most effective. A user-agent self-identifies data such as a user's software application, operating system, vendor, and version. Adversaries may check user-agents for operating system identification and then only serve malware for the exploitable software while ignoring all other operating systems.(Citation: Trellix-Qakbot)
- Tactics
- Stealth
- Platforms
- ESXi, Linux, macOS, Windows
- MITRE Version
- 2.0
- Last Modified
- May 12, 2026
Sub-techniques (2)
Reported Context (14)
- The malware stops execution when locale or IP geolocation checks indicate a CIS country. ICMacOS Infostealer Evolves Into a Persistent macOS RAT
- The dropper takes its installation branch only if /tmp/flag exists and its .php staging script does not. Rapid7 Details BPFDoor and AVERAT Activity Targeting Network-Edge Appliances
- Address, fingerprint, and country filters restricted who could reach phishing pages. CSuite Campaign Uses Phishing, M365 Session Theft and Remote-Access Tools Against US and EU Organizations
- Deployment and execution are gated on checks including HAProxy or cron presence, victim-token validation, and ted backdoor targeting rules. DPRK-Linked Toolkit Uses HAProxy Backdoor and CurlRAT to Target South Korean Organizations
- Loaders checked platform and referrer, and exploit stages selected payloads by iOS version. 13 Malicious Packagist Themes Deliver iOS Spyware and Steal Crypto Wallet Seeds
CVE (5)
Malware (39)
People (5)
Threat Actors (18)
MITRE ATT&CK (136)
Vendors (19)
Products (50)
Tools (24)
Industries (20)
Countries (32)
Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.
