<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Win32 on NTNINJA</title><link>https://ntninja.com/tags/win32/</link><description>Recent content in Win32 on NTNINJA</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Ryan Johnson</copyright><lastBuildDate>Fri, 06 Feb 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://ntninja.com/tags/win32/index.xml" rel="self" type="application/rss+xml"/><item><title>WinDBG MCP with WEDP</title><link>https://ntninja.com/posts/windbg-mcp-with-wedp/</link><pubDate>Fri, 06 Feb 2026 09:00:00 -0500</pubDate><guid>https://ntninja.com/posts/windbg-mcp-with-wedp/</guid><description>&lt;p&gt;I have been late to the game with adopting GenAI into my workflow, but we are at full steam now.
I have slowly been adding it into my daily routines to see where I can gain efficiency leveraging this new tech.
One of the big areas I am playing with right now is for writing Windows based CTF challenges, and now in the past few days, seeing how I can leverage GenAI for writing POCs for these new challenges.
In this post we are going to walk through my initial setup for using the &lt;a href="https://github.com/NadavLor/windbg-ext-mcp" target="_blank" rel="noreferrer"&gt;WinDbg EXT MCP&lt;/a&gt; to control a windbg instance that has the extension I wrote a long time ago, &lt;a href="https://gitlab.com/ntninja-dev/windows-exploit-development/wedp" target="_blank" rel="noreferrer"&gt;WEDP (Windows Exploit Development Plugin)&lt;/a&gt;, to improve the process of going from crash to POC.&lt;/p&gt;</description></item><item><title>rundll... more like fundll</title><link>https://ntninja.com/posts/rundll-fundll/</link><pubDate>Sun, 25 Sep 2022 09:00:00 -0500</pubDate><guid>https://ntninja.com/posts/rundll-fundll/</guid><description>&lt;p&gt;Have you ever written a DLL that had standalone functionality and wasn&amp;rsquo;t meant to be used as a library?
Considering that library is in the name, this idea seems contrary to what a library should be.
Well, you can thank Microsoft for providing a way to execute standalone functionality from a DLL.
Not only did they do that, they also provide DLLs with functionality that you need this utility to run!!!
Say hello to rundll32, pronounced run dull all smashed as one word in some circles.&lt;/p&gt;</description></item></channel></rss>