Skip to content
Ctrl K

Developer highlights

The Case Studies index is organized by CVE: one vulnerability, dissected from root cause to patch. That axis answers "what was the bug". It does not answer "who keeps building working escalations out of these bugs, and how do they think about stringing primitives together".

This section is the second axis. It is organized by the exploit developer, and it is focused on the chain: not the single flaw, but the sequence of primitives that turns a standard-user foothold into SYSTEM, and which defenses that sequence walks past. A developer who ships fifteen exploits in six months is not fifteen unrelated bugs. There is a house style, a reused primitive vocabulary, and a way of composing them that repeats. That pattern is worth studying on its own, because it predicts the next exploit better than any single CVE does.

Why chain-first

KernelSight's thesis is that the individual vulnerability is rarely the interesting part. The interesting part is the composition: coerce a privileged component into acting, redirect where it acts, win or remove the timing, then convert the result into a SYSTEM token. The same five-stage shape recurs across wildly different bugs. A developer-centric view makes that shape visible, because you watch one author apply it to Defender, then to a cloud-filter driver, then to a third-party EDR, changing only the coercion and the redirect while the skeleton stays fixed.

Each profile therefore leads with the chain and treats the bugs as interchangeable parts within it.

How these relate to the kernel focus

Most escalations here reach SYSTEM by coercing a privileged user-mode service rather than by corrupting kernel memory directly. That still belongs in KernelSight for two reasons. First, SYSTEM is the trust level a kernel primitive is usually spent to reach, so these chains arrive at the same destination by a different road, and the which defenses a kernel primitive defeats analysis applies to both. Second, several of the chains do route through kernel drivers: cldflt.sys (the Cloud Filter minifilter) and third-party display drivers appear as links in them, and those have their own case studies. Where a chain touches a driver in the corpus, the profile links to it.

Verdict basis

These profiles are graded cited: they are built from public vendor and press analysis (Huntress, Barracuda, Picus, ThreatLocker, LevelBlue, SecurityWeek, BleepingComputer, The Register), not from independent reversing of the exploit binaries. Where a claim rests only on the developer's own statements, it is marked as such. Nothing here is a repro attestation.

Profiles

Developer Focus Signature Profile
Nightmare-Eclipse Security-product LPE (Defender, cldflt, third-party EDR) Composition over novel bugs; coerce-redirect-race-load-bridge; re-wins narrowed patch windows Read
Lazarus / FudModule Admin-to-kernel, data-only DKOM rootkit Kernel R/W from a Microsoft-signed driver ("beyond BYOVD"), spent only on kernel data to blind EDR Read
Juan Sacco / Exploit Pack DOG Commercial tooling, data-only dispatch hijacking One mechanism, clone-and-repoint, applied to all four kernel dispatch tables; workspace in unmanaged physical memory Read
Volodya / BuggiCorp Freelance seller, 2015-2019 Eleven kernel LPEs fingerprinted by coding style; a one-call elevate API and a user-mode token walk, sold to APTs and recycled to ransomware Read
PlayBit / luxor2008 The recycler, secondhand tier Five 1-day LPEs rebuilt from patches; the opposite handwriting, including the same bug Volodya sold as a zero-day Read
The CLFS contractor Anonymous, ransomware supplier Five CLFS exploits in one year from one author: learned the driver rebuilding a patched bug, then wrote original zero-days in it Read
Candiru / Sourgum Spyware vendor, the customer Windows kernel zero-days as stocked inventory in DevilsTongue, sold to governments, used against journalists Read
j00ru Researcher, the finder A decade of win32k surface enumeration; a year of kernel font fuzzing that ended with Microsoft moving font parsing out of the kernel Read
James Forshaw Researcher, the primitives librarian The catalogue of links, oplocks and privileged file operations that everyone from red teams to Nightmare-Eclipse composes without citation Read
The BYOVD operators Ransomware crews, the user tier Akira's ZeroT against the Dell dbutil driver: kernel access as a purchased checklist item in a rehearsed playbook Read
SpyBoy / Terminator Forum vendor, retail tier EDR termination productized on a signed vulnerable driver; the corner store of the kernel-abuse economy Read
hfiref0x / KDU Open-source tool smith The provider abstraction that turned BYOVD into an API; this corpus's 1,775-driver analysis is built on it Read
DEVCORE Research team, subsystem sweep Ten-plus kernel streaming vulnerabilities in two months on an overlooked surface; three already in this corpus Read
Connor McGarr Researcher, mitigation analyst JTAG into kernel shadow stacks and the kCFG/kCET boundary; measures what the Targets half of this site rates Read
Zerodium Brokerage, the market maker Public price lists that set the reference value for every seller and buyer in this series Read
The agentic finders Research labs and solos, the automation tier SLYP's MCP-toolified harness: 39 MSRC zero-days (31 COM/RPC races, 8 kernel driver bugs), 23 CVEs, a reported 203,000 USD; the moat is the tools, not the model Read

Sixteen profiles now, and together they draw the market's full vertical: the individual dropping zero-days over a grudge (Nightmare-Eclipse), the state program (Lazarus), the bypass industrialist (Sacco), the freelance seller whose code handwriting gave him away (Volodya), his secondhand-tier rival (PlayBit), the anonymous contractor supplying ransomware from one driver (the CLFS contractor), the customer stocking kernel zero-days as inventory (Candiru), the finders who map the surfaces everyone else mines (j00ru, Forshaw), the operators running rehearsed playbooks on purchased access (the BYOVD operators), the retail tier selling termination by the unit (SpyBoy), the open-source tool smith whose API models the whole BYOVD landscape (hfiref0x), the subsystem sweepers (DEVCORE), the mitigation analyst who measures what survives (McGarr), the brokerage that prices it all (Zerodium), and the newest tier, the automation that converts compute into findings and will make every crash-oracle verdict in this corpus churn faster (the agentic finders). More are added as their bodies of work are dissected.