Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CS-Remote-OPs-BOF — Remote operations commands implemented using Beacon Object Files | Kitploit
Tools/GitHubGitHub/trustedsec/cs-remote-ops-bof
Encryption/Decryption ToolsPassword AttacksPersistence MechanismsLateral MovementPost-ExploitationSocial EngineeringAuthenticationRed TeamingPayload Development
GitHubtrustedsec/cs-remote-ops-bof

CS-Remote-OPs-BOF

Remote operations commands implemented using Beacon Object Files

1.2k1756124 days agoReviewed by Kitploit

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share
View Repository

Remote Operations BOF

This repo serves as an addition to our previously released SA Repo. Our original stance was that we would not release our tooling that modified other systems, and we would only provide information gathering tooling in a ready to go format.

Over time we've seen many other public security companies release their offensive facing tooling, and we now feel it is appropriate for us to release a portion of our offensive tooling.

Nothing in this repo is particularly special, its basic Microsoft Windows operations in BOF form. These primitives can be used for a large variety of operations.

Injection BOF

We've decided to include the injection bof's that we use when doing EDR detection testing. These BOF's are provided as is and will not be supported (everything under src/Injection and Injection/*)

You are welcome to use these, but issues opened related to these will be closed without review.

Available Remote Operations commands

commandnotes
adcs_requestRequest an enrollment certificate
chromeKeyDecrypts the provided base64 encoded Chrome key
enableuserEnables and unlocks the specified user account
lastpassSearches chrome, brave memory for lastpass passwords and data
office_tokensCollects Office JWT Tokens from any office process.
procdumpDumps the specified process to the specified output file
ProcessDestroyCloses handle(s) in a process
ProcessListHandlesLists all open handles in a specified process
reg_deletedeletes a registry key
reg_saveSave a registry hive to disk
reg_setset / create a registry key
sc_configconfigure an existing service
sc_createcreate a new service
sc_deletedelete an existing service
sc_descriptionModify an existing services description
sc_startstart an existing service
sc_stopstop an existing service
schtaskscreateCreate a new scheduled task (via xml definition)
schtasksdeleteDelete an existing scheduled task
schtasksstopstop a running scheduled task
setuserpassSet a users password
shspawnasA misguided attempt at injecting code into a newly spawned process

Yes schtasksrun is missing, yes that is intentional, but if someone puts in a pull for it I'll accept it on this side.

Contributing

This repo is intended for single task windows primitives. That is to say, even if it takes multiple calls, creating a scheduled task is appropriate.

A command that would attempt to pre-generate an implant and perform automated movement using the BOF's in the repo would be awesome, but is not appropriate for submission to this repo directly.

Code Expectations

  • Your code should compile without errors when using the default makefile
  • any new BOF defines for resolving functions will be placed in src/common/bofdefs.h
  • Code will compile together using the default Makefile (single entry.c file)
  • Code will likewise be compatible with the existing toolchain (mingw)
  • Code will be written in C. This is to standardize and my personal confidence in validating the code.

What to expect as a contributor

After your contribution is received, it will receive an in-depth code review and testing.
After testing is completed, we will have zero or more rounds of change requests based on findings until there are no issues in the code. At that point it will be accepted into the repository, and your github username will be added to our credit list (if you would prefer not to be added or some other handle to be used, just let me know)

Download Tool