Adversaries may use [Obfuscated Files or Information](https://attack.mitre.org/techniques/T1027) to hide artifacts of an intrusion from analysis. They may require separate mechanisms to decode or deobfuscate that information depending on how they intend to use it. Methods for doing that include built-in functionality of malware, [Scripting](https://attack.mitre.org/techniques/T1064), [PowerShell](https://attack.mitre.org/techniques/T1086), or by using utilities present on the system.One such example is use of certutil to decode a remote access tool portable executable file that has been hidden inside a certificate file. (Citation: Malwarebytes Targeted Attack against Saudi Arabia)
Another example is using the Windows
copy /b
command to reassemble binary fragments into a malicious payload. (Citation: Carbon Black Obfuscation Sept 2016)Payloads may be compressed, archived, or encrypted in order to avoid detection. These payloads may be used with Obfuscated Files or Information during Initial Access or later to mitigate detection. Sometimes a user's action may be required to open it for deobfuscation or decryption as part of User Execution. The user may also be required to input a password to open a password protected compressed/encrypted file that was provided by the adversary. (Citation: Volexity PowerDuke November 2016) Adversaries may also used compressed or archived scripts, such as Javascript.
Encode/Decode executable
Supported Platforms: Windows
Name | Description | Type | Default Value |
---|---|---|---|
executable | name of executable | path | c:\file.exe |
certutil.exe -encode #{executable} file.txt
certutil.exe -decode file.txt #{executable}
Rename certutil and decode a file. This is in reference to latest research by FireEye here
Supported Platforms: Windows
Name | Description | Type | Default Value |
---|---|---|---|
executable | name of executable/file to decode | path | c:\file.exe |
cmd.exe /c copy %windir%\\system32\\certutil.exe %temp%tcm.tmp
cmd.exe /c %temp%tcm.tmp -decode #{executable} file.txt