sim4n6 / apentestbox

A Docker image made with the most commonly used CLI tools for pentesting and bug bounty hunting.

A Pentest Box

A Docker image made with the most commonly used CLI tools for pentesting and bug bounty hunting.

Usage - installed packages - To-do list

List of installed packages

For now, the Docker image contains:

• jq - ffuf - wfuzz
• anew - qsreplace - unfurl by @tomnomnom
• gau - subjs by @lc
• kxss by @Emoe
• pdtm and all the projectdiscovery tools.
• requests - beautifulsoup4 - selenium

Usage

• Run the container from the remote Docker image and falls into the container bash

sudo docker run -it --name apb sim4n6/apentestbox:latest

In case, you need to re-use the container:

sudo docker start apb
sudo docker exec -it apb bash 

Usage for Build

• Build an image from the current directory Dockerfile.

sudo docker build . -t apentestbox

• List the Docker images.

sudo docker images

• Launch a container from the image apentestbox in the background.

sudo docker run -d --name apb apentestbox

• List the Docker containers.

sudo docker container ls

• Run a command in the container.

sudo docker exec -it apb whoami

• Fall to bash shell within the container. You can escape later the container using exit.

sudo docker exec -it apb bash

TO-DO

• rewrite USAGE section for a more concise one, maybe an advanced part.
• consider using .env.
• work on docker-compose file with .env use.
• consider adding docker compose up command to the USAGE as an alternative.
• figure out how to handle the .config for notify & subfinder.
• Docker volumes use.
• Read carefully Dockerfile best practices.
• push to Docker hub repostiory.
• link the Docker hub repo to gihthub.
• consider Github actions as a testing to be performed on PR trigger.
• add nice clickable cards