sneakerhax/arsenal

Red Team tools weaponized

Hi, I'm sneakerhax,

I have spent the last eight years on Red Teams, helping some of the world's largest software companies discover soft spots in their security posture. Additionally, I demonstrate the impact of exploiting those weaknesses, test the response capabilities of Blue Teams and Incident Responders, and identify systemic security process issues at scale. Before working on Red Teams, I spent eight years in Information Technology as a Systems Administrator.

Github Overview

My Github contains documentation, posts, tools, and experimental code for Red Team purposes. I use many elements in these code repos, either in their current state or a modified/updated version, to perform my job daily.

Areas of interest:

• Red Team
• Cloud
• Containers
• Kubernetes

Additional Information

A list of programming languages, software, licenses, and contact information:

arsenal's Issues

Hakin9 Magazine

Hello there! My name is Antonina and I'm an Editor in Hakin9 Magazine. I'd like to officially invite you to become an online course instructor for PenTest Mag and present you with more details about the process and arrangement.

Our courses are video-focused with practical exercises. They are accessible in a VoD format, they are pre-recorded and self-paced, so it implies the flexibility of an arrangement, you can treat it as a part-time contact job.

If you would like to know more details, contact me via: [email protected]

Best Regards,
Antonina Filipowicz

Container Size Optimizations

Noticed a few of these images are using Kali Rolling images to try run things, which is potentially bringing in extra unneeded packages. It may be an idea to try reduce the size of some of your containers by using a smaller base image and also optimizing the build steps a bit.

For instance https://hub.docker.com/r/heywoodlh/metasploit/tags comes in at only 380 MB for the AMD64 image whereas your image is currently coming in at around 850-900 MB for the equivalent AMD64 image. I'm not sure if you also need these additional dependencies or not, but thought it may be something to consider.

Update PyReconer to use eyewitness

Details:

PyReconer currently uses Aquatone for screen shots of targets. This tool has not been updated since 2019. Eyewitness has continued updates and features.

Request:

Replace the functionality of Aquatone to perform screenshots with Eyewitness

Required

• Updated the Dockerfile to use the image python:3-slim (supported by Eyewitness)
• Update the Dockerfile to remove aquatone functionality
• Update the Dockerfile to install Eyewitness
• Remove the binary location variables from PyReconer.py for aquatone
• Add the binary location variable for Eyewitness to PyReconer.py
• Remove the output location for aquatone
• Add the output location for Eyewitness
• Remove the function aquatone_screen_grab and calls to the function
• Add the function eyewitness_screen_grab to PyReconer.py
• Call the function eyewitness_screen_grab as part of the automation flow
• Ensure you can download the eyewitness results by updating run_reconer.sh if necessary
• Post proof of these changes working in the pull request
• Get your pull request approved
• Request closure of this issue