external_c2_framework
external_c2_framework copied to clipboard
Und3rf10w
Python api for usage with cobalt strike's External C2 specification
Code in the `master` branch is considered tested and stable. Once all of the changes that need to be done for the beta release are complete, then we can push...
In cases where a transport needs to encode data in batches, `commonUtils.prepData()` prevents them from working. An example usecase for this can be seen with #12, where we can't build...
As much as I hate to do this, at this point, I'm strongly leaning towards a total rewrite of this project based on lessons learned thus far. I believe I...
Need to add logic to validate builder values. For the most part, this just means making sure that the `type` of the value of a variable passed to the builder...
Eventually, need to add database support to facilitate logging and eventually session restoration. This probably won't be considered until at least after the beta release. #14 contains a few ideas...
Create a new transport that will utilize twitter as a comms channel.
It would be nice to have a subreddit based c2 support. This should avoid the challenges posed by twitter. While still being just as reliable.
If the account(s) configured to be used for the transport have been used for this purpose before (i.e. there's previous c2 messages in the inbox(es)), it's possible to trigger a...
It would be extremely useful if the c2 client had the capability to implement a fail-over transport mechanism. Ideally, in the event of an extremely long timeout where the client...
The client needs to be further abstracted, this will provide the base logic that is required for the server core to be refactored. The following list of desired features should...