Sandmap

Sandmap is a tool supporting network and system reconnaissance using the massive Nmap engine.

Description • How To Use • Modules • Configuration File • Requirements • Logging • Contributing • Project Architecture • License • Wiki

_{Created by trimstray and contributors}

Description

Sandmap is a tool supporting network and system reconnaissance using the massive Nmap engine. It provides a user-friendly interface, automates and speeds up scanning and allows you to easily use many advanced scanning techniques.

Key Features

• simple CLI with the ability to run pure Nmap engine
• predefined scans included in the modules
• support Nmap Scripting Engine (NSE) with scripts arguments
• TOR support (with proxychains)
• multiple scans at one time
• at this point: 31 modules with 459 scan profiles

How To Use

It's simple:

# Clone this repository
git clone --recursive https://github.com/trimstray/sandmap

# Go into the repository
cd sandmap

# Install
./setup.sh install

# Run the app
sandmap

• symlink to bin/sandmap is placed in /usr/local/bin
• man page is placed in /usr/local/man/man8

Modules

Available modules: 31
Available scan profiles: 459

If you want to create your own modules, take a look this.

Configuration file

The etc/main.cfg configuration file has the following structure:

# shellcheck shell=bash

# Specifies the default destination.
# Examples:
#   - dest="127.0.0.1,8.8.8.8"
dest="127.0.0.1"

# Specifies the extended Nmap parameters.
# Examples:
#   - params="--script ssl-ccs-injection -p 443"
params=""

# Specifies the default output type and path.
# Examples:
#   - report="xml"
report=""

# Specifies the TOR connection.
# Examples:
#   - tor="true"
tor=""

# Specifies the terminal type.
# Examples:
#   - terminal="internal"
terminal="internal"

Requirements

Sandmap uses external utilities to be installed before running:

• nmap
• xterm
• proxychains

This tool working with:

• GNU/Linux or BSD (testing on Debian, CentOS and FreeBSD)
• Bash (testing on 4.4.19)

Also you will need root access.

Logging

After running the script, the log/ directory is created and in it the following files with logs:

• <script_name>.<date>.log - all _logger() function calls are saved in it
• stdout.log - a standard output and errors from the _init_cmd() function are written in it. If you want to redirect the output from command, use the following structure: your_command >>"$_log_stdout" 2>&1 &

Contributing

See CONTRIBUTING.md.

Project architecture

See Project Architecture.

License

GPLv3 : http://www.gnu.org/licenses/

Free software, Yeah!