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.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Hexestra — AI-native penetration testing IDE where operators and an AI agent share browser, terminals, traffic capture, shells, asset graph, tasks, and evidence in one project workspace. | Kitploit
Tools/GitHubGitHub/absllk/hexestra
Penetration Testing FrameworksReconnaissanceNetwork MappingVulnerability AnalysisWeb Proxies & InterceptionInformation GatheringPenetration TestingCommand and ControlRed TeamingAI Security
GitHub
4233515 days agoReviewed by Kitploit
absllk/hexestra

Hexestra

AI-native penetration testing IDE where operators and an AI agent share browser, terminals, traffic capture, shells, asset graph, tasks, and evidence in one project workspace.

View Repository

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share
Hexestra

Orchestrate your pentest.

An AI-native penetration testing IDE where human operators and AI share the same browser, terminals, traffic, asset graph, tasks, evidence, and controls.

English · 简体中文

User guide · Docs index

[!WARNING] Hexestra is intended exclusively for authorized security testing. Never use it against systems you do not own or have explicit permission to assess.

Why Hexestra?

Hexestra brings the fragmented parts of a penetration test into one project. Scope labels give the Agent semantic asset context, while the operator can inspect, guide, approve, interrupt, or take over at any time.

  • One shared operational surface: human and AI work with the same browser, terminal sessions, captured traffic, tasks, assets, and evidence.
  • Controlled autonomy: choose ASK, AUTO, or BYPASS while preserving Rules of Engagement and technical safety boundaries; Scope labels remain advisory.
  • Keep the tools you know: continue using Claude Code, Burp Suite, PowerShell, WSL, SSH, and their existing configurations instead of learning a closed replacement.
  • Durable engagement state: reopen a project folder to restore Scope, tasks, NetMap, evidence, findings, reports, workspace tabs, permissions, and conversation branches.

Screenshots

These screenshots use the fictional Northstar Demo Lab, reserved example.test domains, documentation-only IP addresses, synthetic identities, and synthetic evidence.

Hexestra shared workspace with task tree, report, Agent activity, and NetMap

The shared workspace keeps the task tree, report, Agent activity, active asset, and 17-node NetMap in one controllable surface.

Hexestra Inventory showing target asset list, selected target details, and AI summary

Target assets are displayed on the left, with related assets and details shown below in NetMap.

Hexestra Evidence record with raw HTTP response and linked records

Evidence preserves raw output and links it to the Finding and validated Vulnerability.

Hexestra Vulnerability record with severity, impact, and remediation

A validated Vulnerability keeps severity, lifecycle, impact, remediation, and linked context together.

Hexestra built-in browser and traffic capture

Use the built-in browser to access targets; enable capture on the left to record traffic, with interception and replay support.

Core capabilities

  • Integrated browser, HTTP/HTTPS capture, inspection, interception, Repeater, and evidence capture
  • Shared local, WSL, SSH, jump-host, and raw reverse-shell sessions with human takeover and Agent command auditing
  • Graph-guided testing through typed assets, relationships, provenance, and active objectives in NetMap
  • Structured progression from raw output to Evidence, Finding, Vulnerability, and Report
  • Non-destructive conversation branches that preserve the original reasoning path and canonical project state
  • Optional Burp Bridge and Burp MCP integration without replacing the normal Burp workflow
  • Optional per-project Mihomo multi-hop egress with encrypted nodes and fail-closed managed routing

Quick start

Requirements

  • Node.js 24 and npm
  • Windows x64, Linux x64 (Ubuntu 24.04 baseline), macOS Intel, or macOS Apple Silicon
  • Standard Electron desktop libraries; Ubuntu needs the usual X11/GTK runtime libraries
  • Claude Code installed separately on the host for the selected Native or WSL runtime; Hexestra does not bundle or install it
  • mitmproxy is bundled in packaged builds; source runs may provide it separately
  • Optional Burp Suite and JDK 17 for the Bridge
  • Optional user-provided Mihomo for project-level multi-hop egress (v1.19.29 is tested and recommended, but not required)

Install Claude Code

Run these commands in the Native or WSL environment selected under Settings > Connection:

root@kitploit:~
npm install -g @anthropic-ai/claude-code
claude --version

To use an Anthropic account:

root@kitploit:~
claude auth login
claude auth status

Configure a third-party API

Set provider variables in the same terminal that will start Hexestra. DeepSeek example from its official Claude Code integration guide:

Linux and macOS:

