CyberStack

MITRE ATT&CK / Techniques / T1134.002

Access Token Manipulation: Create Process with Token

ID
T1134.002
Tactics
TA0004 Privilege Escalation, TA0005 Stealth
Sub-technique of
T1134 Access Token Manipulation
Platforms
Windows
Data sources
Process Creation, Process Access, OS API Execution, Logon Session Metadata, Active Directory Object Modification
Source
attack.mitre.org
MITRE last modified
12 May 2026

Adversaries may create a new process with an existing token to escalate privileges and bypass access controls. Processes can be created with the token and resulting security context of another user using features such as CreateProcessWithTokenW and runas.[4]

Creating processes with a token not associated with the current user may require the credentials of the target user, specific privileges to impersonate that user, or access to the token to be used. For example, the token could be duplicated via Token Impersonation/Theft or created via Make and Impersonate Token before being used to create a process.

While this technique is distinct from Token Impersonation/Theft, the techniques can be used in conjunction where a token is duplicated and then used to create a new process.

Detection

Mitigations (2)

M1018 User Account Management

An adversary must already have administrator level access on the local system to make full use of this technique; be sure to restrict users and accounts to the least privileges they require.

M1026 Privileged Account Management

Limit permissions so that users and user groups cannot create tokens. This setting should be defined for the local system account only. GPO: Computer Configuration > [Policies] > Windows Settings > Security Settings > Local Policies > User Rights Assignment: Create a token object. [1] Also define who can create a process level token to only the local and network service through GPO: Computer Configuration > [Policies] > Windows Settings > Security Settings > Local Policies > User Rights Assignment: Replace a process level token.[2]

Administrators should log in as a standard user but run their tools with administrator privileges using the built-in access token manipulation command runas.[3]

Groups (2)

Software (12)

References

  1. Microsoft Create Token
  2. Microsoft Replace Process Token
  3. Microsoft runas
  4. Microsoft RunAs