Home Projects About

Vulpes: Starting

Table of Contents

When running vulpes, it must be done from the CLI. This page will show the available options.

First Run

Running vulpes.py:

usage: Vulpes [-h] [-H] [-p] [-r] [-a] [--logstash LOGSTASH] [-v] [--quiet] [--debug]

optional arguments:
  -h, --help           show this help message and exit
  -H , --host          Specify the host to run on (default:
  -p , --port          Specify the port to run on (default: 5000)
  -r , --responses     The directory containing valid/invalid.html for listener responses
  -a , --audio         The directory containing .mp3 files to work as notifications
  --logstash           URL for logstash instance
  --verbose            If enabled, logger will print more information
  --quiet              Disable all logging
  --debug              Enable Debugging (this will stop listener threads from being created).

When specifying --host and --port, this will determine where the web application will be hosted. When ran, this will look something like:

Browsing to the URL:

A login process does exist, but we have completely killed that functionality until later on. As this isn't being used, its not important for us.

Other Startup Flags

There are a few other flags to start vulpes with, namely --responses and --logstash. The logstash one will be discussed more in the Logging section. Whereas the responses flag allows the user to point it towards a directory containing valid.html and invalid.html. This will then both be served back to the implant on request depending on whether or not the request was successful. More on this in Communication.