root@kitploit:~
export ANTHROPIC_BASE_URL=https://api.deepseek.com/anthropic
export ANTHROPIC_AUTH_TOKEN="YOUR_DEEPSEEK_API_KEY"
export ANTHROPIC_MODEL='deepseek-v4-pro[1m]'
export ANTHROPIC_DEFAULT_OPUS_MODEL='deepseek-v4-pro[1m]'
export ANTHROPIC_DEFAULT_SONNET_MODEL='deepseek-v4-pro[1m]'
export ANTHROPIC_DEFAULT_HAIKU_MODEL=deepseek-v4-flash
export CLAUDE_CODE_SUBAGENT_MODEL=deepseek-v4-flash
export CLAUDE_CODE_EFFORT_LEVEL=max

Windows PowerShell:

root@kitploit:~
$env:ANTHROPIC_BASE_URL="https://api.deepseek.com/anthropic"
$env:ANTHROPIC_AUTH_TOKEN="YOUR_DEEPSEEK_API_KEY"
$env:ANTHROPIC_MODEL="deepseek-v4-pro[1m]"
$env:ANTHROPIC_DEFAULT_OPUS_MODEL="deepseek-v4-pro[1m]"
$env:ANTHROPIC_DEFAULT_SONNET_MODEL="deepseek-v4-pro[1m]"
$env:ANTHROPIC_DEFAULT_HAIKU_MODEL="deepseek-v4-flash"
$env:CLAUDE_CODE_SUBAGENT_MODEL="deepseek-v4-flash"
$env:CLAUDE_CODE_EFFORT_LEVEL="max"

Replace the endpoint, token, and model names for another Anthropic-compatible provider. Never commit an API key.

Run from source

Run these commands in the Hexestra project root:

root@kitploit:~
npm ci
npm run electron:dev

Configure Traffic Capture and mitmproxy

When running Hexestra from source, install mitmproxy and confirm that mitmdump is available:

root@kitploit:~
uv tool install mitmproxy
mitmdump --version

Packaged builds include a mitmdump runtime, so Traffic Capture works without a separate mitmproxy installation.

Configure project-level Mihomo egress

Download Mihomo from the upstream releases, then select its executable under Settings > Proxy. v1.19.29 is the tested and recommended reference version, but Hexestra does not enforce an exact version: a runnable binary is accepted and compatibility is determined by configuration validation and Controller startup. Mihomo is an external, user-provided GPLv3 runtime; Hexestra does not download or redistribute it.

Proxy enforcement is isolated to the active project: no TUN or system proxy is enabled. Browser, Traffic/Replay, outer SSH or jump-host connections, and WebShell requests use the managed route. Local and WSL terminals receive HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, NO_PROXY, and WSLENV; programs that ignore these variables and open raw sockets can bypass the terminal boundary. Claude API traffic and secondary egress created by commands on a remote shell are outside v1.

When enforcement is on, a missing node, invalid chain, stopped/crashed runtime, or failed reload blocks managed egress instead of falling back to a direct connection. Run the real two-hop acceptance smoke with:

root@kitploit:~
HEXESTRA_MIHOMO_PATH=/path/to/mihomo npm run test:proxy-smoke

Configure the Burp Suite Bridge

Burp integration is optional. Hexestra captures traffic through mitmproxy and mirrors completed exchanges to Burp through an authenticated loopback Bridge; Burp is not silently inserted into the browser's live network path.

Build the Bridge on Windows, Linux, or macOS with JDK 17:

root@kitploit:~
npm run build:burp-bridge
  1. In Burp, open Extensions > Installed > Add, choose Java, and load resources/burp-bridge/hexestra-burp-bridge.jar.
  2. Open Hexestra Bridge, note the loopback port, and copy the pairing token.
  3. In Hexestra, open Settings > Burp, enter the port and token, save, and choose Connect Bridge.

Mirrored exchanges appear in Target > Site map and, when supported, Organizer. Burp's public extension API cannot create synthetic entries in Proxy > HTTP history.

Build and verify

root@kitploit:~
npm run electron:build
npm run audit:public
npm run check

Responsible use

Use Hexestra only with explicit authorization and an accurate project Scope. Destructive, disruptive, or privacy-impacting actions require appropriate approval, and exported evidence or reports should be treated as sensitive data. Scope labels guide Agent prioritization but do not block commands or traffic; ASK, AUTO, and BYPASS change approval behavior, while Rules of Engagement and technical safety boundaries remain enforced. Hexestra does not replace professional judgment or accountability.

Contributing

See the contribution guide and changelog.

License

Hexestra is licensed under the Apache License 2.0. Third-party components remain subject to their own licenses and terms.

Star History

Star History Chart
Download Tool