Skip to content

meltedinhex/analyst-ai-pack / skills/dissecting-boot-and-kernel-rootkits

dissecting-boot-and-kernel-rootkits

Verified

Analyzes bootkit and rootkit samples by identifying boot-process tampering (MBR/VBR/ UEFI), kernel-mode components, and stealth hooking techniques from static indicators. Activates for requests to analyze a bootkit or rootkit, examine MBR/UEFI tampering, or identify kernel-mode stealth components.

Dissecting Boot and Kernel Rootkits

When to Use

  • You have a sample (MBR/VBR image, UEFI module, or kernel driver) suspected of boot-process or kernel-level tampering and stealth.
  • You need to identify the persistence vector and stealth technique class statically.

Do not use this on production firmware/boot media without acquisition — analyze a captured image. The skill reads bytes statically and executes nothing.

Prerequisites

  • The boot image / UEFI module / driver (read inertly).

Safety & Handling

  • Read bytes statically; never write the sample to boot media or load the driver.

Workflow

Step 1: Classify the artifact

python scripts/analyst.py classify sample.bin

Detects MBR/VBR (boot signature 0x55AA at 0x1FE), UEFI modules (PE with EFI subsystem / PI GUIDs / EFI_ strings), and kernel drivers (PE importing ntoskrnl/hal, .sys indicators).

Step 2: Identify tampering / hooking indicators

Flag disk-write primitives (Int 13h for MBR bootkits), SSDT/IRP hooking and Zw*/Ke* kernel APIs, DKOM strings, and driver-callback registration.

Step 3: Map the persistence vector

Determine whether persistence is via MBR/VBR overwrite, UEFI variable/module, or driver service.

Step 4: Document

Record the artifact type, persistence vector, and stealth technique class, mapping to ATT&CK.

Validation

  • The artifact type is identified by concrete signatures (boot signature, PE subsystem, imports).
  • Tampering/hooking indicators reference real primitives, not generic strings.
  • The persistence vector is stated with its evidence.

Pitfalls

  • A legitimate bootloader/driver resembling a bootkit/rootkit — corroborate with behavior.
  • UEFI modules requiring firmware-volume parsing beyond simple PE checks.
  • Kernel samples needing signed-driver and callback context to confirm stealth.

References

brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 319kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 196kUpdated Claude CodeCodexVerifiedInstall