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
Heroinn — A cross platform C2/post-exploitation framework. | Kitploit
Tools/GitHubGitHub/b23r0/heroinn
Penetration Testing FrameworksPersistence MechanismsLateral MovementData ExfiltrationPost-ExploitationCommand and ControlUtilities & FrameworksRed TeamingRemote Access ToolPayload DevelopmentRemote Access Trojan
GitHubb23r0/heroinn

Heroinn

A cross platform C2/post-exploitation framework.

View Repository
7122233634 days agoReviewed by Kitploit
Share

Heroinn logo

English · 简体中文

CI License: GPL-3.0 Discord

Heroinn

Heroinn is a cross-platform command-and-control and post-exploitation framework written in Rust. It combines a desktop server application, lightweight agents, an interactive PTY shell, a resumable file manager, and a client generator for authorized security research and red-team exercises.

Authorized use only. Use Heroinn exclusively on systems you own or have explicit permission to test. You are responsible for complying with all applicable laws and authorization requirements.

Heroinn server GUI

Features

  • Desktop GUI for managing listeners, online agents, shell sessions, and files.
  • Interactive PTY shell with a dedicated terminal window per session.
  • File manager with resumable transfers and large-file support.
  • Agent generator configurable to connect to the server through a SOCKS5 proxy, including a proxy chain with the system proxy.
  • Configure the aggregate transfer-rate limit per agent (default 1 MB/s).
  • SOCKS5 reverse proxy support through proxy chains.
  • TCP, HTTP, and reliable UDP transports.
  • End-to-end encrypted transport (Noise_NN_25519_ChaChaPoly_BLAKE2s)
  • Windows 10+ (Windows Server 2019+), Linux, BSD, and macOS support.
  • For TCP and HTTP communication, agents automatically discover the proxy from environment variables or the current desktop/user system settings and can connect through HTTP CONNECT, HTTPS (TLS-to-proxy when an explicit https:// proxy URL is used), or SOCKS5. Reliable UDP and loopback IPC remain direct.

Requirements

  • Rust 1.95 or newer with Cargo.
  • Linux build dependencies:
sudo apt-get install -y \
  build-essential pkg-config cmake libssl-dev \
  libfontconfig1-dev libfreetype6-dev libexpat1-dev \
  libx11-dev libx11-xcb-dev libxcb1-dev libxrandr-dev \
  libxi-dev libxcursor-dev libxinerama-dev \
  libxkbcommon-dev libxkbcommon-x11-dev libwayland-dev \
  libegl1-mesa-dev libvulkan-dev
  • Windows: a normal Rust MSVC toolchain is recommended. Heroinn uses Schannel for TLS and does not require OpenSSL development packages.
  • At runtime on Linux, the terminal component needs libX11, libxcb, libEGL, libwayland-client, libxkbcommon, and libvulkan.

Build

git clone https://github.com/b23r0/Heroinn.git
cd Heroinn
cargo build --release --locked

The build produces five executables:

  • heroinn — server GUI
  • heroinn_client — agent
  • heroinn_ftp — file manager
  • heroinn_shell — terminal window used by interactive shell sessions
  • heroinn_socks5proxy — reverse SOCKS5 proxy GUI used by online agents

heroinn_shell, heroinn_ftp, and heroinn_socks5proxy must be placed next to the heroinn executable because the server launches them from its working directory.

Client generation

The server's Generator tab does not compile an agent. It copies a prebuilt heroinn_client and rewrites its embedded connection stamp in place.

For TCP and HTTP agents, the Generator can also embed an optional SOCKS5 proxy. If the generated agent discovers a system proxy, it connects through the system proxy to the configured SOCKS5 proxy and then to the server, forming a proxy chain. SOCKS5 settings are not available for UDP agents. Any SOCKS5 credentials are embedded in the generated client binary and may be extractable.

Templates are searched next to the running heroinn executable first, then in the current working directory. Both legacy platform-suffixed names and normal Cargo output names are accepted:

PlatformTemplate names
Windows x86_64heroinn_client_windows.exe, heroinn_client.exe
Linux x86_64heroinn_client_linux, heroinn_client
BSD x86_64heroinn_client_bsd, heroinn_client
macOS x86_64heroinn_client_darwin, heroinn_client

Build a native agent with cargo build -p heroinn_client --release --locked and keep it next to the server. Cross-platform agents must first be compiled for their target and copied under one of the matching names above.

The generated executable inherits the template's permissions, including the Unix executable bit. Connection information is limited to 1024 bytes of JSON, and the generator rejects templates containing more than one valid stamp.

Workspace

PathPurpose
heroinnServer GUI and controller
heroinn_clientCross-platform agent
heroinn_coreShared application-core logic
heroinn_utilProtocol, transport, packet, and utility layers
th3rd/heroinn_ftpFile manager
th3rd/heroinn_socks5proxyReverse SOCKS5 proxy GUI and sidecar
th3rd/heroinn_shellTerminal implementation used by heroinn_shell

First-party crates use edition 2024 and share dependency versions pinned at the workspace root in [workspace.dependencies]. Vendored terminal crates retain their upstream editions.

The vendored terminal driver removes the two inherited PTY backends because Heroinn connects through a local TCP socket. The existing windowing stack is kept on its current glutin release to avoid a separate full rewrite of the terminal event loop.

Contributing

Bug reports, feature suggestions, pull requests, and documentation improvements are welcome. Before opening a pull request, run the same checks used by CI:

cargo fmt -p heroinn_ftp -- --check
cargo metadata --format-version 1 --locked --no-deps
cargo check --workspace --lib --bins --locked
cargo clippy -p heroinn -p heroinn_client -p heroinn_core -p heroinn_util -p heroinn_ftp -p heroinn_socks5proxy --all-targets --locked -- -D warnings
cargo test --workspace --exclude heroinn_shell_terminal --locked
cargo test -p heroinn_shell_terminal --lib --locked
cargo test -p heroinn_shell_config_derive --test config --locked
cargo build --workspace --release --locked
HEROINN_CLIENT_TEMPLATE=target/release/heroinn_client \
  cargo test -p heroinn_util --test real_client_template --locked -- --ignored --exact patches_a_real_client_template

On Windows PowerShell, set $env:HEROINN_CLIENT_TEMPLATE = "target/release/heroinn_client.exe" before running the same test command.

Join the community on Discord.

License

Heroinn is distributed under the GNU General Public License v3.0. The project logo is an original asset distributed with the project under the same license.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    755
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    510
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    415
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    343
  • 5

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    259
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    258

Explore all tools

Browse our collection of tools

View all tools →