Long-term desired feature implementation list

[Und3rf10w]

• Create a common framework_manager, which will interface directly with a framework's server. This will allow us to support multiple running clients, with multiple running transports and encoders, across multiple frameworks.

• Creation of common and modular transport and obfuscation modules, that can be loaded by either the client or controller for usage. Any obfuscation module should be compatible with any transport module and vice versa

• Make the client be entirely in Python - Implement the builder functionality #16

• Enable the ability to have the staging process utilize a different transport and encoder module than the normal c2 comms modules.

• Creation of modular injection module, that can be loaded by the client to support multiple methods of injecting the beacon stage to the host.

• Creation of builder routine, that will build the various components of the client and controller when given a specified injection, transport, and obfuscation modules. Should support reading in a common config file so toolsets can be rapidly deployed. - Add builder functionality, reorg project #17

• Research rootkit options for the client.

• See if possible to dynamically loading and unloading modules in a polymorphic manner on the client.

• See if possible to store and read additional options in the beacon configuration stage between the controller and c2 server.

• If possible, support ability to modify beacon process with control flow graph modification code to give reversers and investigators a personal "fuck you"