Advanced Red Team Tool Development
Budget: $250 – $750 USD
This project is for experienced people, so don't waste your time if you are a newcomer.
#Urgent need .
------------
Please read the requirement's properly :
--
Server for Linux and client for Windows and Linux
1. Server:
Platform: Linux.
- Administration: Local, through a web interface.
- Main functionality: Implement a DNS over DNS builder, similar to dnscat2, but with greater speed in DNS requests to improve interaction.
Additional characteristics:
- Interactive cmd shell: Allow execution of any command to pivot seamlessly.
- File Transfer: Ability to upload and download files.
- Listeners: Create listeners to bind to target ports and access internal services from the outside.
- Multisession: Manage multiple sessions simultaneously from the web interface without stopping the server.
- Builder: Generate binaries for Windows and Linux.
2. Client:
- Platforms: Windows and Linux.
- Additional characteristics:
- Enable HVNC over HTTPS for remote control of the compromised server without creating listeners.
The windows/linux binary would ultimately be like a fusion of "dnscat2","chisel" and "hvnc html",
uniting the capabilities of these three binaries into one but always the connection of this binary will initially be "dns over dns" (never confuse with dot or doh)
so that this way it always works in any scenario, from the admin web panel in Ubuntu we can view the connected clients,
access the various sessions of each client, manage commands, download and upload files, create listeners between server-client and activate the hvnc html when necessary
***On GitHub there are free source codes for "dnscat2" and "chisel" to create a single binary and the hvnc would have to be added using the HTML protocol. Regarding the server, it would be more of a web interface in Flask or Apache that allows you to build the binary. choosing between Windows or Linux and allowing us to see which clients are connected, open a session of the chosen client to create an interactive reverse shell, bind a client port to us using a "listeners" option and choosing if the listener uses the protocol dns or tcp and the option to activate hvnc on the client to manage it, among other main things
#Urgent need .
------------
Please read the requirement's properly :
--
Server for Linux and client for Windows and Linux
1. Server:
Platform: Linux.
- Administration: Local, through a web interface.
- Main functionality: Implement a DNS over DNS builder, similar to dnscat2, but with greater speed in DNS requests to improve interaction.
Additional characteristics:
- Interactive cmd shell: Allow execution of any command to pivot seamlessly.
- File Transfer: Ability to upload and download files.
- Listeners: Create listeners to bind to target ports and access internal services from the outside.
- Multisession: Manage multiple sessions simultaneously from the web interface without stopping the server.
- Builder: Generate binaries for Windows and Linux.
2. Client:
- Platforms: Windows and Linux.
- Additional characteristics:
- Enable HVNC over HTTPS for remote control of the compromised server without creating listeners.
The windows/linux binary would ultimately be like a fusion of "dnscat2","chisel" and "hvnc html",
uniting the capabilities of these three binaries into one but always the connection of this binary will initially be "dns over dns" (never confuse with dot or doh)
so that this way it always works in any scenario, from the admin web panel in Ubuntu we can view the connected clients,
access the various sessions of each client, manage commands, download and upload files, create listeners between server-client and activate the hvnc html when necessary
***On GitHub there are free source codes for "dnscat2" and "chisel" to create a single binary and the hvnc would have to be added using the HTML protocol. Regarding the server, it would be more of a web interface in Flask or Apache that allows you to build the binary. choosing between Windows or Linux and allowing us to see which clients are connected, open a session of the chosen client to create an interactive reverse shell, bind a client port to us using a "listeners" option and choosing if the listener uses the protocol dns or tcp and the option to activate hvnc on the client to manage it, among other main things