Book Image

Windows APT Warfare

By : Sheng-Hao Ma
5 (2)
Book Image

Windows APT Warfare

5 (2)
By: Sheng-Hao Ma

Overview of this book

An Advanced Persistent Threat (APT) is a severe form of cyberattack that lies low in the system for a prolonged time and locates and then exploits sensitive information. Preventing APTs requires a strong foundation of basic security techniques combined with effective security monitoring. This book will help you gain a red team perspective on exploiting system design and master techniques to prevent APT attacks. Once you’ve understood the internal design of operating systems, you’ll be ready to get hands-on with red team attacks and, further, learn how to create and compile C source code into an EXE program file. Throughout this book, you’ll explore the inner workings of how Windows systems run and how attackers abuse this knowledge to bypass antivirus products and protection. As you advance, you’ll cover practical examples of malware and online game hacking, such as EXE infection, shellcode development, software packers, UAC bypass, path parser vulnerabilities, and digital signature forgery, gaining expertise in keeping your system safe from this kind of malware. By the end of this book, you’ll be well equipped to implement the red team techniques that you've learned on a victim's computer environment, attempting to bypass security and antivirus products, to test its defense against Windows APT attacks.
Table of Contents (17 chapters)
1
Part 1 – Modern Windows Compiler
5
Part 2 – Windows Process Internals
9
Part 3 – Abuse System Design and Red Team Tips

Thread Environment Block (TEB)

TEB is one of Microsoft’s unpublished structures. The contents listed in Figure 3.4 here are extracted from Undocumented 32-bit PEB and TEB Structures (bytepointer.com/resources/tebpeb32.htm):

Figure 3.4 – TEB structure

Figure 3.4 – TEB structure

These are the partial contents of the TEB after 32-bit reverse engineering. The total size of TEB is as large as 0xFF8. However, for the sake of explanation, we will only mention the 0x30 bytes at the beginning, and the other parts are for Windows internal implementation.

As we mentioned in Chapter 2, Process Memory – File Mapping, PE Parser, tinyLinker, and Hollowing, when each process is generated, there must be a PEB stored in the process memory to record the details of the process being generated. And what about threads? Yes. Let’s take the multithread concept that you have studied in your operating system class. If there are multiple threads running in parallel in the same...