215 curated tools across 21 categories — recon, OSINT, web, wireless, phishing, forensics, post-exploitation and more — with an AI layer that turns plain English into the right tool and the exact command.
Built for penetration testers · red teamers · blue-team/SOC and DFIR analysts · OSINT researchers · bug-bounty hunters · CTF players · security researchers and students — all working legally, on systems they own or are authorised to test.
- Why hackingtool
- Tool Categories
- Installation
- Quick Commands
- Features
- Documentation
- Contributing
- Support & Sponsor
- Social
- 🧠 AI-guided workflow — describe what you want ("find subdomains of example.com") and it maps your intent to the right tools, hands you the exact documented command, plans an objective step by step, then summarizes findings and drafts an engagement report. Bring your own key or run a local model — nothing auto-executes and nothing is fabricated.
- 🗂 215 curated tools, one console — install and run across 21 categories without hunting down Git repos; a fixed tag taxonomy (63 tags in use) makes every tool discoverable.
- 🔎 It knows what it doesn't have —
/findsearches your catalog first, then the GitHub API, and shows real maintained projects with the reason each was ranked. - 🛡 Safe by default — standard installs, no
curl | bash, downloads pinned + SHA-256 verified, list-formsubprocess, no forcedsudo, and signed releases with an SBOM. - 🎯 For the whole spectrum — red team, blue team, OSINT, bug bounty, CTF/THM, forensics/IR — all on authorized targets only.
The console on launch — live system readout, and
/ opens the command palette.
215 tools across 21 categories — the full list, with links and tags, is in docs/TOOLS.md.
| # | Category | Tools | # | Category | Tools | |
|---|---|---|---|---|---|---|
| 1 | 🛡 Anonymously Hiding Tools | 5 | 12 | 🔁 Reverse engineering tools | 10 | |
| 2 | 🔍 Information gathering tools | 26 | 13 | ⚡ DDOS Attack Tools | 7 | |
| 3 | 📚 Wordlist Generator | 8 | 14 | 🖥 Remote Administrator Tools (RAT) | 4 | |
| 4 | 📡 Wireless attack tools | 17 | 15 | 🧪 XSS Attack Tools | 6 | |
| 5 | 💉 SQL Injection Tools | 7 | 16 | 🖼 Steganography Tools | 10 | |
| 6 | 🎣 Phishing attack tools | 13 | 17 | 🏢 Active Directory Tools | 10 | |
| 7 | 🌐 Web Attack tools | 23 | 18 | ☁ Cloud Security Tools | 7 | |
| 8 | 🔧 Post exploitation tools | 15 | 19 | 📱 Mobile Security Tools | 6 | |
| 9 | 🕵 Forensic tools | 12 | 20 | ✨ Other tools | 10 | |
| 10 | 📦 Payload creation tools | 6 | 21 | 🔑 Password / Hash Cracking | 7 | |
| 11 | 🧰 Exploit framework | 6 |
59 further entries are archived (unmaintained or dead upstream) and hidden unless
you set show_archived true via /config. The in-app header counts 22 categories /
217 tools because it also counts the built-in Update / Uninstall menu.
Requires Python 3.10+ on Linux or macOS (Kali, Parrot, Debian/Ubuntu, Arch,
…). Windows is not supported — the app tells you so and exits. No curl | bash:
every path below is a standard, verifiable install.
pipx installs hackingtool into its own isolated environment
and puts the hackingtool command on your PATH, so you can launch it from any
directory.
# 1 — get the code
git clone https://github.com/Z4nzu/hackingtool.git
cd hackingtool
# 2 — install it onto your PATH (isolated venv, no system Python touched)
pipx install .
# 3 — run it from anywhere
hackingtoolNo pipx yet?
# macOS
brew install pipx && pipx ensurepath
# Debian / Ubuntu / Kali
sudo apt install pipx && pipx ensurepathOpen a new shell after pipx ensurepath so the PATH change takes effect.
To update later: git pull && pipx install . --force. To remove it:
pipx uninstall hackingtool.
Alternative: uv tool install . (same result, uses uv instead of pipx)
git clone https://github.com/Z4nzu/hackingtool.git
cd hackingtool
uv tool install . # installs the `hackingtool` executable on your PATH
hackingtoolAlternative: plain venv + pip (no PATH changes)
git clone https://github.com/Z4nzu/hackingtool.git
cd hackingtool
python3 -m venv .venv && . .venv/bin/activate
pip install . # or: pip install -e . for an editable dev install
hackingtoolThe command is only on your PATH while that venv is activated.
uv creates the virtualenv and installs everything from
pyproject.toml / uv.lock in one step:
git clone https://github.com/Z4nzu/hackingtool.git
cd hackingtool
uv sync
uv run hackingtoolNo uv yet? pipx install uv (or see the
uv install docs).
Contributing? make setup wires the pre-push hook and make check runs the full
gate (lint + tests + catalog validation). See CONTRIBUTING.md.
Pull and run the published image:
docker run -it --rm hardikzinzu/hackingtool:latestOr build it locally from a checkout:
git clone https://github.com/Z4nzu/hackingtool.git && cd hackingtool
docker build -t hackingtool .
docker run -it --rm hackingtoolSome individual tools need a language runtime to install/run; the core app doesn't.
| Dependency | Version | Needed for |
|---|---|---|
| Go | 1.21+ | nuclei, ffuf, amass, httpx, katana, dalfox, gobuster, subfinder |
| Ruby | any | haiti, evil-winrm |
| tmux | any | background panes (/run … &, /panes, /attach) |
| Docker | any | Mythic, MobSF (optional) |
Launch hackingtool and type. There are only three kinds of input:
| You type | It means | Example |
|---|---|---|
/… |
a command you run | /search subdomain |
@… |
a thing you name | @nmap, @tag:osint |
| anything else | plain English "what I want to do" | crack a wifi handshake |
@ completes tool names — @tag: completes tags, / completes commands.
| Command | Aliases | What it does |
|---|---|---|
/run <tool> [args] [&] |
/open |
open a tool's menu; with a trailing & it runs in a background tmux pane instead (that's where args are used) |
/search <keyword> |
search tools by name, description or tag | |
/tags |
list every tag with its tool count | |
/ai <goal> |
/recommend, /r |
recommend tools for a goal |
/goal <objective> |
AI-plan an objective and run it step by step, with per-step confirmation | |
/find <need> |
/discover |
find tools for a need — your catalog first, then GitHub (suggest-only) |
/panes |
/jobs |
list background panes |
/attach |
attach to the background session (Ctrl-b d to return) |
|
/kill <label|all> |
kill one background pane, or all of them | |
/config [key value] |
view/change settings; /config test checks the AI connection, /config github checks the GitHub token |
|
/skill |
show the operator playbook | |
/update · /uninstall |
/remove |
update system packages or hackingtool · remove hackingtool and its tools |
/clear |
/cls |
clear the screen |
/back |
/b |
leave the current tool and go back |
/help |
/?, /h |
quick reference card |
/quit |
/q, /exit |
exit (also q, Ctrl-C, Ctrl-D) |
@<tool> |
open a tool (case-insensitive, fuzzy fallback) | |
@tag:<tag> |
list and pick from the tools carrying that tag |
Inside a category: 1–N pick a tool · 97 install everything not yet installed ·
98 archived tools · 99 back.
Inside a tool: 1 install · 2 run · c ask for the exact command for your goal ·
98 project page · 99 back.
/help — the same card, in the app.
On a non-interactive terminal (or without prompt_toolkit) hackingtool falls back to
the classic numbered menu, where / or s searches, t filters by tag, r or a
recommends, ? helps and q quits. Force it with hackingtool --classic.
New here? docs/HOW-TO-USE.md walks through each of these start to finish with numbered steps.
Searches the 215 curated tools first, then the GitHub search API, and ranks the results explainably. Suggest-only — it never clones, installs or runs anything — and it makes zero model calls.
/find crack a wpa handshake
In your toolbox (vetted)
• aircrack-ng (WiFi security suite)
• Kismet (wireless detector / WIDS)
• Reaver (WPS PIN attack)
• WiGLE (wardriving map & API)
• hashcat example hashes (WPA mode 22000)
Found on GitHub — NOT vetted by us
wifiphisher/wifiphisher 14713★ GPL-3.0
The Rogue Access Point Framework
14713★ · trusted author (ships in our catalog) · active · matches: security, wifi
git clone https://github.com/wifiphisher/wifiphisher
…
Press a to keep a result: it is saved to ~/.hackingtool/found.yaml as a
"Discovered tools" entry — title, tags, description, link, and no install or run
command, so a discovered entry can never execute anything. It shows up in your menu
and in /search next launch.
Out-of-scope asks (jamming, DoS, mass-targeting, malware) are refused before any network call, with an authorized alternative where one exists. Defensive/DFIR phrasing is never refused.
Works anonymously at 10 GitHub searches/minute; a no-scope, no-permission token
raises that to 30 — see
/config github.
/goal find live subdomains of example.com
hackingtool drafts a short plan of real commands (with the reason for each step and
an install hint for tools you don't have), asks you to confirm you are authorized
to test the target, then walks the steps: [y] run · [s] skip · [e] edit ·
[q] abort. Every step runs list-form — never through a shell — and each goal gets a
timestamped workspace under ~/.hackingtool/goals/ holding plan.json, a
UTC-stamped run.log, and the raw output of each step.
The model is called once, for planning; tool output is never fed back to it. With
no model configured, /goal degrades to tool recommendations for the same objective.
Bare text (or /ai) maps intent to tools. The model may only return tags from the
fixed taxonomy, and the catalog resolves tags → tools, so a tool can never be
invented; with no model reachable a stdlib keyword matcher answers instead.
/ai — pick one of the common tasks, or type the job in your own words.
/tags prints every tag in use with its live tool count; @tag:<name> opens the
tools carrying it; /search <keyword> matches names, descriptions and tags.
/tags — 63 tags in use, with the number of tools behind each.
Long scans shouldn't block your console. With tmux installed, /run <tool> … & opens
a labeled window in one detached hackingtool session:
/run nmap -sV -oA scan 10.0.0.5 &
▶ started 'nmap' in background — /attach to view
/panes lists them, /attach watches one (Ctrl-b d to come back), /kill <label>
or /kill all stops them, and the status line under the prompt shows ▶ N running.
No tmux? It says so and opens the tool inline instead; disable it entirely with
/config background_runner off.
/config opens a full-screen settings editor (↑↓ move, ←→ change, Enter edit,
t test the connection, Esc close); /config <key> <value> sets one key from the
prompt. Settings live in ~/.hackingtool/config.json.
The AI layer is opt-in and bring-your-own-key: an OpenAI-compatible endpoint when
ai_base_url + an API key are set, else a local Ollama, else
nothing — every feature degrades to a deterministic offline behaviour instead of
guessing. Your API key is written only to ~/.hackingtool/.env (mode 600), never to
config.json, and never printed back. /config test reports the real failure if a
probe fails.
The same catalog drives a non-interactive orchestrator that normalizes tool output
into one findings.json:
hackingtool --engagement acme --targets example.com --pipeline recon
hackingtool --engagement acme --report # deterministic Markdown report
hackingtool --engagement acme --ai-summary # opt-in triage of the REAL findings
hackingtool --engagement acme --ai-report # opt-in narrative draft (report.draft.md)Out-of-scope targets are flagged and logged before anything runs, and the AI passes only ever summarize findings that exist.
| Document | What's in it |
|---|---|
| How to use hackingtool | numbered walkthroughs: first run, /find, /goal, /config, background panes, headless mode |
| Tool catalog | every tool, by category, with links and tags |
| Operator playbook | the charter and grounding rules the AI layer runs under (also /skill) |
| SECURITY.md | disclosure policy, release verification, threat model |
| CONTRIBUTING.md | catalog-first tool additions, the gate your PR must pass |
New tools, fixes, and docs are all welcome — for authorized security testing only.
The easy path: most tools are just one YAML entry in
src/hackingtool/catalog/— no Python needed. Tags come from a fixed taxonomy, so your tool is instantly discoverable and searchable.
| I want to… | Do this |
|---|---|
| 💡 Suggest a tool | Open a Tool Request issue |
| ➕ Add a tool | Add a catalog entry (or a class for custom install/run logic), then open a PR with the template |
| 🐛 Report a bug | Open a Bug report issue |
| 🔒 Report a vulnerability | Privately — do not open a public issue; see SECURITY.md |
Before opening a PR, run make check (lint + tests + catalog validation) and use
the title format [New Tool] Name — Category. The full guide — security rules and the
one-entry catalog walkthrough — is in CONTRIBUTING.md.
📄 Contributing · Security · Code of Conduct
hackingtool is free and open-source. If it saves you time on an engagement or helps you learn, please consider sponsoring — funding goes to tool curation, the AI layer, and keeping installs safe and current.
⭐ Starring the repo is free and helps others discover the project.
For authorized security testing only. Thanks to all original authors of the tools included in hackingtool.
Your favourite tool is not listed? Suggest it here