<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nick Zero</title><link>https://nickzero.co.uk/</link><description>Recent content on Nick Zero</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Mon, 20 Jul 2026 10:00:00 +0100</lastBuildDate><atom:link href="https://nickzero.co.uk/index.xml" rel="self" type="application/rss+xml"/><item><title>Automating Exploit Discovery with MCP: Ghidra, WinDbg and a Very Broken TCP Server</title><link>https://nickzero.co.uk/posts/automating-exploit-discovery-with-mcp/</link><pubDate>Mon, 20 Jul 2026 10:00:00 +0100</pubDate><guid>https://nickzero.co.uk/posts/automating-exploit-discovery-with-mcp/</guid><description>&lt;p&gt;Exploit development is mostly alt-tabbing. You find an address in Ghidra, paste it into&#10;WinDbg, read a register, go back to Ghidra to work out what that register meant, and&#10;somewhere in the middle of all that you forget whether the offset was 104 or 140. It&amp;rsquo;s an enormous amount of very precise clerical work, and humans are&#10;famously excellent at that.&lt;/p&gt;&#10;&lt;p&gt;Reverse engineering and exploit dev are tool-driven activities. We live in a disassembler&#10;and a debugger, and most of the job is asking those two tools very specific questions.&#10;What calls &lt;code&gt;memcpy&lt;/code&gt;? What&amp;rsquo;s at this address? What&amp;rsquo;s in RCX when we crash? How far is it&#10;from the buffer to the saved return address?&lt;/p&gt;</description></item><item><title>Automating a Red Team Lab (Part 2): Monitoring and Logging</title><link>https://nickzero.co.uk/posts/automating-a-red-team-lab-part-2/</link><pubDate>Tue, 15 Mar 2022 07:33:28 +0000</pubDate><guid>https://nickzero.co.uk/posts/automating-a-red-team-lab-part-2/</guid><description>&lt;p&gt;In our &lt;a href="https://nickzero.co.uk/posts/automating-a-red-team-lab/"&gt;previous post&lt;/a&gt; we used Packer, Ansible and Terraform to automate the creation of a domain on our ESXi server. This is great for testing out tools and techniques, but as red teamers we really need to see what&amp;rsquo;s going on behind the scenes in the event logs so that when the blue team kick in our front door, we know exactly where we went wrong.&lt;/p&gt;&#10;&lt;p&gt;In this post we&amp;rsquo;ll cover adding in some monitoring services so that we can trace events. In order to achieve this, we&amp;rsquo;re going to add an Ubuntu server to our lab, and install the ELK stack across the network. As before, we&amp;rsquo;re going to do all this automagically using Infrastructure-as-Code, because as the old saying goes:&lt;/p&gt;</description></item><item><title>Automating a Red Team Lab (Part 1): Domain Creation</title><link>https://nickzero.co.uk/posts/automating-a-red-team-lab/</link><pubDate>Thu, 17 Feb 2022 13:03:18 +0000</pubDate><guid>https://nickzero.co.uk/posts/automating-a-red-team-lab/</guid><description>&lt;p&gt;If you&amp;rsquo;re anything like me, you will tend to rip your test lab down and build it again at least once a day. Whilst this is definitely great fun and an efficient usage of your time, wouldn&amp;rsquo;t it be amazing to just have a fire and forget script that will set it up exactly how you want, every time?&lt;/p&gt;&#10;&lt;p&gt;Luckily this is achievable using Infrastructure-as-Code! In this post, I&amp;rsquo;m going to go over how we can use Packer, Terraform and Ansible to go from an empty ESXi server to an up and running Windows domain in no time.&lt;/p&gt;</description></item><item><title>About</title><link>https://nickzero.co.uk/about/</link><pubDate>Fri, 11 Feb 2022 14:13:20 +0000</pubDate><guid>https://nickzero.co.uk/about/</guid><description>&lt;p&gt;Nick is a hacker, penetration tester and red team consultant.&lt;/p&gt;&#10;&lt;p&gt;This blog is a collection of things I found interesting enough to write about; during my&#10;ventures, work and research.&lt;/p&gt;&#10;&lt;p&gt;You can get in touch via Twitter &lt;a href="https://twitter.com/_nickzer0"&gt;@_NickZero&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>