Masquerading: Match Legitimate Name or Location

admin@338 actors used the following command to rename one of their tools to a benign file name: ren "%temp%\upload" audiodg.exe^[50]

The file name AcroRD32.exe, a legitimate process name for Adobe's Acrobat Reader, was used by APT1 as a name for malware.^[51][52]

APT32 has renamed a NetCat binary to kb-10233.exe to masquerade as a Windows update. APT32 has also renamed a Cobalt Strike beacon payload to install_flashplayers.exe. ^[43]

APT39 has used a tool named mfevtpse.exe to proxy C2 communications, closely mimicking a legitimate McAfee file mfevtps.exe.^[62]

APT41 attempted to masquerade their files as popular anti-virus software.^[57]

BackConfig has hidden malicious payloads in %USERPROFILE%\Adobe\Driver\dwg\ and mimicked the legitimate DHCP service binary.^[42]

BADNEWS attempts to hide its payloads using legitimate filenames.^[23]

Blue Mockingbird has masqueraded their XMRIG payload name by naming it wercplsupporte.dll after the legitimate wercplsupport.dll file.^[61]

BRONZE BUTLER has given malware the same name as an existing file on the file share server to cause users to unwittingly launch and install the malware on additional systems.^[48]

Bundlore has disguised a malicious .app file as a Flash Player update.^[44]

Calisto's installation file is an unsigned DMG image under the guise of Intego’s security solution for mac.^[3]

Carbanak has named malware "svchost.exe," which is the name of the Windows shared service host program.^[47]

ChChes copies itself to an .exe file with a filename that is likely intended to imitate Norton Antivirus but has several letters reversed (e.g. notron.exe).^[6]

DarkComet has dropped itself onto victim machines with file names such as WinDefender.Exe and winupdate.exe in an apparent attempt to masquerade as a legitimate file.^[28]

Daserf uses file and folder names related to legitimate programs in order to blend in, such as HP, Intel, Adobe, and perflogs.^[21]

If installing itself as a service fails, Elise instead writes itself as a file named svchost.exe saved in %APPDATA%\Microsoft\Network.^[4]

Felismus has masqueraded as legitimate Adobe Content Management System files.^[9]

FinFisher renames one of its .dll files to uxtheme.dll in an apparent attempt to masquerade as a legitimate file.^[24][25]

Fysbis has masqueraded as trusted software rsyncd and dbus-inotifier.^[34]

Goopy has impersonated the legitimate goopdate.dll, which was dropped on the target system with a legitimate GoogleUpdate.exe.^[43]

HTTPBrowser's installer contains a malicious file named navlu.dll to decrypt and run the RAT. navlu.dll is also the name of a legitimate Symantec DLL.^[5]

InnaputRAT variants have attempted to appear legitimate by using the file names SafeApp.exe and NeutralApp.exe.^[19]

InvisiMole saves one of its files as mpr.dll in the Windows folder, masquerading as a legitimate library file.^[10]

Ixeshe has used registry values and file names associated with Adobe software, such as AcroRd32.exe.^[30]

KONNI creates a shortcut called "Anti virus service.lnk" in an apparent attempt to masquerade as a legitimate file.^[20]

LightNeuron has used filenames associated with Exchange and Outlook for binary and configuration files, such as winmail.dat.^[31]

Machete renamed payloads to masquerade as legitimate Google Chrome, Java, Dropbox, Adobe Reader and Python executables.^[35]

MechaFlounder has been downloaded as a file named lsass.exe, which matches the legitimate Windows file.^[38]

menuPass has been seen changing malicious files to appear legitimate.^[56]

Metamorfo has disguised an MSI file as the Adobe Acrobat Reader Installer.^[41]

Mis-Type saves itself as a file named msdtc.exe, which is also the name of the legitimate Microsoft Distributed Transaction Coordinator service binary.^[13][14]

Misdat saves itself as a file named msdtc.exe, which is also the name of the legitimate Microsoft Distributed Transaction Coordinator service binary.^[13][14]

MuddyWater has used filenames and Registry key names associated with Windows Defender.^[45][46]

