Last updated
Last updated
Class handlers are the core of every new Zuthaka integration. These represent the base functionality and given by the integration. The attributes defined in the class handler frame the representation exposed in the web interface and the functions implemented in the class shape the service behavior.
The handlers should only provide the basic C2 interaction while managing consistency. Error tracking tasks are done by Zuthaka's service.
The attributes "name", "description", "documentation", and a list of "registered_options" is mandatory for the correct function of Zuthaka. This helps guide the user through the steps necessary to use the specific implementation.
The descriptions of the integration helps to populate the user interface, for a guided experience.
health check method: is_alive
A good practice to implement "is_alive" is to query the API for a given response. For REST APIs, generating a token is a good way to guarantee the C2 is processing the requests given through the handler.
The Listeners are the services awaiting for connections from different Agents and generally delivering the instructions to be executed by them.
Listener Types are integrated with a similar logic that responds to the C2 API to handle Listeners.
Listeners must be able to be created and destroyed.
The creation or elimination of elements requires a consistency check by the class handler. This allows Zuthaka to catch at an early stage any consistency problem with the infrastructure handled.
The Launchers represent the capabilities of a given C2 to encapsulate the implant for later execution on the victim's machine.
Agents are controlled victim's machines. The integration of Agents on Zuthaka allows the user to manage the computer through the UI.
The behavior is defined through the implementation of abstract methods with an specific "".
The elements of Zuthaka are instances over implemented abstract classes that define the general behavior of a C2.