Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/dissecting-boot-and-kernel-rootkitsReporting and compliance

dissecting-boot-and-kernel-rootkits

⁨Analyzes bootkit and rootkit samples by identifying boot-process tampering (MBR/VBR/⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/dissecting-boot-and-kernel-rootkits

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
G3IFXro002…661EHZBw==The CLI checks the SHA-256 and the signature before it writes a file.
Package694bdf3e…0b79b908
694bdf3eba6d…fadb0b79b9084 files · ⁦3.4 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/dissecting-boot-and-kernel-rootkits@da7600a

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

bash
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

  • See references/api-reference.md for the classifier.
  • ATT&CK T1542.003 and T1014 (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a694bdf3eSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login