Back to catalog
Static reviewDevelopment

Skill dossier

analyzing-bootkit-and-rootkit-samples

Source declaration

Analyzes bootkit and advanced rootkit malware infecting the Master Boot Record (MBR), Volume Boot Record (VBR), or UEFI firmware for below-OS persistence, covering boot sector analysis, UEFI module inspection, and anti-rootkit detection. Use when compromise survives OS reinstallation or antivirus/EDR fails to detect malware despite clear infection signs.

The author's original description, preserved in English. It describes intent, not verified performance.

Analyzes bootkit and advanced rootkit malware infecting the Master Boot Record (MBR), Volume Boot Record (VBR), or UEFI firmware for below-OS persistence, covering boot sector analysis, UEFI module inspection, and anti-rootkit detection. Use when compromise survives OS reinstallation or antivirus/EDR fails to detect malware despite clear infection signs.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Analyzes bootkit and advanced rootkit malware infecting the Master Boot Record (MBR), Volume Boot Record (VBR), or UEFI firmware for below-OS persistence, covering boot sector analysis, UEFI module inspection, and anti-rootkit detection. Use when compromise survives OS reinstallation or antivirus/EDR fails to detect malware despite clear infection signs. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/analyzing-bootkit-and-rootkit-samples/SKILL.md:L55]
  • Step 1: Acquire Boot Sectors and Firmware [Source statement; provisional, not tested. Evidence: skills/analyzing-bootkit-and-rootkit-samples/SKILL.md:L57]
  • Step 2: Analyze MBR/VBR for Bootkit Code [Source statement; provisional, not tested. Evidence: skills/analyzing-bootkit-and-rootkit-samples/SKILL.md:L87]
  • Step 3: Analyze UEFI Firmware for Implants [Source statement; provisional, not tested. Evidence: skills/analyzing-bootkit-and-rootkit-samples/SKILL.md:L134]
  • Step 4: Detect Kernel-Level Rootkit Behavior [Source statement; provisional, not tested. Evidence: skills/analyzing-bootkit-and-rootkit-samples/SKILL.md:L189]
  • Step 5: Boot Process Integrity Verification [Source statement; provisional, not tested. Evidence: skills/analyzing-bootkit-and-rootkit-samples/SKILL.md:L222]
  • Step 6: Document Bootkit/Rootkit Analysis [Source statement; provisional, not tested. Evidence: skills/analyzing-bootkit-and-rootkit-samples/SKILL.md:L253]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/analyzing-bootkit-and-rootkit-samples/SKILL.md:L1-L32]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
33.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/analyzing-bootkit-and-rootkit-samples/LICENSEOther11 KB
skills/analyzing-bootkit-and-rootkit-samples/references/api-reference.mdReference2.7 KB
skills/analyzing-bootkit-and-rootkit-samples/scripts/agent.pyScript7 KB
skills/analyzing-bootkit-and-rootkit-samples/SKILL.mdInstruction12.7 KB

SKILL.md frontmatter

{
  "name": "analyzing-bootkit-and-rootkit-samples",
  "description": "Analyzes bootkit and advanced rootkit malware infecting the Master Boot Record (MBR), Volume Boot Record (VBR), or UEFI firmware for below-OS persistence, covering boot sector analysis, UEFI module inspection, and anti-rootkit detection. Use when compromise survives OS reinstallation or antivirus/EDR fails to detect malware despite clear infection signs.\n",
  "domain": "cybersecurity",
  "subdomain": "malware-analysis",
  "tags": [
    "malware",
    "bootkit",
    "rootkit",
    "UEFI",
    "MBR-analysis"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "DE.AE-02",
    "RS.AN-03",
    "ID.RA-01",
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1542.003",
    "T1542.001",
    "T1542.002",
    "T1014",
    "T1547.006"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Acquire Boot Sectors and Firmware

    Source-described action candidate under “Step 1: Acquire Boot Sectors and Firmware”; not verified execution.

  4. 04
    Action

    Extract MBR, VBR, and UEFI firmware for offline analysis:

    Source-described action candidate under “Step 1: Acquire Boot Sectors and Firmware”; not verified execution.

  5. 05
    Action

    Step 2: Analyze MBR/VBR for Bootkit Code

    Source-described action candidate under “Step 2: Analyze MBR/VBR for Bootkit Code”; not verified execution.

  6. 06
    Action

    Step 3: Analyze UEFI Firmware for Implants

    Source-described action candidate under “Step 3: Analyze UEFI Firmware for Implants”; not verified execution.

Inspect all extracted workflow candidates (23 candidate steps)
  1. 07
    Action

    Inspect UEFI firmware volumes for unauthorized modules:

    Source-described action candidate under “Step 3: Analyze UEFI Firmware for Implants”; not verified execution.

  2. 08
    Action

    Step 4: Detect Kernel-Level Rootkit Behavior

    Source-described action candidate under “Step 4: Detect Kernel-Level Rootkit Behavior”; not verified execution.

  3. 09
    Action

    Analyze the running system for rootkit artifacts:

    Source-described action candidate under “Step 4: Detect Kernel-Level Rootkit Behavior”; not verified execution.

  4. 10
    Action

    Step 5: Boot Process Integrity Verification

    Source-described action candidate under “Step 5: Boot Process Integrity Verification”; not verified execution.

  5. 11
    Action

    Step 6: Document Bootkit/Rootkit Analysis

    Source-described action candidate under “Step 6: Document Bootkit/Rootkit Analysis”; not verified execution.

  6. 12
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  7. 13
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  8. 14
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  9. 15
    Action

    Boot from a Linux live USB to avoid executing any compromised OS components

    Source-described action candidate under “Scenario: Investigating Persistent Compromise Surviving OS Reinstallation”; not verified execution.

  10. 16
    Action

    Dump the SPI flash firmware using chipsec or flashrom for offline analysis

    Source-described action candidate under “Scenario: Investigating Persistent Compromise Surviving OS Reinstallation”; not verified execution.

  11. 17
    Action

    Dump the MBR and VBR sectors with dd for boot sector analysis

    Source-described action candidate under “Scenario: Investigating Persistent Compromise Surviving OS Reinstallation”; not verified execution.

  12. 18
    Action

    Copy the EFI System Partition for bootloader integrity verification

    Source-described action candidate under “Scenario: Investigating Persistent Compromise Surviving OS Reinstallation”; not verified execution.

  13. 19
    Input

    Open the SPI dump in UEFITool and compare module GUIDs against vendor-provided firmware

    Source-described input candidate under “Scenario: Investigating Persistent Compromise Surviving OS Reinstallation”; not verified execution.

  14. 20
    Output

    Look for additional or modified DXE drivers that should not be present

    Source-described output candidate under “Scenario: Investigating Persistent Compromise Surviving OS Reinstallation”; not verified execution.

  15. 21
    Action

    Analyze any suspicious modules with Ghidra (x8664 UEFI module format)

    Source-described action candidate under “Scenario: Investigating Persistent Compromise Surviving OS Reinstallation”; not verified execution.

  16. 22
    Action

    Verify Secure Boot configuration and check for exploit-based bypasses

    Source-described action candidate under “Scenario: Investigating Persistent Compromise Surviving OS Reinstallation”; not verified execution.

  17. 23
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

18 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

2 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

16 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 16 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/analyzing-bootkit-and-rootkit-samples/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/analyzing-bootkit-and-rootkit-samples/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/analyzing-bootkit-and-rootkit-samples
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.