<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
  xmlns:atom="http://www.w3.org/2005/Atom"
  xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>XPN InfoSec Blog</title>
    <link>https://blog.xpnsec.com/</link>
    
    <image>
      <url>https://blog.xpnsec.com/images/profile-image.jpg</url>
      <title>XPN InfoSec Blog</title>
      <link>https://blog.xpnsec.com/</link>
    </image>
    
    <atom:link href="https://blog.xpnsec.com/rss.xml" rel="self" type="application/rss+xml"/>
    
    <description></description>
    <pubDate>Sat, 03 Jan 2026 20:12:35 GMT</pubDate>
    <generator>https://blog.xpnsec.com/</generator>
    <ttl>60</ttl>
    
    <item>
      <title>An Evening with Claude (Code)</title>
      <link>https://blog.xpnsec.com/An-Evening-with-Claude-Code/</link>
      <guid isPermaLink="false"></guid>
      <pubDate>Sat, 29 Nov 2025 19:19:16 GMT</pubDate>
      
      <description>A deep dive into discovering CVE-2025-64755, a vulnerability in Claude Code v2.0.25. This post walks through the process of reversing the obfuscated Claude Code JavaScript, and exploiting weak regex expressions to achieve code execution unprompted.</description>
      
      
      <enclosure url="https://assets.xpnsec.com/an-evening-with-claude-code/cover.webp" type="image"/>
      
      
      
      
      <category domain="https://blog.xpnsec.com/tags/claude/">claude</category>
      
      <category domain="https://blog.xpnsec.com/tags/llm/">llm</category>
      
      <category domain="https://blog.xpnsec.com/tags/mcp/">mcp</category>
      
      <category domain="https://blog.xpnsec.com/tags/vulnerability/">vulnerability</category>
      
      <category domain="https://blog.xpnsec.com/tags/cve/">cve</category>
      
    </item>
    
    <item>
      <title>Administrator Protection Review</title>
      <link>https://blog.xpnsec.com/administrator-protection/</link>
      <guid isPermaLink="false"></guid>
      <pubDate>Fri, 20 Jun 2025 23:01:46 GMT</pubDate>
      
      <description>Microsoft will be introducing Administrator Protection into Windows 11, so I wanted to have an understanding of how this technology works and how it interacts with existing offensive tooling. While this technology is just a thin wrapper around a separate account, there are a few nuances such as who is permitted to access these accounts, as well as existing UAC bypasses which are still effective against the new &quot;backdoorless&quot; Administrator Protection. This post explores these nuances in detail.</description>
      
      
      <enclosure url="https://assets.xpnsec.com/administrator-protection/title.png" type="image"/>
      
      
      
      
      <category domain="https://blog.xpnsec.com/tags/redteam/">redteam</category>
      
      <category domain="https://blog.xpnsec.com/tags/windows/">windows</category>
      
      <category domain="https://blog.xpnsec.com/tags/reversing/">reversing</category>
      
    </item>
    
    <item>
      <title>Tokenization Confusion</title>
      <link>https://blog.xpnsec.com/tokenization-confusion/</link>
      <guid isPermaLink="false"></guid>
      <pubDate>Wed, 04 Jun 2025 23:01:46 GMT</pubDate>
      
      <description>In this post we look at the new Prompt Guard 2 model from Meta, and introduce a concept I&#39;ve been calling &quot;Tokenization Confusion&quot; which aims to confuse Unigram tokenization into generating tokens which will result in the misclassification of malicious prompts. We&#39;ll also look at why building up our ML knowledge will lead to better findings when assessing LLM API’s, as I discovered during a flight across the Atlantic.</description>
      
      
      <enclosure url="https://assets.xpnsec.com/tokenization-confusion/title.png" type="image"/>
      
      
      
      
      <category domain="https://blog.xpnsec.com/tags/llm/">llm</category>
      
      <category domain="https://blog.xpnsec.com/tags/machine-learning/">machine-learning</category>
      
    </item>
    
    <item>
      <title>The SQL Server Crypto Detour</title>
      <link>https://blog.xpnsec.com/the-sql-server-crypto-detour/</link>
      <guid isPermaLink="false"></guid>
      <pubDate>Wed, 16 Apr 2025 23:01:46 GMT</pubDate>
      
      <description>One of the things that I love about my role at SpecterOps is getting to dig into various technologies and seeing the resulting research being used in real-time. This post will explore one such story of how I was able to go from a simple request of recovering credentials from a database backup, to reverse engineering how SQL Server encryption works, finding some new methods of brute-forcing database encryption keys.. and finally identifying a mistake in ManageEngine’s ADSelfService product which allows encrypted database backups to reveal privileged credentials.</description>
      
      
      <enclosure url="https://assets.xpnsec.com/sql-server-crypto-detour/title.jpg" type="image"/>
      
      
      
      
      <category domain="https://blog.xpnsec.com/tags/redteam/">redteam</category>
      
      <category domain="https://blog.xpnsec.com/tags/sqlserver/">sqlserver</category>
      
    </item>
    
    <item>
      <title>ADFS - Living in the Legacy of DRS</title>
      <link>https://blog.xpnsec.com/ADFS-Living-in-the-Legacy-of-DRS/</link>
      <guid isPermaLink="false"></guid>
      <pubDate>Sun, 12 Jan 2025 23:01:46 GMT</pubDate>
      
      <description>In this post we’re going to focus on some ADFS internals. We’ll be looking at OAuth2, and how it underpins the analogues to Entra ID security features like Device Registration and Primary Refresh Tokens.</description>
      
      
      <enclosure url="https://assets.xpnsec.com/adfs-living-in-the-legacy-of-drs/image%2020.png" type="image"/>
      
      
      
      
      <category domain="https://blog.xpnsec.com/tags/adfs/">adfs</category>
      
      <category domain="https://blog.xpnsec.com/tags/redteam/">redteam</category>
      
      <category domain="https://blog.xpnsec.com/tags/oauth2/">oauth2</category>
      
    </item>
    
  </channel>
</rss>
