gitmyhub

RedTeam-Tools

★ 9.2k updated 2mo ago

Tools and Techniques for Red Team / Penetration Testing

A curated index of 150+ tools and techniques for authorized penetration testing and red teaming, organized by attack stage from reconnaissance through lateral movement.

setup: easycomplexity 1/5

RedTeam-Tools is a curated reference collection of more than 150 tools and techniques used in red teaming and penetration testing. Red teaming is the practice of simulating an attacker's approach against a system or organization to find weaknesses before real attackers do. This repository does not contain original software; it is an organized index pointing to existing tools, with notes on what each one does.

The collection is divided into clearly labeled categories that follow the typical stages of an attack simulation. It starts with reconnaissance, which covers tools for mapping a target's external footprint, including scanning subdomains, enumerating DNS records, scraping credentials from public sources, and taking automated screenshots of web properties. From there it moves into resource development (building payloads), initial access (gaining a foothold), and further stages like execution, persistence, privilege escalation, and lateral movement.

Beyond the tool listings, the README also includes a section of red team tips: short, practical techniques shared by the security community. These range from finding internal endpoints stored in browser bookmarks to methods for temporarily disabling antivirus software during an authorized test. Each tip credits the person who shared it.

The repository is intended for security professionals, students, and researchers working in authorized testing contexts. The authors include a clear warning that the materials are for educational and informational purposes only and are not intended for illegal use. A companion repository called BlueTeam-Tools covers the defensive side of the same field.

Because the full list runs to many hundreds of entries across dozens of categories, the README is very long. Only a portion of it was available for this summary. The full README is longer than what was shown.

Where it fits