Exploit Data Added

Classic_Code_Injection_API_Obfuscate/readme.md

@@ -513,7 +513,7 @@ int main(int argc, char* argv[]) {
 
 ## Demonstration
 
-![](Assets/apiobf.gif)
+![](Asset/PE3.gif)
 
 For GitHub-Repo Click Here: [Offensive-Panda/ProcessInjectionTechniques](https://github.com/Offensive-Panda/ProcessInjectionTechniques/tree/main/Classic_Code_Injection_API_Obfuscate/Classic_Code_Injection_API_Obfuscate)
 

Classic_Code_Injection_Remote/readme.md

@@ -415,7 +415,7 @@ int main(int argc, char* argv[]) {
 
 ## Demonstration
 
-![](Assets/ccir.gif)
+![](Asset/PE2.gif)
 
 For GitHub-Repo Click Here: [Offensive-Panda/ProcessInjectionTechniques](https://github.com/Offensive-Panda/ProcessInjectionTechniques/tree/main/Classic_Code_Injection_Remote/Classic_Code_Injection_Remote)
 

Classic_Code_Injection_Remote_VP/readme.md

@@ -424,7 +424,7 @@ int main(int argc, char* argv[]) {
 
 ## Demonstration
 
-![](Assets/ccir.gif)
+![](Asset/PE4.gif)
 
 For GitHub-Repo Click Here: [Offensive-Panda/ProcessInjectionTechniques](https://github.com/Offensive-Panda/ProcessInjectionTechniques/tree/main/Classic_Code_Injection_Remote_VP/Classic_Code_Injection_Remote_VP)
 

Classic_DLL_Injection/readme.md

@@ -559,7 +559,7 @@ BOOL WINAPI DllMain(HINSTANCE hinstDLL, DWORD fdwReason, LPVOID lpReserved) {
 
 ## Demonstration
 
-![](Assets/cdll.gif)
+![](Asset/PE5.gif)
 
 For GitHub-Repo Click Here: [Offensive-Panda/ProcessInjectionTechniques](https://github.com/Offensive-Panda/ProcessInjectionTechniques/tree/main/Classic_DLL_Injection/Classic_DLL_Injection)
 

Reflective_DLL_Injection/readme.md

@@ -604,7 +604,7 @@ BOOL WINAPI DllMain(HINSTANCE hinstDLL, DWORD fdwReason, LPVOID lpReserved) {
 
 ## Demonstration
 
-![](Assets/rdll.gif)
+![](Asset/PE6.gif)
 
 For GitHub-Repo Click Here: [Offensive-Panda/ProcessInjectionTechniques](https://github.com/Offensive-Panda/ProcessInjectionTechniques/tree/main/Reflective_DLL_Injection/Reflective_DLL_Injection)
 

index.html

@@ -83,7 +83,7 @@ layout: default
         }
         .card p {
             font-size: 1em;
-            color: #555;
+            color: #f4efef;
             margin-left: 120px;
         }
       body {
@@ -184,35 +184,35 @@ layout: default
             <p>In this lab, we cover classic code injection in local process technique. This technique uses Windows API calls to allocate memory in local Process, write the shellcode to the allocated memory, and then execute it.</p>
         </a>
 
-            <a href="pe1.html" class="card">
+            <a href="Classic_Code_Injection_Remote" class="card">
             <h3>PE 2 - Classic Code Injection Remote Process</h3>
             <img src="Assets/classic-remote.jpg" alt="Technique Image" class="technique-image">
             <img src="Assets/windows-icon.png" class="windows-icon" alt="Windows Icon">
             <p>In this lab, we cover classic code injection in remote process. This is one of the most straightforward forms of process injection technique also known as Remote Thread Injection. This method involves creating a new thread in a remote process and executing the payload or shellcode within that context. This is often done using Windows API functions such as OpenProcess, VirtualAllocEx, WriteProcessMemory, and CreateRemoteThread.</p>
         </a>
            
-            <a href="pe1.html" class="card">
+            <a href="Classic_Code_Injection_API_Obfuscate" class="card">
             <h3>PE 3 - Classic Code Injection with API Obfuscation</h3>
             <img src="Assets/api-obf.jpg" alt="Technique Image" class="technique-image">
             <img src="Assets/windows-icon.png" class="windows-icon" alt="Windows Icon">
             <p>In this lab, we cover the remote thread injection technique with APIs obfuscation. To evade static detection mechanisms used by AV/EDR solutions, we will implement API call obfuscation throughout the process. By the end of this lab, we'll demonstrate the difference in the import table of a sample program both before and after API obfuscation, highlighting how these changes can help to bypass static analysis.</p>
         </a>
            
-            <a href="pe1.html" class="card">
+            <a href="Classic_Code_Injection_Remote_VP" class="card">
             <h3>PE 4 - Classic Code Injection VirtualProtect</h3>
             <img src="Assets/ccvp_AI.jpg" alt="Technique Image" class="technique-image">
             <img src="Assets/windows-icon.png" class="windows-icon" alt="Windows Icon">
             <p>In this lab, we cover classic code injection in remote process using VirtualProtect. This is the same technique, we discussed in last lab but one extra step is involved in this lab which is to change the permission of allocated memory with Windows API VirtualProtect. Allocating RWX region at a same time is great indicator for AV/EDR solutions, so to avoid RWX region detection, we first create RW and before executing shellcode we change it to RX.</p>
         </a>
 
-            <a href="pe1.html" class="card">
+            <a href="Classic_DLL_Injection" class="card">
             <h3>PE 5 - Classic DLL Injection</h3>
             <img src="Assets/classic-dll.jpg" alt="Technique Image" class="technique-image">
             <img src="Assets/windows-icon.png" class="windows-icon" alt="Windows Icon">
             <p>In this lab, we cover a DLL injection technique that targets a process (in this case, explorer.exe) to load a malicious DLL (panda.dll) from the Downloads folder. DLL injection is a method used to run arbitrary code within the address space of another process by forcing it to load a dynamic-link library (DLL).</p>
         </a>
            
-            <a href="pe1.html" class="card">
+            <a href="Reflective_DLL_Injection" class="card">
             <h3>PE 6 - Reflective DLL Injection</h3>
             <img src="Assets/rdll_AI.jpg" alt="Technique Image" class="technique-image">
             <img src="Assets/windows-icon.png" class="windows-icon" alt="Windows Icon">