T1036.010sub-technique of T1036 Masquerading
Masquerade Account Name
Containers · IaaS · Identity Provider · Linux · macOS · Office Suite · SaaS · Windowsnothing on this site yetT1036.010 on attack.mitre.org
Adversaries may match or approximate the names of legitimate accounts to make newly created ones appear benign. This will typically occur during Create Account, although accounts may also be renamed at a later date. This may also coincide with Account Access Removal if the actor first deletes an account before re-creating one with the same name.
how MITRE says to see it
Detection Strategy for Masquerading via Account Name Similarity
- Detects adversary behavior where a newly created or renamed user account closely resembles existing service or administrator accounts to blend in and avoid detection. Common patterns include prefix/suffix modifications, homoglyphs, or use of names like 'admin1', 'adm1n', or 'backup_help'.
- Detects creation or renaming of accounts with names that closely match known service, root, or admin accounts. Behavior often follows account discovery or deletion, attempting to blend into system activity logs using trusted name conventions.
- Detects adversary creation of cloud or IdP accounts whose names resemble existing privileged or service accounts. May indicate preparation for privilege escalation or defense evasion.
- Monitors for the creation of accounts inside containers using names that resemble legitimate orchestrator or backup identities to mask adversary persistence.
what reduces it
the rest of T1036
- T1036.001 Invalid Code Signature
- T1036.002 Right-to-Left Override
- T1036.003 Rename Legitimate Utilities
- T1036.004 Masquerade Task or Service
- T1036.005 Match Legitimate Resource Name or Location
- T1036.006 Space after Filename
- T1036.007 Double File Extension
- T1036.008 Masquerade File Type
- T1036.009 Break Process Trees
- T1036.011 Overwrite Process Arguments
- T1036.012 Browser Fingerprint