Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Adversaries may attempt to manipulate features of their artifacts to make them appear legitimate or benign to users and/or security tools.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-03 | ✗→✓ | ▲ Improved | 68% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 16% | 0% |
| case-10 | ✗→✓ | ▲ Improved | 36% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 64% | 0% |
| case-13 | ✗→✓ | ▲ Improved | -20% | 0% |
Adversaries may attempt to manipulate features of their artifacts to make them appear legitimate or benign to users and/or security tools. Masquerading occurs when the name or location of an object, legitimate or malicious, is manipulated or abused for the sake of evading defenses and observation. This may include manipulating file metadata, tricking users into misidentifying the file type, and giving legitimate task or service names.
Renaming abusable system utilities to evade security monitoring is also a form of Masquerading.
Platforms: Containers, ESXi, Linux, macOS, Windows
The following tests are from Atomic Red Team and provide actionable ways to test this technique:
It may be suspicious seeing a file copy of an EXE in System32 or SysWOW64 to a non-system directory or executing from a non-system directory.
Supported Platforms: windows
powershellcopy-item "$env:windir\System32\cmd.exe" -destination "$env:allusersprofile\cmd.exe" start-process "$env:allusersprofile\cmd.exe" sleep -s 5 stop-process -name "cmd" | out-null
When the file is unzipped and the README.cmd file opened, it executes and changes the .pdf to .dll and executes the dll. This is a BazaLoader technique as reported here
Supported Platforms: windows
powershellExpand-Archive -Path "PathToAtomicsFolder\..\ExternalPayloads\T1036.zip" -DestinationPath "$env:userprofile\Downloads\T1036" -Force cd "$env:userprofile\Downloads\T1036" cmd /c "$env:userprofile\Downloads\T1036\README.cmd" >$null 2>$null
Dependencies:
If Atomic Red Team tests are not applicable, manually verify the technique by:
Audit user accounts to ensure that each one has a defined purpose.
Consider defining and enforcing a naming convention for user accounts to more easily spot generic account names that do not fit the typical schema.
Train users not to open email attachments or click unknown links (URLs). Such training fosters more secure habits within your organization and will limit many of the risks.
Require signed binaries.
Implement security controls on the endpoint, such as a Host Intrusion Prevention System (HIPS), to identify and prevent execution of potentially malicious files (such as those with mismatching file signatures).
Use file system access controls to protect folders such as C:\\Windows\\System32.
Anti-virus can be used to automatically quarantine suspicious files.
Use tools that restrict program execution via application control by attributes other than file name for common operating system utilities that are needed.
| Finding | Severity | Impact | | --------------------------------- | -------- | --------------- | | Masquerading technique applicable | Low | Defense Evasion |
| CWE ID | Title | | ------- | ---------------------------- | | CWE-693 | Protection Mechanism Failure |
Other measured skills in the registry, with their headline benchmark lift.