analyzing-uefi-bootkit-persistence

Analyze UEFI bootkit persistence via CHIPSEC SPI dumps and ESP inspection.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/YukiIto1999/ctf-sleuth --skill analyzing-uefi-bootkit-persistence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyzing-uefi-bootkit-persistence
Source: https://github.com/YukiIto1999/ctf-sleuth/tree/main/.claude/skills/analyzing-uefi-bootkit-persistence
Command: npx skills add https://github.com/YukiIto1999/ctf-sleuth --skill analyzing-uefi-bootkit-persistence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Analyzes UEFI bootkit persistence mechanisms including firmware implants in SPI flash, ESP modifications, Secure Boot bypass techniques, and UEFI variable manipulation.

Core Features & Use Cases

  • ESP and SPI flash analysis to detect firmware implants and unauthorized modifications.
  • UEFI variable inspection and ESP contents inventory to uncover persistence mechanisms.
  • Forensic workflow support with CHIPSEC-based validation and Measured Boot/PKI indicators, enabling enterprise incident response.

Quick Start

Run the agent on a firmware dump or mounted ESP to detect bootkit indicators and generate a report.

Frequently Asked Questions about analyzing-uefi-bootkit-persistence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect UEFI bootkit persistence in a firmware dump?

To detect UEFI bootkit persistence, analyze firmware implants in SPI flash and ESP modifications. This process identifies unauthorized changes by inspecting UEFI variables and examining firmware volumes using CHIPSEC-based validation techniques.

What is a UEFI bootkit persistence mechanism?

A UEFI bootkit persistence mechanism is a threat that implants malicious code in SPI flash, modifies ESP contents, or manipulates Secure Boot variables. These techniques allow attackers to maintain unauthorized control over compromised endpoints during boot-time.

Can I use CHIPSEC to inspect Secure Boot variables for bypass techniques?

Yes, you can use CHIPSEC to inspect Secure Boot variables and examine firmware volumes. This supports forensic analysis of boot-time threats by validating SPI dumps and uncovering unauthorized UEFI variable manipulation.

How do I perform an enterprise firmware security audit for boot-time threats?

Perform an enterprise firmware security audit by analyzing UEFI bootkit persistence across compromised endpoints. This involves SPI dump validation, ESP contents inventory, and Measured Boot indicator examination to generate forensic reports.

What is the best way to analyze ESP modifications during incident response?

The best way to analyze ESP modifications is conducting a full ESP contents inventory alongside SPI flash analysis. This uncovers persistence mechanisms by detecting unauthorized firmware implants and generating machine-readable forensic outputs.