<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Powershell on Vanilla InfoSec</title>
    <link>/tags/powershell/</link>
    <description>Recent content in Powershell on Vanilla InfoSec</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 16 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/powershell/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Remote Thread Injection - Writing a Powershell Shellcode Loader</title>
      <link>/posts/remote-thread-injection---writing-a-powershell-shellcode-loader/</link>
      <pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate>
      <guid>/posts/remote-thread-injection---writing-a-powershell-shellcode-loader/</guid>
      <description>Process Injection in Practice: PowerShell Remote Thread Injection In the previous article, we explored what exactly process injection is, why it is used, and how blue teams attempt to detect it. In this post, we move from theory into practice by walking through a real-world example of the classic Remote Thread Injection technique, implemented using PowerShell.&#xA;This example is intentionally straightforward and educational. It does not attempt to evade EDR, bypass AMSI, or conceal behavior whatsoever.</description>
    </item>
  </channel>
</rss>
