覆盖 BOF 从编译到内存执行的关键环节,组件即将开源
工具bof免杀逆向
RT @NtRajkit: 🐝 🪼 Inside BOFs, Crystal Palace, and JellyBee PIC (1/3): How the Loader Prepares and Executes a COFF Object in Memory
What happens between compiling a BOF and executing it in memory?
The compiler produces a COFF object. The implant’s loader still has work to do.
🎥 Watch the first episode:
https://t.co/NQju8cbvgB
The release of the first JellyBee components is approaching. One will be released under GPLv3, while the others will be available free of charge under a license provided upon request.
Before the first release, this technical series explores the architectural differences behind how implant capabilities are built, loaded, and executed.
JellyBee is the only command-and-control ecosystem built around a modular, position-independent implant architecture with an integrated environment for building its capabilities directly from C projects and repositories.
Swarm Factory makes this architecture practical for operators by handling PIC complexity through an advanced compilation driver integrated into its build environment.
Capabilities are built as independent modules within the same ecosystem that manages their execution, allowing JellyBee to maintain a small implant core.
Craft & Control.
To explain this architecture and how it differs from other approaches, the series examines three models:
① BOF / COFF
Compilation produces the object, but loading still requires work such as applying relocations and resolving symbols and dependencies.
In the Beacon BOF model, the implant provides the loading infrastructure. Modules can also use Beacon’s internal APIs and Dynamic Function Resolution (DFR) for Windows API imports.
The first video follows this process in memory.
② Crystal Palace Linker
The second episode explores linking and composing capabilities for position-independent execution, examining where loading and resolution responsibilities reside in the resulting design.
③ JellyBee’s Modular PIC Architecture
The third episode presents the build workflow integrated into Swarm Factory, from C projects to position-independent modules.
Instead of continually expanding a single implant binary, JellyBee keeps capabilities in separate modules. Its base implant currently ranges from approximately 23 to 45 KB and does not require a separate stager.
Code originally developed as a BOF can also be adapted to conventional C and built through Swarm Factory into a position-independent module.
Start with Chapter 1 to see what the BOF loader does in memory and understand the foundation for the next two episodes.
🧪 https://t.co/SdVLGEzzgg
#Cybersecurity #RedTeam #BOF #Offensive #PIC