<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Windows-Internals on proteqtum</title>
    <link>https://proteqtum.com/tags/windows-internals/</link>
    <description>Recent content in Windows-Internals on proteqtum</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 30 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://proteqtum.com/tags/windows-internals/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Win x64 Shellcode – Part 2: TEB, PEB and List of Loaded Modules</title>
      <link>https://proteqtum.com/posts/02-win-x64-shellcode-teb-peb_en/</link>
      <pubDate>Tue, 30 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://proteqtum.com/posts/02-win-x64-shellcode-teb-peb_en/</guid>
      <description>&lt;p&gt;In the previous part, we explained why shellcode cannot use statically written addresses of Windows API functions. The solution lies in the structures that Windows maintains directly in the memory of each process. Today we will look at them closely.&lt;/p&gt;
&lt;h2 id=&#34;prerequisites&#34;&gt;Prerequisites&lt;/h2&gt;
&lt;p&gt;Before reading this part, it is advisable to read and understand the previous part. At the same time, it is highly advisable to have at least a basic understanding of what virtual memory and a pointer are.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Win x64 Shellcode – Part 1: Why We Can&#39;t Use Static Addresses</title>
      <link>https://proteqtum.com/posts/01-win-x64-shellcode-introduction_en/</link>
      <pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://proteqtum.com/posts/01-win-x64-shellcode-introduction_en/</guid>
      <description>&lt;p&gt;I have a background in writing 32-bit shellcodes for Windows [1][2][3]. The transition to x64 looks like a cosmetic change at first glance (wider registers, a different calling convention). In reality, it is an entirely different mental model.&lt;/p&gt;
&lt;p&gt;The goal of this series is to describe the fundamentals of Win64 shellcode development in a simplified yet comprehensive way. It does not aim to be exhaustive documentation on the topic, but rather to provide accessible learning material that can serve as a stepping stone into this field.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
