Common Information
| Type | Value |
|---|---|
| Value |
Masquerading - T1036 |
| Category | Attack-Pattern |
| Type | Mitre-Enterprise-Attack-Attack-Pattern |
| Misp Type | Cluster |
| Description | Masquerading occurs when the name or location of an executable, legitimate or malicious, is manipulated or abused for the sake of evading defenses and observation. Several different variations of this technique have been observed. One variant is for an executable to be placed in a commonly trusted directory or given the name of a legitimate, trusted program. Alternatively, the filename given may be a close approximation of legitimate programs. This is done to bypass tools that trust executables by relying on file name or path, as well as to deceive defenders and system administrators into thinking a file is benign by associating the name with something that is thought to be legitimate. ===Windows=== In another variation of this technique, an adversary may use a renamed copy of a legitimate utility, such as rundll32.exe. (Citation: Endgame Masquerade Ball) An alternative case occurs when a legitimate utility is moved to a different directory and also renamed to avoid detections based on system utilities executing from non-standard paths. (Citation: F-Secure CozyDuke) An example of abuse of trusted locations in Windows would be the <code>C:\Windows\System32</code> directory. Examples of trusted binary names that can be given to malicious binares include "explorer.exe" and "svchost.exe". ===Linux=== Another variation of this technique includes malicious binaries changing the name of their running process to that of a trusted or benign process, after they have been launched as opposed to before. (Citation: Remaiten) An example of abuse of trusted locations in Linux would be the <code>/bin</code> directory. Examples of trusted binary names that can be given to malicious binares include "rsyncd" and "dbus-inotifier". (Citation: Fysbis Palo Alto Analysis) (Citation: Fysbis Dr Web Analysis) Detection: Collect file hashes; file names that do not match their expected hash are suspect. Perform file monitoring; files with known names but in unusual locations are suspect. Likewise, files that are modified outside of an update or patch are suspect. If file names are mismatched between the binary name on disk and the binary's resource section, this is a likely indicator that a binary was renamed after it was compiled. Collecting and comparing disk and resource filenames for binaries could provide useful leads, but may not always be indicative of malicious activity. (Citation: Endgame Masquerade Ball) Platforms: Linux, macOS, Windows Data Sources: File monitoring, Process monitoring, Binary file metadata Defense Bypassed: Whitelisting by file name or path Contributors: ENDGAME, Bartosz Jerzman |
| Details | Published | Attributes | CTI | Title | ||
|---|---|---|---|---|---|---|
| Details | Website | 2011-04-13 | 8 | This Month in the Threat Webscape - March 2011 | ||
| Details | Website | 2011-03-11 | 0 | Green Skimmers Skimming Green – Krebs on Security | ||
| Details | Website | 2011-02-17 | 103 | Targeted attacks against personal accounts of military, government employees and associates | ||
| Details | Website | 2010-09-08 | 0 | Android SMS Trojan Now Being Delivered via SEO Techniques | ||
| Details | Website | 2010-07-31 | 28 | Quicktime,malicious movies and Angelina Jolie | WeLiveSecurity | ||
| Details | Website | 2010-02-05 | 95 | NIST Special Publication 800-63B | ||
| Details | Website | 2008-06-12 | 0 | New Zlob Trojan Alters Your Router Settings - Darknet - Hacking Tools, Hacker News & Cyber Security |