Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/loseys/awesome-c2-frameworks
Penetration Testing FrameworksExploit FrameworksLateral MovementInformation GatheringPost-ExploitationPenetration TestingCommand and ControlRed TeamingCurated ResourcesPayload DevelopmentAdversarial Attack
GitHubloseys/awesome-c2-frameworks

awesome-c2-frameworks

Curated catalog of 2026 command-and-control frameworks for red team operations, with per-tool breakdowns of implants, listeners, payloads, and evasion features.

View Repository
42 days agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools →
Share

Awesome

Awesome Command & Control. Field catalog 2026.

Awesome Command & Control (C2) - 2026 Edition

The best C2 tools of 2026 for red team operations. Disclaimer: this project is for security professionals doing authorized work and study.


Index

  • Open Source
  • Commercial
  • Comparison

Open Source

NukeRat

NukeRat is a post-exploitation framework and C2 for advanced red team operations. The README centers on an armory of BOF and .NET utilities, implants for Windows, Linux, and macOS, and reports of commands, IOCs, and compromised hosts.

It comes with runtime evasion containing indirect syscalls, stack spoofing, and a sleep mask.

  • Repository: https://github.com/nukeratframework/nukerat

  • Tutorial: https://www.youtube.com/watch?v=3dOcPoVXv30

[!NOTE] Click below to see more details.

More details
Repositorynukeratframework/nukerat
Primary languageTypeScript, as reported by GitHub. The tree also contains a Python entrypoint, a server, a client, and implants.
LicenseGPL-3.0. The README also names MIT pieces (SGN, Nim crypt utils) and a GPLv3 LOLBAS reference copy.
Created6 November 2026
Last push14 November 2026
Stars / forks263 / 65
Docs languagesEnglish, Spanish, Korean, Simplified Chinese, Russian, Persian, Japanese

Docs · Armory · Disclaimer. The docs home describes BOFs and .NET tools from the official repository, run from the client, plus stageless and loader builds. Repository topics also include active-directory, edr-bypass, and lateral-movement. Those three stay topics. The feature table gives them no row, so they are not categories.

CategoryIn the project's wordsSource
ArmoryMore than 550 adapted BOF and .NET utilities.README
External-platform C2Custom C2 with external platforms. The examples named are Telegram and Discord.README
Runtime evasionA feature row under that name.README
InjectionsA feature row for allocation modes.README
Living off the landIntegration with more than 240 native Windows binaries, cited as LOLBAS.README
Static evasionA feature row for PE customization.README
ImplantsCross-platform: Windows, Linux, and macOS, with ARM support.README
Linux BOFLinux implants described as compatible with Linux BOFs.README
AIIntegration with agents. The examples named are DeepSeek and local agents.README
ReportsExecuted commands, IOCs, and compromised hosts.README
ClientThe docs say the armory tools are ready to run from the client. The README includes a gallery.Docs

NukeRat workspace with a session graph, a remote view, a console, and a process list.

Sliver

Sliver is Bishop Fox's framework for adversary emulation and authorized red team work. The server and client run on Windows, Linux, and macOS, and the implants officially support those same three, with C2 over mutual TLS, WireGuard, HTTP(S), and DNS.

  • Repository: https://github.com/BishopFox/sliver

[!NOTE] Click below to see more details.

More details
Primary languageGo
LicenseGPL-3.0
Last push14 November 2026
Stars / forks12,337 / 1,674

The README says implants are dynamically compiled with unique per-binary asymmetric encryption keys, and that they support native and shellcode payloads, userspace reflective loading, built-in shellcode encoding, and BOF/COFF execution on amd64 and arm64.

CategoryIn the project's wordsSource
TransportsMutual TLS, WireGuard, HTTP(S), and DNS.README
ImplantsWindows, Linux, and macOS. BOF/COFF on amd64 and arm64 for those three.README
Per-build keysUnique per-binary asymmetric encryption keys.README
Payload formsNative and shellcode payloads, userspace reflective loading, built-in shellcode encoding.README
ArmoryThe Armory page describes a package manager for aliases and extensions, including BOFs and .NET tooling. The armory index lists 22 aliases and 157 extensions. Aliases wrap .NET assemblies or shared libraries. Extensions are BOFs or native libraries. Packages install on the client and are not shared across operators in multiplayer. Signed packages come from the Sliver Armory GitHub organization.Docs
AI storeThe same Armory page describes a separate server-side store for an AI agent, distinct from the client Armory.Docs
Adversary emulationThe README's own name for the project.README

Sliver console with the block logo and an open listener.

Havoc

Havoc is a malleable post-exploitation command-and-control framework by @C5pider. The client is a cross-platform Qt UI, the teamserver is Go, and the flagship agent is Demon, written in C and assembly. GitHub marks the repository archived.

  • Repository: https://github.com/HavocFramework/Havoc

[!NOTE] Click below to see more details.

More details

Site: havocframework.com. Wiki: Havoc wiki.

Primary languageGo
LicenseGPL-3.0
Last push18 December 2025
Stars / forks8,501 / 1,272
Repository stateArchived, in the GitHub API.

The teamserver is described as multiplayer, with payload generation, HTTP/HTTPS listeners, customizable C2 profiles, and External C2. Demon's README section lists SMB support, a token vault, and built-in post-exploitation commands, and it also lists sleep obfuscation, x64 return-address spoofing, indirect syscalls, and AMSI/ETW patching via hardware breakpoints.

The same README states that Havoc was not developed to be evasive. It was designed to be malleable and modular, so an operator can add custom features or modules. That sentence decides the category. Evasion is not one of them.

Download Tool