NOKKI is written to %LOCALAPPDATA%\MicroSoft Updatea\svServiceUpdate.exe prior being executed in a new process in an apparent attempt to masquerade as a legitimate folder and file.^[22]

OLDBAIT installs itself in %ALLUSERPROFILE%\Application Data\Microsoft\MediaPlayer\updatewindws.exe; the directory name is missing a space and the file name is missing the letter "o."^[26]

OSX/Shlayer can masquerade as a Flash Player update.^[32][33]

OwaAuth uses the filename owaauth.dll, which is a legitimate file that normally resides in %ProgramFiles%\Microsoft\Exchange Server\ClientAccess\Owa\Auth\; the malicious file by the same name is saved in %ProgramFiles%\Microsoft\Exchange Server\ClientAccess\Owa\bin\.^[15]

Patchwork installed its payload in the startup programs folder as "Baidu Software Update." The group also adds its second stage payload to the startup programs as "Net Monitor."^[53] They have also dropped QuasarRAT binaries as files named microsoft_network.exe and crome.exe.^[54]

Pony has used the Adobe Reader icon for the downloaded file to look more trustworthy.^[37]

Poseidon Group tools attempt to spoof anti-virus processes as a means of self-defense.^[49]

PUNCHBUGGY mimics filenames from %SYSTEM%\System32 to hide DLLs in %WINDIR% and/or %TEMP%.^[16][17]

QUADAGENT used the PowerShell filenames Office365DCOMCheck.ps1 and SystemDiskClean.ps1.^[27]

Ramsay has masqueraded as a 7zip installer.^[39]

The Remsec loader implements itself with the name Security Support Provider, a legitimate Windows function. Various Remsec .exe files mimic legitimate file names used by Microsoft, Symantec, Kaspersky, Hewlett-Packard, and VMWare. Remsec also disguised malicious modules using similar filenames as custom network encryption software on victims.^[11][12]

Rocke has used shell scripts which download mining executables and saves them with the filename "java".^[64]

Ryuk has constructed legitimate appearing installation folder paths by calling GetWindowsDirectoryW and then inserting a null byte at the fourth character of the path. For Windows Vista or higher, the path would appear as C:\Users\Public.^[36]

S-Type may save itself as a file named msdtc.exe, which is also the name of the legitimate Microsoft Distributed Transaction Coordinator service binary.^[13][14]

Sandworm Team has avoided detection by naming a malicious binary explorer.exe.^[63]

ShimRatReporter spoofed itself as AlphaZawgyl_font.exe, a specialized Unicode font.^[1]

Silence has named its backdoor "WINWORD.exe".^[58]

Skidmap has created a fake rm binary to replace the legitimate Linux binary.^[40]

Sowbug named its tools to masquerade as Windows or Adobe Reader software, such as by using the file name adobecms.exe and the directory CSIDL_APPDATA\microsoft\security.^[18]

To establish persistence, SslMM identifies the Start Menu Startup directory and drops a link to its own executable disguised as an "Office Start," "Yahoo Talk," "MSN Gaming Z0ne," or "MSN Talk" shortcut.^[2]

Starloader has masqueraded as legitimate software update packages such as Adobe Acrobat Reader and Intel.^[18]

TEMP.Veles has renamed files to look like legitimate files, such as Windows update files or Schneider Electric application files.^[55]

Tropic Trooper has hidden payloads in Flash directories and fake installer files.^[59]

Ursnif has used strings from legitimate system files and existing folders for its file, folder, and Registry entry names.^[29]

USBStealer mimics a legitimate Russian program called USB Disk Security.^[8]

Whitefly has named the malicious DLL the same name as DLLs belonging to legitimate software from various security vendors.^[60]

A Winnti for Windows implant file was named ASPNET_FILTER.DLL, mimicking the legitimate ASP.NET ISAPI filter DLL with the same name.^[7]

ZLib mimics the resource version information of legitimate Realtek Semiconductor, Nvidia, or Synaptics modules.^[13]

Require signed binaries.

Use tools that restrict program execution via application control by attributes other than file name for common operating system utilities that are needed.

Use file system access controls to protect folders such as C:\Windows\System32.