| ID | Name |
|---|---|
| T1136.001 | Local Account |
| T1136.002 | Domain Account |
| T1136.003 | Cloud Account |
Adversaries may create a local account to maintain access to victim systems. Local accounts are those configured by an organization for use by users, remote support, services, or for administration on a single system or service.
For example, with a sufficient level of access, the Windows net user /add command can be used to create a local account. In Linux, the useradd command can be used, while on macOS systems, the dscl -create command can be used. Local accounts may also be added to network devices, often via common Network Device CLI commands such as username, to ESXi servers via esxcli system account add, or to Kubernetes clusters using the kubectl utility.[1][2]
Adversaries may also create new local accounts on network firewall management consoles – for example, by exploiting a vulnerable firewall management system, threat actors may be able to establish super-admin accounts that could be used to modify firewall rules and gain further access to the network.[3]
Such accounts may be used to establish secondary credentialed access that do not require persistent remote access tools to be deployed on the system.
| ID | Name | Description |
|---|---|---|
| G0022 | APT3 |
APT3 has been known to create or enable accounts, such as |
| G0087 | APT39 |
APT39 has created accounts on multiple compromised hosts to perform actions within the network.[5] |
| G0096 | APT41 | |
| G1023 | APT5 |
APT5 has created Local Administrator accounts to maintain access to systems with short-cycle credential rotation.[7] |
| S0274 | Calisto |
Calisto has the capability to add its own account to the victim's machine.[8] |
| S0030 | Carbanak | |
| G1034 | Daggerfly |
Daggerfly created a local account on victim machines to maintain access.[10] |
| S1111 | DarkGate |
DarkGate creates a local user account, |
| G0035 | Dragonfly |
Dragonfly has created accounts on victims, including administrator accounts, some of which appeared to be tailored to each individual staging target.[12] |
| S0363 | Empire |
Empire has a module for creating a local user if permissions allow.[13] |
| G1016 | FIN13 |
FIN13 has created MS-SQL local accounts in a compromised network.[14] |
| S0143 | Flame |
Flame can create backdoor accounts with login "HelpAssistant" on domain connected systems if appropriate rights are available.[15][16] |
| G0117 | Fox Kitten |
Fox Kitten has created a local user account with administrator privileges.[17] |
| S0493 | GoldenSpy | |
| S0394 | HiddenWasp |
HiddenWasp creates a user account as a means to provide initial persistence to the compromised machine.[19] |
| S0601 | Hildegard | |
| G0119 | Indrik Spider |
Indrik Spider has created local system accounts and has added the accounts to privileged groups.[21] |
| G0094 | Kimsuky | |
| G0077 | Leafminer |
Leafminer used a tool called Imecab to set up a persistent remote access account on the victim machine.[23] |
| G0059 | Magic Hound |
Magic Hound has created local accounts named |
| S0084 | Mis-Type |
Mis-Type may create a temporary user on the system named |
| S0039 | Net |
The |
| S0192 | Pupy |
Pupy can user PowerView to execute "net user" commands and create local system accounts.[28] |
| S0085 | S-Type |
S-Type may create a temporary user on the system named |
| S0382 | ServHelper |
ServHelper has created a new user named "supportaccount".[29] |
| S0649 | SMOKEDHAM | |
| G0139 | TeamTNT |
TeamTNT has created local privileged users on victim machines.[31] |
| G0102 | Wizard Spider |
Wizard Spider has created local administrator accounts to maintain persistence in compromised networks.[32] |
| S0412 | ZxShell |
| ID | Mitigation | Description |
|---|---|---|
| M1032 | Multi-factor Authentication |
Use multi-factor authentication for user and privileged accounts. |
| M1026 | Privileged Account Management |
Limit the number of accounts permitted to create other accounts. Limit the usage of local administrator accounts to be used for day-to-day operations that may expose them to potential adversaries. |
| ID | Name | Analytic ID | Analytic Description |
|---|---|---|---|
| DET0447 | T1136.001 Detection Strategy - Local Account Creation Across Platforms | AN1235 |
Adversary uses built-in tools like 'net user /add', PowerShell, or WMI to create a local user. Sequence: Account creation event (4720) follows process creation of a suspicious executable (e.g., powershell.exe or net.exe). |
| AN1236 |
Local user accounts are created via binaries like 'useradd', 'adduser', or by editing passwd/shadow. Behavior chain includes execution of user management binaries or modification of user database files. |
||
| AN1237 |
Account creation using 'dscl -create' or via GUI tools. Detection involves command execution and file changes to the local directory services database. |
||
| AN1238 |
Account created using esxcli commands. Sequence includes esxcli execution and successful modification to account DB. |
||
| AN1239 |
Account created in a running container (e.g., via 'useradd' or by modifying /etc/passwd directly). Detectable via runtime telemetry (e.g., Falco or eBPF hooks). |
||
| AN1240 |
Account created via CLI using 'username' command or REST API. Detectable through AAA logging or CLI history telemetry. |