Skip to content

meltedinhex/analyst-ai-pack / skills/analyzing-windows-driver-malware

analyzing-windows-driver-malware

Verified

Analyzes malicious and vulnerable Windows kernel drivers (.sys) by parsing the PE for the native subsystem, identifying DriverEntry/IRP dispatch and IOCTL handlers, and flagging BYOVD and kernel-callback abuse. Activates for requests to analyze a Windows driver, examine a .sys sample, or assess a BYOVD/kernel driver threat.

Analyzing Windows Driver Malware

When to Use

  • You have a .sys kernel driver (malicious rootkit driver or a vulnerable driver used for BYOVD) and need to identify its entry, IRP/IOCTL handlers, and dangerous kernel operations.
  • You are assessing privilege-escalation or kernel-stealth risk.

Do not use this by loading the driver — analyze it statically. Loading kernel code is dangerous and is the threat itself.

Prerequisites

  • The driver .sys (read inertly).

Safety & Handling

  • Read bytes statically; never install/load the driver. Note its signing status for BYOVD context.

Workflow

Step 1: Confirm it is a kernel driver

python scripts/analyst.py inspect driver.sys

Verifies the PE native subsystem (1), kernel imports (ntoskrnl.exe, hal.dll), and reports imported kernel APIs.

Step 2: Identify dispatch and dangerous primitives

Flag IRP/IOCTL handling (IoCreateDevice, IoCreateSymbolicLink, IRP_MJ_DEVICE_CONTROL), arbitrary read/write primitives (MmMapIoSpace, ZwMapViewOfSection, MmCopyMemory), and callback registration (PsSetCreateProcessNotifyRoutine, ObRegisterCallbacks).

Step 3: Assess BYOVD/stealth potential

Map exposed IOCTLs to capabilities (physical memory access, process kill, token theft) that BYOVD abuse relies on.

Step 4: Document

Record the driver's handlers, dangerous primitives, signing status, and risk.

Validation

  • Native subsystem and kernel imports confirm a driver.
  • Dispatch/IOCTL and dangerous-primitive imports are reported with evidence.
  • Capabilities are tied to concrete imported APIs.

Pitfalls

  • Legitimate vendor drivers that are nonetheless exploitable (BYOVD) — context matters.
  • Drivers resolving APIs dynamically, hiding imports.
  • Confusing user-mode helper components with the kernel driver itself.

References

rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 193kUpdated Claude CodeCodexVerifiedInstall