They may change its name, where it sits or its descriptive details. The aim is to avoid being noticed by people and by security tools.
How it works
Attackers copy the look of things that are normally trusted. This can be a name, a storage location or the metadata attached to a file.
Common forms include renaming a system tool, giving a file a misleading type, or naming a task or service so it sounds routine. MITRE lists these as separate sub-techniques.
The idea is simple: a harmful item that looks ordinary is less likely to be questioned during a quick review or a basic security check. MITRE lists 12 sub-techniques: 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.010 Masquerade Account Name, T1036.011 Overwrite Process Arguments and T1036.012 Browser Fingerprint Mimicking.
A real example
- MITRE ATT&CK lists Agrius as renaming a tunneling tool to systems.exe in some cases.
- MITRE ATT&CK lists AppleSeed as able to disguise JavaScript files as PDFs.
- MITRE ATT&CK lists APT28 as renaming the WinRAR utility to avoid detection.
- MITRE ATT&CK lists Dacls as having a Mach-O binary disguised as a .nib file.
- MITRE ATT&CK lists DarkTortilla as having a payload renamed PowerShellInfo.exe.
Seen in incidents
- Incident Kyiv substation attack with Industroyer On 17 December 2016, malware called Industroyer, also known as CrashOverride, disrupted a transmission substation outside Kyiv, Ukraine. December 2016 · Energy and utilities
- Incident SingHealth patient database attack, 2018 Between August 2017 and July 2018 an attacker broke into the network of SingHealth, Singapore's largest public healthcare group, and copied the records of almost 1.5 million patients, mainly names, ID numbers, addresses and dates of birth. August 2017 to July 2018 · Healthcare
How to detect
-
Look for mismatches
Compare what an item claims to be with how it behaves. A file whose name, metadata or icon does not fit its actual execution is a warning sign.
-
Unusual placement
Watch for programs or scripts with familiar names sitting in uncommon folders, or names that use odd characters.
-
Services, bundles and images
Check for services with legitimate-sounding names, application bundles with inconsistent details, and renamed container images.
-
Data sources MITRE lists
Command Execution, File Metadata, File Modification, Image Metadata, Process Creation, Process Metadata, Service Creation, Service Metadata
How to defend
-
Require signed software
Allow only signed binaries and images, so a renamed unsigned file is less likely to run.
-
Control what can run
Use application controls that judge a program by more than its file name.
-
Protect system folders
Use file and directory permissions to guard important system locations.
-
Audit accounts and train users
Review accounts for a defined purpose, enforce account naming rules and train people not to open suspicious attachments or links.
Frequently Asked Questions
What is masquerading in cyber attacks?
Masquerading (T1036) is when an attacker changes how a file, program, service or account looks so it seems legitimate, for example by changing its name, location or descriptive details.
What forms does masquerading take?
Common forms include renaming a system tool, giving a file a misleading type, or naming a task or service so it sounds routine. MITRE lists these as separate sub-techniques.
How can I detect masquerading?
Compare what an item claims to be with how it behaves. Watch for familiar names in uncommon folders, services with legitimate-sounding names and renamed container images.
How do I defend against masquerading?
Allow only signed software, use application controls that judge a program by more than its name, protect system folders with permissions, and train people not to open suspicious attachments.
