MITRE ATT&CK Technique
T1134Access Token Manipulation
- First Reported
- Oct 7, 2025
- Latest Reported
- Oct 20, 2026
Official Description
Adversaries may modify access tokens to operate under a different user or system security context to perform actions and bypass access controls. Windows uses access tokens to determine the ownership of a running process. A user can manipulate access tokens to make a running process appear as though it is the child of a different process or belongs to someone other than the user that started the process. When this occurs, the process also takes on the security context associated with the new token.
An adversary can use built-in Windows API functions to copy access tokens from existing processes; this is known as token stealing. These token can then be applied to an existing process (i.e. [Token Impersonation/Theft](https://attack.mitre.org/techniques/T1134/001)) or used to spawn a new process (i.e. [Create Process with Token](https://attack.mitre.org/techniques/T1134/002)). An adversary must already be in a privileged user context (i.e. administrator) to steal a token. However, adversaries commonly use token stealing to elevate their security context from the administrator level to the SYSTEM level. An adversary can then use a token to authenticate to a remote system as the account for that token if the account has appropriate permissions on the remote system.(Citation: Pentestlab Token Manipulation)
Any standard user can use the <code>runas</code> command, and the Windows API functions, to create impersonation tokens; it does not require access to an administrator account. There are also other mechanisms, such as Active Directory fields, that can be used to modify access tokens.
An adversary can use built-in Windows API functions to copy access tokens from existing processes; this is known as token stealing. These token can then be applied to an existing process (i.e. [Token Impersonation/Theft](https://attack.mitre.org/techniques/T1134/001)) or used to spawn a new process (i.e. [Create Process with Token](https://attack.mitre.org/techniques/T1134/002)). An adversary must already be in a privileged user context (i.e. administrator) to steal a token. However, adversaries commonly use token stealing to elevate their security context from the administrator level to the SYSTEM level. An adversary can then use a token to authenticate to a remote system as the account for that token if the account has appropriate permissions on the remote system.(Citation: Pentestlab Token Manipulation)
Any standard user can use the <code>runas</code> command, and the Windows API functions, to create impersonation tokens; it does not require access to an administrator account. There are also other mechanisms, such as Active Directory fields, that can be used to modify access tokens.
- Tactics
- Stealth, Privilege Escalation
- Platforms
- Windows
- MITRE Version
- 3.0
- Last Modified
- May 12, 2026
Sub-techniques (5)
Reported Context (13)
- Attackers abused Windows token impersonation to act as SYSTEM without stealing credentials. ThreatDown 2026 Malware Report Tracks Ransomware Growth and AI-Assisted Attacks
- Detected Potato-family tools used token spoofing techniques in an attempt to obtain SYSTEM privileges. Attackers Exploit Telerik CVE-2019-18935 to Install Web Shells and Scan for Exposed WordPress Pages
- The actor attempted privilege escalation through token impersonation or theft. Chinese-Speaking Hackers Exploit WordPress and Other Flaws to Steal Government Data
- ChonkyChicken supported token-based execution through token_run and used APIs for token manipulation. TAG-195 Evolves Its Malware-as-a-Service Toolkit with Four New Malware Families
- The article maps token modification in its CVE-2025-29824 exploitation chain to this ID. TTP-Chain Validation Offers a Way to Assess Exploitability Without Live Exploits
CVE (21)
Malware (32)
People (14)
Threat Actors (32)
MITRE ATT&CK (87)
Vendors (25)
Products (69)
Tools (47)
Industries (17)
Countries (26)
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.
