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-rootkitsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package694bdf3e…0b79b908
694bdf3eba6d…fadb0b79b9084 files · 3.4 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/dissecting-boot-and-kernel-rootkits@da7600a
On this page
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.binDetects 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.mdfor the classifier. - ATT&CK T1542.003 and T1014 (linked in frontmatter).
Files in this version
references/11.3 KB
- api-reference.md1.3 KB
scripts/13.4 KB
- analyst.py3.4 KB
- LICENSE340 B
- SKILL.md2.8 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 694bdf3e | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in Reporting and compliance
See the category- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login