A community maintained repository of Beacon Object Files (BOFs) for the offensive security community.
OpenBOF is an open, community driven repository dedicated to collecting, maintaining, and documenting Beacon Object Files (BOFs). Our mission is to provide a centralized resource where security professionals can discover high quality BOFs, contribute new capabilities, and collaborate to strengthen the offensive security ecosystem.
Whether you're a red team operator, security researcher, or developer, OpenBOF is designed to make finding and sharing BOFs simple, consistent, and accessible.
Our goal is to become the definitive community resource for publicly available Beacon Object Files by:
- Maintaining a centralized collection of BOFs.
- Encouraging community contributions and collaboration.
- Improving discoverability through consistent organization and documentation.
- Preserving attribution and licensing for every contribution.
- Providing clear documentation and examples for each BOF.
.
├── bofs/
│ ├── credential-access/
│ ├── defense-evasion/
│ ├── discovery/
│ ├── execution/
│ ├── lateral-movement/
│ ├── persistence/
│ ├── privilege-escalation/
│ ├── reconnaissance/
│ └── ...
├── docs/
├── examples/
├── LICENSE
└── README.md
We welcome contributions from the community.
Before opening a pull request, please ensure that:
- The BOF is publicly releasable.
- The project includes documentation describing its purpose, supported platforms, arguments, and usage examples.
- The original author is properly credited.
- The applicable license is included.
- The BOF has been tested and builds successfully.
If you're planning a significant addition or structural change, consider opening an issue first to discuss the proposal.
OpenBOF is built on the work of the offensive security community. Every effort is made to preserve original authorship and licensing. Contributors retain ownership of their work, and users should review the license accompanying each BOF before use or redistribution.
The OpenBOF repository is licensed under the MIT License.
Individual BOFs may be distributed under different licenses. Unless otherwise noted, the original license for each BOF remains in effect.
OpenBOF is intended for authorized security testing, research, and educational purposes only. Users are responsible for ensuring their activities comply with applicable laws, regulations, and organizational policies. The maintainers and contributors assume no responsibility for misuse of the software contained within this repository.