This commit is contained in:
ethanseow2002@gmail.com
2026-02-03 17:32:20 +08:00
parent 3fb0e2e757
commit 6c9fd747b1
+2 -2
View File
@@ -11,9 +11,9 @@ python bof_pack.py Msgbox.x64.o -o bof.blob
```
## Why did I make this?
The Cobalt Strike BOF Loader has given me numerous issues in the past when doing BOF development, regarding sections (COMDATs, i'm looking at you) that aren't handled by the Beacon BOF loader. This is especially frustrating when the issues are not reproducable in open source COFF Loaders, which benefit from more debuggability.
The Cobalt Strike BOF Loader has given me numerous issues in the past when doing BOF development, regarding sections (COMDATs, i'm looking at you) that aren't handled by the Beacon BOF loader. This is especially frustrating when the issues are not reproducible in open source COFF Loaders, which benefit from more debuggability.
To make things worse, the Cobalt Strike BOF Loader does not even take in full COFFs directly, there is some processing done on the teamserver side, which is barely documented. The resulting blob sent down to Beacon is much smaller than the original COFF, and the format is not documented.
This project aims to be a true 1:1 replica of the Cobalt Strike implementation, where any issues in one should be reproducable in the other.
This project aims to be a true 1:1 replica of the Cobalt Strike implementation, where any issues in one should be reproducible in the other.