Distributed-Automation

Summary

This set of applications is for a system made of up hosts connected to a centralized system for automation purposes. This contains the libraries and the basic framework.

This botnet isn't a traditional style one. This isn't desgined to run on host located all around the world. It is designed to virtualize thousands of hosts distributem them all around the globe and run tasks.

This botnet is not designed to be hidden on a computer. Disguising the traffic running between hosts and applications is not a priority. However, disguising outbound traffic heading to external destations does need to be distributed to between many differnet vpns. The name "Distributed Automation" comes from the fact that:

1. Bots will be distributed between different external IP addresses using VPN Gateways. See: VPN Gateway for more details
2. Tasks will be distributed to these bots to run a different times throughout a set period (usually 24hrs).
3. The bots run time will be distributed throught 24 hour intervals
4. All of the trafic comes from many different virtualized hosts distributed
5. This has some distribution/decentralization where different node groups (called franchises)

Please Use Ethically

Definitions

• Framework: Structure for the botnet and the base plugins run on top
• Plugin: The applications that run on top of the bots in the botnet
• Franchise: A subsystem node that can be functionally independent.

Folder Structure

• Director Appliance
  • Application Source
  • Interface Console
• Scheduler Appliance
  • Application Source
• Query Generator Appliance
  • Application Source
  • Docker Image
  • Public API
• Generic Appliance Scripts
• DA2 Libraries
• BW Libraries

Instructions

Please see deployment guide for detailed instructions