<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows on Thaddeus Koenig</title><link>https://www.thaddeuskoenig.com/tags/windows/</link><description>Recent content in Windows on Thaddeus Koenig</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Thaddeus Koenig</copyright><lastBuildDate>Wed, 12 Feb 2025 11:33:30 -0500</lastBuildDate><atom:link href="https://www.thaddeuskoenig.com/tags/windows/index.xml" rel="self" type="application/rss+xml"/><item><title>06FEB25 - DLL Hijacking</title><link>https://www.thaddeuskoenig.com/blog/20250206/</link><pubDate>Thu, 06 Feb 2025 06:30:00 -0500</pubDate><guid>https://www.thaddeuskoenig.com/blog/20250206/</guid><description>&lt;p&gt;Today I was looking at something new to learn and I came accross some material on DLL Hijacking. Previously I was only really aware of DLL search order hijacking, but I was interested to see that theres actually several varients to this idea. It may be best to first explain what a DLL is before talking about methods of manipulation. A DLL is a shared object or a snippet of code that several applications and operating system components can import for many common functions as to not have to re-invent the wheel on many things. Since many vital applications and operating system components need these DLLs, there is an opportunity for arbitrary code execution if you can somehow influence an application to load your DLL. There are many techniques to do so, many of them are very similar so I categorize them as such:&lt;/p&gt;</description></item></channel></rss>