Wraith

About

Wraith is an open source IRC bot written in C++. It has been in development since late 2003. It is based on Eggdrop 1.6.12 but has since evolved into something much different at its core.

Wraith aims to be a secure and easy to setup and manage botnet, compared to eggdrop. A botnet can be setup in a matter of minutes and updated later with 1 command. Leaf bots save no files locally, but rather store configuration in their own binary. Hubs do not connect to IRC, and keep a local encrypted copy of the userfile. It is meant for use on IRC servers without services as a means of protecting an IRC channel from takeover, and easily controlling channels.

Wraith can be setup on FreeBSD, Linux, OpenBSD and OpenSolaris shells. It does not support modules or TCL currently. The very best part of Wraith, is the config. A normal eggdrop config can consist of hunders of lines, a wraith config is ~10

Features

The features are way too many to be posted here, so I have picked a few of my favourites:

General

• Wraith IRC bot works in an unique way. Only leafs connects to IRC, hubs are offline and only accessable thru telnet. Leafs are in a way like drones, controllable thru the hub via telnet. Userfiles are stored encrypted on the shell in runtime memory and sent to leafs during link. With eggdrop, you need to make a new conf for each bot but wraith uses same binary and config for all bots. More information about that under Installing

Security

• All trafic between bots are encrypted with AES-256+base64 and configs with SALT1, while binaries stores an assortment of MD5 checksums internally and verify them upon starting the bot. For security reasons, the hun stays offline and only leafs connect, without any configs. Wraith comes with a strong mass op/deop protection along with a large list of security settings to protect your channel. No initial TCL scripts are needed, nor supported.

IRC

• +bitch uses several methods of protection, Wraith comes with a fun list of pre-added kick reasons and autolimiter is standard to prevent massjoins from other botnets. Wraith also comes with a RBL ban support, making it able to use AHBL.org, efnetrbl.org blockinglists and others.

Shells

• Bot config is password protected and bots automatically sets up a crontab entry. All bots on the shell go into 1 binary and each bots spawns its own process. Bots on the same shell will link to the first bot in the binary (the localhub). Only the localhub links to the actual hubs, keeping the other leafs in a subnet so if a hub dies they are not just roaming around uncontrolled.

Installing

Installation is very easy. I'v chosen to divide it into 2 steps, hub and leaf. Let's start with the hub.

[1]Download the pre-compiled binary. If you fail to get it running, download the source and compile manually. I choosed to use that part in this documentation, since I have never in all my shells ran into a problem with manually compiling, so here we go:

• Download the source to your dir, and make 2 folders: "hub" and "leaf". Note that you only need do add 2 folders on the shell where you want the hub to be. If you choose to run ONLY hub on a shell, then don't make an folders :)

• tar -zxvf the tar.gz-file and cd into the source.
  • ./configure
  • make or gmake

• For the pack.cfg, the actual net configuration, I advice you to use the Wraith homepage example: [2]

• When pack.cfg is done, you initiate the config with "./wraith -q pack.cfg"

• To enter the bots you want, enter: "./wraith -C". Notice the capital C. Same as pack.cfg, use the official websites example: [3]

• If this is the hub bot, enter EXACT same name as you did in pack.cfg and same IP, and tada..you have a hub. If you run leafs, enter whatever you want your bots to be named and just start them with "./wraith". They will start, crontab and link automatically and all you need is to telnet into the hub's IP/port as specified in pack.cfg.

Links

• Official website: [4]
• IRC channel: [5]

--Raven 06:18, 25 November 2011 (EST)