c-bof

Generate, compile, and debug C Beacon Object Files for Cobalt Strike.

15|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/AeonDave/malskill --skill c-bof
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: c-bof
Source: https://github.com/AeonDave/malskill/tree/main/bof/c-bof
Command: npx skills add https://github.com/AeonDave/malskill --skill c-bof

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enables the creation, compilation, and debugging of Beacon Object Files (BOFs) in C, streamlining the development of custom payloads for Cobalt Strike and compatible C2 frameworks.

Core Features & Use Cases

  • BOF Generation: Create new BOFs from scratch or convert existing C Proof-of-Concepts.
  • Error Resolution: Debug common BOF linking and entrypoint errors.
  • Pattern Implementation: Provides patterns for advanced techniques like DFR, heap management, process injection, multi-mode BOFs, and embedded payloads.
  • Use Case: A user needs to create a BOF to dump LSASS credentials. They can use this Skill to generate the BOF code, compile it, and ensure it functions correctly within Cobalt Strike.

Quick Start

Use the c-bof skill to create a BOF that injects a payload into a target process.

Frequently Asked Questions about c-bof

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

FAQPage Schema
How do I develop and compile C Beacon Object Files for Cobalt Strike?

Beacon Object Files are COFF objects executed in-memory by Cobalt Strike beacons to perform post-exploitation tasks like credential dumping or process injection. This Skill facilitates BOF generation by converting existing C Proof-of-Concepts into functional payloads and resolving common linking errors.

Can I convert an existing C Proof-of-Concept into a BOF for Cobalt Strike?

Yes, this Skill supports generating BOFs from scratch or converting existing C Proof-of-Concepts. It provides implementation patterns for dynamic function resolution, heap management, process injection, multi-mode BOFs, and embedded payloads to ensure compatibility with Cobalt Strike and compatible C2 frameworks.

Why does my Beacon Object File fail with linking or entrypoint errors in Cobalt Strike?

Beacon Object File linking or entrypoint errors typically occur due to incorrect compilation settings or missing dependencies. This Skill helps debug common BOF linking and entrypoint errors, ensuring your C code is properly compiled using mingw-w64 for seamless execution within the C2 framework.

How do I implement process injection and credential access patterns in a BOF?

To implement process injection and credential access patterns in a BOF, utilize this Skill's provided templates for dynamic function resolution and embedded payloads. It facilitates generating C code for advanced techniques like injecting payloads into target processes or dumping LSASS credentials within Cobalt Strike.

Do I need mingw-w64 to compile Beacon Object Files?

Yes, mingw-w64 is required to compile Beacon Object Files written in C. This Skill requires mingw-w64 for compilation and Cobalt Strike or a compatible loader for testing, ensuring the generated BOFs function correctly within your C2 framework environment.