<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>pwn.dog</title><link>https://pwn.dog/</link><description>Recent content on pwn.dog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 02 Jun 2026 20:00:00 +0000</lastBuildDate><atom:link href="https://pwn.dog/index.xml" rel="self" type="application/rss+xml"/><item><title>Indistinguishable: What VAC Checks For, and Why Anti-Lag+ Never Stood a Chance</title><link>https://pwn.dog/posts/indistinguishable-what-vac-checks/</link><pubDate>Tue, 02 Jun 2026 20:00:00 +0000</pubDate><guid>https://pwn.dog/posts/indistinguishable-what-vac-checks/</guid><description>Finale of the Anti-Lag+ teardown. We mapped the feature byte-for-byte; now we line it up against what Valve Anti-Cheat is publicly known to look for. Every single signal a cheat trips, Anti-Lag+ tripped too - because at the instruction level they were the same thing.</description></item><item><title>The Control Plane: How One Byte in a Profile Blob Disabled Anti-Lag+</title><link>https://pwn.dog/posts/the-control-plane-atiapfxx-blb/</link><pubDate>Tue, 02 Jun 2026 16:00:00 +0000</pubDate><guid>https://pwn.dog/posts/the-control-plane-atiapfxx-blb/</guid><description>Part 3 of the Anti-Lag+ teardown. The hook lived in code - but the on/off switch was data. Reverse-engineering AMD&amp;rsquo;s per-game application-profile database (atiapfxx.blb / the BWJE format) and the single byte that turned the feature off.</description></item><item><title>The Engine Room: AMD's Detours-Based Hook Library (amdihk64)</title><link>https://pwn.dog/posts/the-hook-engine-amdihk64/</link><pubDate>Tue, 02 Jun 2026 12:00:00 +0000</pubDate><guid>https://pwn.dog/posts/the-hook-engine-amdihk64/</guid><description>Part 2 of the Anti-Lag+ teardown. A deep dive into amdihk64 - a Microsoft Detours-based inline-hook engine that ships in the same driver package and also hooks raw input. It&amp;rsquo;s a sibling to the Delag detour from Part 1; I couldn&amp;rsquo;t prove it&amp;rsquo;s on the Anti-Lag+ path itself, and I say so.</description></item><item><title>Detouring Yourself Into a Ban: Reverse-Engineering AMD Anti-Lag+</title><link>https://pwn.dog/posts/detouring-yourself-into-a-ban/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://pwn.dog/posts/detouring-yourself-into-a-ban/</guid><description>A symbol-level teardown of the Adrenalin 23.10.1 feature that got Counter-Strike 2 players VAC-banned - what it hooked, how it hooked it, and the single byte that turned it off.</description></item><item><title>about</title><link>https://pwn.dog/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pwn.dog/about/</guid><description>&lt;p&gt;&lt;strong&gt;pwn.dog&lt;/strong&gt; is a reverse-engineering notebook - driver teardowns, anti-cheat
internals, exploitation, and debugging write-ups. Mostly low-level Windows
internals and whatever rabbit hole is open this week.&lt;/p&gt;
&lt;p&gt;Everything here is research and documentation only.&lt;/p&gt;</description></item></channel></rss>