

<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://vollragm.github.io/</id>
  <title>VollRagm</title>
  <subtitle>A blog regarding reverse engineering, game hacking and the Windows operating system</subtitle>
  <updated>2025-08-24T02:24:57+02:00</updated>
  <author>
    <name>VollRagm</name>
    <uri>https://vollragm.github.io/</uri>
  </author>
  <link rel="self" type="application/atom+xml" href="https://vollragm.github.io/feed.xml"/>
  <link rel="alternate" type="text/html" hreflang="en"
    href="https://vollragm.github.io/"/>
  <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator>
  <rights> © 2025 VollRagm </rights>
  <icon>/assets/img/favicons/favicon.ico</icon>
  <logo>/assets/img/favicons/favicon-96x96.png</logo>


  
  <entry>
    <title>Developing an undetected debugger on Windows - Part 4 [Evaluation]</title>
    <link href="https://vollragm.github.io/posts/developing-veh-debugger-p4/" rel="alternate" type="text/html" title="Developing an undetected debugger on Windows - Part 4 [Evaluation]" />
    <published>2025-08-23T21:58:00+02:00</published>
  
    <updated>2025-08-23T21:58:00+02:00</updated>
  
    <id>https://vollragm.github.io/posts/developing-veh-debugger-p4/</id>
    <content src="https://vollragm.github.io/posts/developing-veh-debugger-p4/" />
    <author>
      <name>VollRagm</name>
    </author>

  
    
    <category term="Reverse Engineering" />
    
  

  
    <summary>
      





      Part 4 – Evaluation

You are reading Part 4: Evaluation and Results.


  👉 Part 1: Theory
  👉 Part 2: Detection
  👉 Part 3: Implementation


🔗 Explore the complete project here: GhostDebug on GitHub

Evaluation and Results

In this chapter the detectability of the newly developed debugger is examined. First the test environment is described. Then the detectability is measured and compared to cl...
    </summary>
  

  </entry>

  
  <entry>
    <title>Developing an undetected debugger on Windows - Part 3 [Implementation]</title>
    <link href="https://vollragm.github.io/posts/developing-veh-debugger-p3/" rel="alternate" type="text/html" title="Developing an undetected debugger on Windows - Part 3 [Implementation]" />
    <published>2025-08-23T21:56:00+02:00</published>
  
    <updated>2025-08-23T21:56:00+02:00</updated>
  
    <id>https://vollragm.github.io/posts/developing-veh-debugger-p3/</id>
    <content src="https://vollragm.github.io/posts/developing-veh-debugger-p3/" />
    <author>
      <name>VollRagm</name>
    </author>

  
    
    <category term="Reverse Engineering" />
    
  

  
    <summary>
      





      Part 3 – Implementation

You are reading Part 3: Implementation.


  👉 Part 1: Theory
  👉 Part 2: Detection
  👉 Part 4: Evaluation


🔗 Full implementation is available at: GhostDebug on GitHub

Implementation

In this chapter an overview of the requirements for the debugger is given first.
Then the underlying architecture is described, with focus on the division into different components: a deb...
    </summary>
  

  </entry>

  
  <entry>
    <title>Developing an undetected debugger on Windows - Part 2 [Detection]</title>
    <link href="https://vollragm.github.io/posts/developing-veh-debugger-p2/" rel="alternate" type="text/html" title="Developing an undetected debugger on Windows - Part 2 [Detection]" />
    <published>2025-08-23T21:53:00+02:00</published>
  
    <updated>2025-08-23T21:53:00+02:00</updated>
  
    <id>https://vollragm.github.io/posts/developing-veh-debugger-p2/</id>
    <content src="https://vollragm.github.io/posts/developing-veh-debugger-p2/" />
    <author>
      <name>VollRagm</name>
    </author>

  
    
    <category term="Reverse Engineering" />
    
  

  
    <summary>
      





      Part 2 – Detection

You are reading Part 2: Detection.


  👉 Part 1: Theory
  👉 Part 3: Implementation
  👉 Part 4: Evaluation


🔗 Check out the source code here: GhostDebug on GitHub

Reasons for Debugger Detection

Because debuggers allow deep insight into the execution of a program, in many areas there is a desire to prevent debugging. This desire is not limited to malware that wants to make ...
    </summary>
  

  </entry>

  
  <entry>
    <title>Developing an undetected debugger on Windows - Part 1 [Theory]</title>
    <link href="https://vollragm.github.io/posts/developing-veh-debugger/" rel="alternate" type="text/html" title="Developing an undetected debugger on Windows - Part 1 [Theory]" />
    <published>2025-08-23T21:50:00+02:00</published>
  
    <updated>2025-08-23T21:50:00+02:00</updated>
  
    <id>https://vollragm.github.io/posts/developing-veh-debugger/</id>
    <content src="https://vollragm.github.io/posts/developing-veh-debugger/" />
    <author>
      <name>VollRagm</name>
    </author>

  
    
    <category term="Reverse Engineering" />
    
  

  
    <summary>
      





      Part 1 – Theory

You are reading Part 1: Theory.


  👉 Part 2: Detection
  👉 Part 3: Implementation
  👉 Part 4: Evaluation


🔗 The debugger project itself can be found here: GhostDebug on GitHub

Introduction

Debuggers are important tools in software development and in reverse engineering. They make it possible to analyze program execution, find errors, and gain deeper insights into the flow o...
    </summary>
  

  </entry>

  
  <entry>
    <title>Abusing LargePageDrivers to copy shellcode into valid kernel modules</title>
    <link href="https://vollragm.github.io/posts/abusing-large-page-drivers/" rel="alternate" type="text/html" title="Abusing LargePageDrivers to copy shellcode into valid kernel modules" />
    <published>2022-04-10T23:26:00+02:00</published>
  
    <updated>2022-04-12T15:46:29+02:00</updated>
  
    <id>https://vollragm.github.io/posts/abusing-large-page-drivers/</id>
    <content src="https://vollragm.github.io/posts/abusing-large-page-drivers/" />
    <author>
      <name>VollRagm</name>
    </author>

  
    
    <category term="Kernel Development" />
    
  

  
    <summary>
      





      Introduction
Most people in the game hacking community write their kernel-mode drivers to get around kernel-level anti-cheats such as EasyAntiCheat.
However, those anti-cheats have several methods to detect cheat drivers. The most commonly used way to load the cheat driver is manually mapping it with tools like kdmapper. Unfortunately, manually mapping a driver in this way causes the code to be...
    </summary>
  

  </entry>

</feed>


