T1136.001

Local Account

Adversaries may create a local account to maintain persistent access to victim systems. Local accounts can be created using built-in OS commands such as net user /add (Windows), useradd or adduser (Linux), or dscl -create (macOS). Adversaries including Wizard Spider, APT5, Fox Kitten, TeamTNT, and FIN13 have used this technique to establish secondary access that survives credential rotation and does not require persistent remote access tools. Created accounts are often added to the local Administrators group to maximize their utility. Common naming patterns observed in the wild include service-like names (supportaccount, HelpAssistant) designed to blend with legitimate accounts.

Microsoft Sentinel / Defender
kusto
// Branch 1: Windows Security Event 4720 — A user account was created
let AccountCreationEvents = SecurityEvent
| where TimeGenerated > ago(24h)
| where EventID == 4720
| extend CreatedAccount = TargetUserName
| extend CreatedBy = SubjectUserName
| extend CreatedByDomain = SubjectDomainName
| extend CreatedOnHost = Computer
| project TimeGenerated, EventID, CreatedAccount, CreatedBy, CreatedByDomain, CreatedOnHost, Activity;
// Branch 2: Account added to local Administrators or privileged group (Event 4732) within 10 minutes of creation
let GroupAddEvents = SecurityEvent
| where TimeGenerated > ago(24h)
| where EventID == 4732
| where TargetUserName in~ ("Administrators", "Remote Desktop Users", "Remote Management Users", "Backup Operators")
| extend AddedAccount = MemberName
| extend AddedToGroup = TargetUserName
| extend AddedBy = SubjectUserName
| project TimeGenerated, EventID, AddedAccount, AddedToGroup, AddedBy, Computer;
// Branch 3: Process-based detection — net user /add via command line
let NetUserAddEvents = DeviceProcessEvents
| where Timestamp > ago(24h)
| where (FileName =~ "net.exe" or FileName =~ "net1.exe")
| where ProcessCommandLine has_any ("user ", "/add")
| where ProcessCommandLine has "/add"
| extend SuspiciousParent = InitiatingProcessFileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "wscript.exe", "cscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe")
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, SuspiciousParent;
// Combine and surface all results
union
  (AccountCreationEvents | extend DetectionBranch = "SecurityEvent_4720"),
  (GroupAddEvents | extend DetectionBranch = "SecurityEvent_4732_GroupAdd"),
  (NetUserAddEvents | extend DetectionBranch = "DeviceProcessEvents_NetUserAdd")
| sort by TimeGenerated desc
high severity high confidence

Data Sources

User Account: User Account Creation Process: Process Creation Command: Command Execution Microsoft Defender for Endpoint Windows Security Event Log

Required Tables

SecurityEvent DeviceProcessEvents

False Positives

  • IT helpdesk or system administrators creating local service accounts for new application deployments or onboarding workflows
  • Software installers (e.g., SQL Server, IIS, application suites) that create dedicated local service accounts during setup
  • Configuration management tooling (Ansible, Chef, Puppet, DSC) that enforces a local account policy and creates or recreates accounts as part of a run
  • Domain join workflows that briefly create local accounts before applying domain policy
  • Automated provisioning systems creating local break-glass administrator accounts per a documented runbook

Unlock Pro Content

Get the full detection package for T1136.001 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections