convez.ai
MCP ServerSegurançaAvançado
26zl

Cybersec Toolkit com MCP Server

26zl/cybersec-toolkit

580+ ferramentas de cibersegurança + MCP para IA assistida em testes éticos

Ver no GitHub
BomPluginScore · de 0 a 100

Toolkit modular com 580+ ferramentas de segurança ofensiva, integrado a um MCP server que permite IA assistir em testes éticos, CTFs e bug bounty. Instala automaticamente runtimes, dependências e oferece 14 perfis pré-configurados para diferentes cenários de ataque e defesa.

Instalação

$npx convez-ai 26zl/cybersec-toolkit

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
100
Forks
19
Acompanhando
0
Saúde
100%
Último commit
há 2 dias
Versão
v1.5.0
Issues abertas
1
Contribuidores
3

Casos de uso

  • CTFs e competições de segurança
  • Testes de penetração e red team
  • Bug bounty e vulnerability assessment
  • Reconhecimento e exploração com suporte IA

Veredito

Solução robusta e bem-mantida para profissionais de segurança ofensiva. O MCP server diferencia o toolkit ao permitir IA recomendarferramenta certas, executar com políticas de segurança e auditar comandos — ideal para fluxos assistidos em Claude e ferramentas compatíveis.

README

A tradução para o português deste README ainda está na fila.

CI Integration Security uv update Status: Under Active Development

   ______      __              _____
  / ____/_  __/ /_  ___  _____/ ___/___  _____
 / /   / / / / __ \/ _ \/ ___/\__ \/ _ \/ ___/
/ /___/ /_/ / /_/ /  __/ /   ___/ /  __/ /__
\____/\__, /_.___/\___/_/   /____/\___/\___/
     /____/                          by 26zl
              Toolkit

Cybersecurity toolkit with built-in AI integration. An embedded MCP (Model Context Protocol) server lets any MCP-capable AI -- Claude Code, Claude Desktop, Cursor -- query the tool registry, check install status, recommend the right tools for a CTF category or bug-bounty target, and execute them with enforced safety policies (argument sanitization, network allowlists, rate limiting, audit logging). Jump to MCP Server (AI Integration).

Bundled with a modular installer for Linux and Termux (Android) covering 580+ tools, 18 modules, 14 profiles, and 12 install methods.


Install

All required runtimes (Python, Go, Ruby, Java, Rust, Node.js), dev libraries, pipx, and build tools are installed automatically. The only prerequisite is a supported Linux distro. Windows and macOS are not supported (use WSL or Docker).

Docker is the one exception — install it manually if you want C2 frameworks, MobSF, BeEF, BloodHound, TheHive, or Cortex (--enable-docker). See Docker install docs. GitHub authentication is recommended. The installer downloads ~30 binary releases and makes ~30+ API calls to GitHub. Without auth, you're limited to 60 requests/hour and some downloads may fail. With auth, the limit is 5,000/hour. The easiest way:

# Install gh CLI and log in (one-time) — the installer auto-detects it
sudo apt install gh && gh auth login

Alternatively, export a personal access token (no scopes needed):

export GITHUB_TOKEN=ghp_xxxxxxxxxxxxxxxxxxxx
git clone https://github.com/26zl/cybersec-toolkit.git && cd cybersec-toolkit && sudo ./install.sh

That installs all 580+ tools. To install a subset:

sudo ./install.sh --profile ctf                      # CTF tools only
sudo ./install.sh --profile redteam --enable-docker   # Red team + Docker C2
sudo ./install.sh --module web --module recon          # Specific modules
sudo ./install.sh --tool sqlmap --tool nmap            # Individual tools
sudo ./install.sh --dry-run --profile ctf              # Preview without installing

Try in Docker

docker build -t cybersec-toolkit .
docker run cybersec-toolkit --profile ctf

macOS (Apple Silicon): Add --platform linux/amd64 to both commands to run via x86 emulation:

docker build --platform linux/amd64 -t cybersec-toolkit .
docker run --platform linux/amd64 cybersec-toolkit --profile ctf

Termux (Android, experimental):

Note: Termux support is under development and has not been fully tested on physical Android devices. Expect rough edges.

pkg install git
git clone https://github.com/26zl/cybersec-toolkit.git
cd cybersec-toolkit
./install.sh --profile lightweight
sudo ./install.sh --help                # Full help
sudo ./install.sh --list-profiles       # Show profiles
sudo ./install.sh --list-modules        # Show modules
sudo ./install.sh --skip-heavy          # Skip large/slow packages
sudo ./install.sh --skip-pipx           # Skip all pipx (Python) installs
sudo ./install.sh --skip-go             # Skip all Go tool installs
sudo ./install.sh --skip-cargo          # Skip all Cargo (Rust) installs
sudo ./install.sh --skip-gems           # Skip all Ruby gem installs
sudo ./install.sh --skip-git            # Skip all git clone installs
sudo ./install.sh --skip-binary         # Skip all binary release downloads
sudo ./install.sh --skip-source         # Skip build-from-source, snap, npm, and curl-pipe installs
sudo ./install.sh --fast                # Skip checksum verification (see Security note below)
sudo ./install.sh --require-checksums   # Fail if binary release has no checksum file
sudo ./install.sh --upgrade-system      # Upgrade system packages before installing
sudo ./install.sh --list-sessions       # List install sessions and exit
sudo ./install.sh --rollback <id|last>  # Rollback tools installed in a session
sudo ./install.sh --version             # Show installer version and exit
sudo ./install.sh --enable-docker       # Pull Docker images
sudo ./install.sh --include-c2          # Include C2 frameworks (needs --enable-docker)
sudo ./install.sh -j 8                  # 8 parallel install jobs (default: 4)
sudo ./install.sh -v                    # Verbose / debug output

--tool installs only the specified tool without running the full dependency setup. Dry-run time estimates count install entries across methods, so the estimate can be higher than the de-duplicated 580+ tool registry.

The installer orchestrates 580+ tools across 12 different install methods. The time is spent on I/O-bound operations that no scripting language can speed up:

What takes timeWhyTypical time
System packages (apt/dnf)Downloading and unpacking ~150 .deb/.rpm files, resolving dependencies~40%
Cargo (Rust) cratesCompiling from source — Rust has no pre-built registry binaries~25%
Go toolsDownloading modules and compiling ~30 binaries~15%
pipx (Python)Creating ~40 isolated venvs, downloading wheels~10%
Git clonesCloning ~30 repositories~5%
Binary releasesDownloading ~30 pre-built binaries from GitHub~4%
Bash overheadArray iteration, logging, progress bars<0.1%

The installer already parallelizes where possible (-j 4 by default). Methods with shared locks (apt, pipx, cargo) must run sequentially. To reduce install time:

  • Use --profile lightweight or --module <name> to install only what you need
  • Use --skip-cargo to skip Rust compilation (the slowest per-tool method)
  • Increase parallelism with -j 8 for faster Go/git/binary downloads
  • Set up an apt-cacher-ng proxy for repeated installs

Profiles

ProfileModulesDescription
fullAll 18Complete security toolkit
ctfmisc, crypto, pwn, reversing, stego, forensics, cracking, web, mobile, blockchainCTF competitions
redteammisc, networking, recon, web, enterprise, pwn, mobile, cracking, cloud, wireless, reversing, cryptoOffensive security
webmisc, networking, recon, web, llmWeb application testing
osintmisc, reconOSINT gathering
forensicsmisc, forensics, blueteam, reversing, stego, crackingDigital forensics and incident response
pwnmisc, pwn, reversing, cryptoBinary exploitation and reverse engineering
mobilemisc, mobile, web, reversingMobile application security testing
cloudmisc, cloud, containers, networking, reconCloud and container security auditing
blockchainmisc, blockchain, web, cryptoSmart contract auditing and blockchain security
wirelessmisc, wireless, networkingWiFi, Bluetooth, and SDR security
lightweightmisc, networking, recon, web, crackingHobby ethical hacking essentials (HTB, THM, bug bounty)
crackstationmisc, cracking, cryptoHash cracking
blueteammisc, blueteam, forensics, reversing, mobile, containers, networking, cloud, reconDefensive security, IR, malware analysis

Modules

ModuleToolsDescription
misc35Post-exploitation, social engineering, wordlists, resources, C2 (Docker)
networking53Port scanning, packet capture, tunneling, MITM, protocol tools
recon74Subdomain enumeration, OSINT, DNS, automated recon frameworks
web51Vulnerability scanning, fuzzing, SQLi, XSS, CMS scanners, API testing
crypto13RSA attacks, cipher analysis, hash attacks, constraint solving
pwn33Exploit frameworks, binary exploitation, fuzzing, payload generation
reversing31Disassemblers, debuggers, emulation, Java/Python reversing
forensics50Disk/memory forensics, file carving, timeline analysis, log analysis, hardware/serial
enterprise76Active Directory, Kerberos, Azure AD, credential harvesting, lateral movement
wireless39WiFi cracking, Bluetooth, SDR, rogue AP
cracking28Hash cracking (john, hashcat), brute force, wordlist generation
stego13Image/audio steganography, detection, StegCracker
cloud15AWS/Azure/GCP security auditing, Checkov
containers8Docker/Kubernetes security (Grype, Syft, Kubescape, kubeaudit)
blueteam31IDS/IPS, SIEM, incident response, threat intelligence, hardening, malware analysis (YARA, ClamAV, FLOSS, Capa, Loki)
mobile12Android/iOS app testing, APK analysis, MobSF (Docker)
blockchain12Smart contract auditing (Slither, Mythril, Foundry, Aderyn), blockchain forensics, Echidna (Docker)
llm9LLM red teaming, prompt injection, jailbreak testing, AI vulnerability scanning

Install Methods

MethodCountExamples
Git clone~176GitHub repos with auto-setup, resources, wordlists
System packages (apt/dnf/pacman/zypper)~164nmap, wireshark, john, hashcat
pipx~116sqlmap, impacket, bloodhound, volatility3
Go install~53nuclei, subfinder, ffuf, httpx
Binary release~35gitleaks, chainsaw, findomain, FLOSS, Capa, Loki, Syft, Kubescape
Build from source~12massdns, duplicut, AFLplusplus, honggfuzz
Docker~9Empire, MobSF, BeEF, BloodHound, TheHive, Cortex, PentAGI
Ruby gem6wpscan, evil-winrm, brakeman
Cargo (Rust)5feroxbuster, RustScan, pwninit, yara-x-cli
Special (curl-pipe)3Metasploit, Foundry, Steampipe
Snap1zaproxy
npm1promptfoo

Post-Install Scripts

All scripts require root on Linux (sudo) and support --help. On Termux, no root is needed.

ScriptPurposeExample
scripts/verify.shCheck which tools are installedsudo ./scripts/verify.sh --module web --skip-heavy
scripts/update.shUpdate all installed toolssudo ./scripts/update.sh --skip-system
scripts/remove.shRemove tools by modulesudo ./scripts/remove.sh --module enterprise --yes
scripts/remove.sh --deep-cleanPurge all caches and build artifactssudo ./scripts/remove.sh --deep-clean --yes
scripts/backup.shBackup/restore tool configssudo ./scripts/backup.sh backup

--deep-clean removes Go module/build cache, Cargo registry, pip/pipx/npm/gem caches, orphaned pipx venvs, stale symlinks, and log files. Add --remove-deps to also purge Rustup toolchains.

MCP Server (AI Integration)

MCP (Model Context Protocol) is an open standard that lets AI assistants use external tools. This project includes an MCP server that gives any MCP-capable AI (Claude Code, Claude Desktop, Cursor, etc.) full read access to the 580+ tool registry — plus the ability to check installs, recommend profiles, and execute tools. The AI becomes an interactive partner for ethical hacking: it knows every tool, which ones you have installed, and can run them for you.

What the AI can do

ToolWhat it does
list_toolsList/filter all 580+ tools by module, method, or install status (includes URLs)
check_installedCheck if a tool is installed (5 detection strategies)
get_tool_infoFull details: method, module, URL, install/update/remove commands
get_module_infoDeep-dive a module: all tools, install status, which profiles use it
get_profile_toolsSee every tool a profile installs, grouped by module
suggest_for_ctfCurated tool recommendations for 13 CTF challenge categories
suggest_for_bountyBug bounty tool recommendations for 6 target types with methodology and common vulns
recommend_installNatural-language → profile/module/tool recommendation
list_profilesAll 14 profiles with tool counts and install commands
run_toolExecute installed tools safely (sanitized args, network policy, rate limiting, audit logging). Supports remote execution via SSH
run_pipelinePipe tools together safely without shell (strings binary | grep flag)
run_scriptWrite and execute Python/Bash scripts (pwntools, z3, requests, crypto). Supports per-script venv selection
manage_remote_hostsAdd, remove, list, and test SSH remote hosts for remote tool execution

The AI knows every tool, what's installed, and runs them under policy — so you can drive whole engagements conversationally, red team or blue. It selects tools, chains them, parses the output, and pivots on what it finds.

External recon → attack surface (needs CYBERSEC_MCP_ALLOW_EXTERNAL=1, authorized scope only)

  • "Enumerate the attack surface for target.com and flag anything exploitable" — fans out amass / subfinder → resolves and probes with httpx → fingerprints with whatweb → runs nuclei templates → content-discovery with ffuf, then ranks hosts by exposure and proposes next steps
  • "Found an open redirect on /go?url= — weaponize it" — verifies with curl, then builds an SSRF / OAuth-token-theft PoC and probes for an exploitable callback

Web exploitation

  • "Confirm and exploit the SQLi on the login endpoint" — sqlmap to confirm and dump (destructive --os-shell/--os-cmd are policy-blocked), then run_script to automate the auth bypass and pull just enough for a PoC
  • "GraphQL introspection is on — map it and hunt IDOR" — pulls the schema, generates queries, fuzzes object IDs, and diffs authenticated vs unauthenticated responses

Active Directory / internal

  • "Low-priv creds on 10.10.0.0/24 — find a path to Domain Admin" — collects with bloodhound, kerberoasts with impacket (GetUserSPNs.py), cracks the TGS in hashcat, then validates lateral movement with netexec — all over the Kali VM via SSH
  • "Check for DCSync rights and dump if the path exists" — enumerates replication ACLs, then runs secretsdump.py against the DC

Binary exploitation & reversing

  • "Build a ret2libc exploit for this 64-bit binary" — triages with checksec / readelf, finds gadgets with ROPgadget, leaks libc via a puts@plt call, then writes the full pwntools chain in venv="pwntools" and pops a shell locally
  • "Recover the algorithm from this stripped binary" — objdump / radare2 disassembly piped into targeted analysis, then a run_script reimplementation to verify behavior

Crypto

  • "Break this RSA — small e, several ciphertexts" — detects the attack (Håstad / common-modulus / Wiener) and solves it with pycryptodome + sympy in a venv, returning plaintext
  • "This JWT is HS256 with a weak key" — cracks the signing secret and forges an admin token

Blue team · detection engineering

  • "Write a Sigma rule for this technique and convert it to my SIEM" — authors the rule and renders it for the target backend (Splunk / Elastic) via sigma-cli
  • "Hunt these Windows event logs for lateral movement" — runs chainsaw over the EVTX with Sigma rules, then summarizes hits by host and timeline
  • "Build YARA rules from these samples and scan the tree" — generates yara signatures and runs them recursively

DFIR · malware triage

  • "Timeline this memory dump" — sweeps volatility3 plugins (pslist, netscan, malfind) and chains them into one narrative
  • "Hunt for C2 beaconing in this pcap" — tshark / tcpdump extraction → suricata rules → flags periodic callbacks
  • "Statically triage this suspicious file" — file → strings → capa / yara, then extracts IOCs for enrichment

Cloud · containers · ops

  • "Audit this AWS account for public S3 and risky IAM" — runs prowler / scoutsuite and surfaces only the high-severity findings
  • "Scan this image and k8s manifests before deploy" — grype image scan plus kubescape config checks
  • "What's my redteam coverage — and fix the gaps" — diffs get_profile_tools("redteam") against install status and emits the exact install commands

Mobile · wireless · blockchain

  • "Static-analyze this APK for secrets and insecure storage" — apktool / jadx decompile → MobSF-style checks, then greps for keys and endpoints
  • "Audit this Wi-Fi capture" — parses the handshake and runs aircrack-ng / hashcat against it
  • "Review this Solidity contract for reentrancy" — runs slither / mythril and explains the findings

Every execution is argument-sanitized, network-policed, rate-limited, and audit-logged. run_script and external targets are off by default; destructive flags (--os-shell, -rf, --exploit, …) are blocked outright. Use only against systems you are authorized to test.

Quick Start

Requires uv. Claude Code can use the tracked project .mcp.json directly. It runs the MCP server over stdio with scripts and external network targets disabled by default:

{
  "mcpServers": {
    "cybersec-tools": {
      "command": "uv",
      "args": ["run", "--directory", "mcp_server", "fastmcp", "run", "server.py", "--transport", "stdio", "--no-banner"],
      "env": {
        "CYBERSEC_MCP_ALLOW_EXTERNAL": "0",
        "CYBERSEC_MCP_ALLOW_SCRIPTS": "0"
      }
    }
  }
}

Restart Claude Code. The 13 tools appear in /mcp.

Other MCP clients (Codex, Cursor, local LLMs)

MCP is an open standard, so the same stdio server works with any MCP-capable client. From the repo root the launch command is:

uv run --directory mcp_server fastmcp run server.py --transport stdio --no-banner

--directory mcp_server is relative to the working directory, so if a client may start the server from a subdirectory, wrap it to move to the repo root first:

bash -lc 'cd "$(git rev-parse --show-toplevel)" && exec uv run --directory mcp_server fastmcp run server.py --transport stdio --no-banner'
  • Codex — a project .codex/config.toml is included (mirrors .mcp.json, using the git-root wrapper above so it works from any subdirectory). Codex's primary config is ~/.codex/config.toml; if the project file isn't picked up, copy the [mcp_servers.cybersec-tools] block into your home config.
  • Cursor / Continue / Cline / Roo / Goose — add the same launch command in the client's MCP settings UI or config file (use the wrapper form if the client's working directory isn't the repo root).
  • LM Studio (≥0.3.17) — LM Studio is itself an MCP host, no bridge needed. Add the server to its mcp.json (Cursor notation, same mcpServers shape as .mcp.json) using an absolute path or the git-root wrapper, since LM Studio's working directory isn't the repo root. Using MCP via LM Studio's API requires ≥0.4.0 and an MCP-capable endpoint such as /api/v1/chat or /v1/responses.
  • Ollama — Ollama is a model runtime, not an MCP host. Put an MCP-capable agent in front of it (e.g. Kit) and point it at the launch command above.
  • Other local LLMs — a bare model does not speak MCP on its own. Run it behind any MCP-capable host (LM Studio, Cline, Continue, Goose, Kit, or Open WebUI via an MCP→OpenAPI bridge like mcpo) and point that host at the launch command above.

Security note: start with just this one server. It already enforces argument sanitization, network allowlists, rate limiting, and audit logging, and ships with script execution and external targets disabled by default — keep those off unless you have an authorized scope, and prefer hosts that support human-in-the-loop tool approval.

Vendor-neutral repo instructions live in AGENTS.md (read natively by Codex and many agentic tools); Claude Code reads CLAUDE.md.

Connect from WSL (e.g. Kali Linux)

The MCP server runs over stdio, so it works from any environment that Claude Code can spawn. To use tools installed inside WSL:

{
  "mcpServers": {
    "cybersec-tools": {
      "command": "wsl",
      "args": [
        "-d", "kali-linux",
        "bash", "-lc",
        "cd /path/to/cybersec-toolkit/mcp_server && uv run fastmcp run server.py --transport stdio --no-banner"
      ]
    }
  }
}

Connect from Docker

{
  "mcpServers": {
    "cybersec-tools": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm", "cybersec-toolkit",
        "bash", "-c",
        "cd /opt/cybersec-toolkit/mcp_server && uv run fastmcp run server.py --transport stdio --no-banner"
      ]
    }
  }
}

Script Execution

run_script lets the AI write and execute Python or Bash scripts. Requires CYBERSEC_MCP_ALLOW_SCRIPTS=1. External targets stay blocked by default; set CYBERSEC_MCP_ALLOW_EXTERNAL=1 only for explicitly authorized scopes:

{
  "mcpServers": {
    "cybersec-tools": {
      "command": "uv",
      "args": ["run", "--directory", "mcp_server", "fastmcp", "run", "server.py", "--transport", "stdio", "--no-banner"],
      "env": {
        "CYBERSEC_MCP_ALLOW_SCRIPTS": "1",
        "CYBERSEC_MCP_ALLOW_EXTERNAL": "0"
      }
    }
  }
}

Venv Support

Some packages (e.g. pwntools) require an older Python. The venv parameter lets the AI choose the right interpreter per script:

# One-time setup: create a venv with pwntools
python3.12 -m venv ~/.ctf-venvs/pwntools
~/.ctf-venvs/pwntools/bin/pip install pwntools z3-solver

The AI then uses run_script("from pwn import *; ...", venv="pwntools") automatically. Scripts that only need standard libs or the server's packages (requests, pycryptodome, beautifulsoup4) run without venv. Set CYBERSEC_MCP_VENVS_DIR to override the default ~/.ctf-venvs/ location.

Manual Scripts

The manual_scripts/ directory stores persistent scripts — complex exploits, multi-step solvers, and reusable tools that shouldn't disappear after execution. The AI writes scripts here when they're worth keeping.

Test the Server

cd mcp_server && uv run fastmcp dev server.py

This opens a web-based MCP Inspector for interactively testing each tool.

See mcp_server/README.md for Claude Desktop setup and full documentation.

Development

Public contributor docs live in CONTRIBUTING.md. The quick-start is:

git submodule update --init --recursive
shellcheck --severity=warning install.sh lib/*.sh modules/*.sh scripts/*.sh
bash -n install.sh lib/*.sh modules/*.sh scripts/*.sh
python3 scripts/validate_tools_config.py
python3 scripts/validate_mcp_sync.py
python3 scripts/validate_distro_compat.py
python3 scripts/validate_claude_skills.py
./tests/bats/bin/bats tests/*.bats
cd mcp_server && uv sync --group dev && uv run ruff check . && uv run ruff format --check . && uv run pytest tests/ -q

The MCP Python project uses uv with [tool.uv] exclude-newer = "3 days". New dependency resolutions intentionally ignore packages uploaded in the last 72 hours to reduce dependency-confusion and compromised-release blast radius. Dependabot uses the matching 3-day cooldown, and the weekly uv update workflow inherits the same policy.

This release-age policy is scoped to project bootstrap/runtime dependencies only: MCP Python packages, CI actions, and the Docker build inputs needed to get the project running. It does not delay or pin the cybersecurity tools installed from the registry; those tools intentionally follow their module installer and update flow so operators can get current scanners, exploits, signatures, and research utilities.

Run shell tests on Linux or WSL. Native Windows checkouts can rewrite the vendored Bats submodules with CRLF and cause $'\r' failures.

Claude Code Skills

This repo ships 857 Claude Code skills under .claude/skills/. They activate on demand based on the task — they don't permanently consume context.

  • 9 project-specific developer skills (add-tool, validate-all, module-scaffold, writeup-template, mcp-sync-check, security-wordlists, security-payloads, skill-dependency-audit, skill-curation-router)
  • 7 coverage gap anchor skills (GRC/privacy, AI/LLM security, IoT/embedded/hardware, mainframe, telecom/5G, SAP/ERP, supply-chain/product security)
  • 1 coding-agent workflow skill from multica-ai/andrej-karpathy-skills (MIT)
  • 6 CTF methodology skills (ctf-crypto, ctf-pwn, ctf-web, ctf-rev, ctf-forensics, ctf-stego)
  • 4 bug bounty methodology skills (bounty-recon, bounty-web, bounty-api, bounty-mobile)
  • 58 offensive methodology skills from SnailSploit Claude-Red (MIT)
  • 14 code audit skills from Trail of Bits (CC-BY-SA 4.0)
  • 754 operational how-tos from Anthropic Cybersecurity Skills (Apache 2.0)
  • 4 high-level workflows from Transilience (MIT)

Source and category index in .claude/skills/SKILLS.md.

Skills are a Claude Code feature, but the content is plain Markdown plus helper scripts. To use them with Codex or other agents that read .agents/skills/, mirror them (the .agents/skills/ copy is generated and git-ignored — .claude/skills/ stays the source of truth):

scripts/sync-skills.sh            # mirror .claude/skills/ -> .agents/skills/
scripts/sync-skills.sh --check    # report drift without writing (exit 1 if out of date)

scripts/validate_claude_skills.py checks skill metadata, index counts, curation freshness, and helper-script syntax for Python and PowerShell. Vendored skill helper scripts can also have optional task-specific Python imports. Audit those extras with:

python3 scripts/audit_skill_dependencies.py

Skill ranking/curation lives in .claude/skills/CURATION.md and .claude/skills/curation.json. Regenerate it with:

python3 scripts/curate_claude_skills.py --write

Tool Locations

Non-system tools (pipx, Go, Cargo, git, binary releases) are installed to /usr/local/bin/ on Linux and $PREFIX/bin on Termux. System packages go to their default location (/usr/bin/).

MethodBinary location (Linux)Binary location (Termux)Data location
pipx/usr/local/bin/$PREFIX/bin//opt/pipx/ or ~/.local/pipx/
Go/usr/local/bin/$PREFIX/bin//opt/go/ or ~/.go/
Cargo/usr/local/bin/ (symlinked)$PREFIX/bin/ (symlinked)~/.cargo/
Git repos/usr/local/bin/ (symlinked)$PREFIX/bin/ (symlinked)/opt/<repo>/ or ~/tools/<repo>/
Binary releases/usr/local/bin/Skipped (glibc incompatible with Bionic)--

Docker Images (optional)

Only used with --enable-docker. If Docker is not installed and --enable-docker is set, the installer exits with an error asking you to install Docker first.

ImageModuleFlagDescription
bcsecurity/empiremisc--enable-docker --include-c2Empire C2
spiderfoot/spiderfootmisc--enable-dockerSpiderFoot OSINT
beefproject/beefweb--enable-dockerBeEF browser exploitation
opensecurity/mobile-security-framework-mobsfmobile--enable-dockerMobSF
specterops/bloodhoundenterprise--enable-dockerBloodHound CE
trailofbits/echidnablockchain--enable-dockerEchidna smart contract fuzzer
strangebee/thehive:latestblueteam--enable-dockerTheHive IR platform
thehiveproject/cortex:latestblueteam--enable-dockerCortex analysis
vxcontrol/pentagi:latestllm--enable-dockerPentAGI autonomous pentesting

Distro Support

Debian/Ubuntu/Kali is the primary target -- the full 580+ registry is available there, and it has the strongest test coverage. Fedora/Arch/openSUSE have ~10-20 packages auto-skipped (distro-specific) and are covered by the integration workflow. WSL and ARM are supported in practice, but they do not yet have dedicated CI jobs. Windows and macOS are detected and blocked with a clear error message.

PlatformStatus
WSLSupported for installs and MCP usage. Wireless module auto-skipped (no hardware access) and kernel-level packages filtered. Validate release-critical changes in a local WSL distro because there is no dedicated CI job yet. See the Windows Defender note below if you keep the repo on a Windows-mounted path.
ARM (aarch64/armv7)Supported with automatic skips for x86-only binary releases and build-from-source tools. No dedicated CI job yet.
Termux (Android)Experimental. Under development, not covered by CI, and not yet broadly tested on physical devices. No sudo needed. Docker/snap/binary releases/build-from-source skipped (Bionic incompatible).
Windows (native)Not supported. Use WSL.
macOSNot supported. Use Docker container.

Supply Chain Model

This installer downloads and runs code from the internet. On Linux it runs as root (sudo); on Termux it runs in the app's user sandbox (no root).

  • System packages: GPG-signed by your distro's repos (apt, dnf, pacman, zypper, pkg)
  • pipx/Go/Cargo/Gem/npm: Downloads from registries (no signature verification, pipx isolated in venvs)
  • Binary releases: SHA256 verified when checksum file available, hard-fails on mismatch. Use --require-checksums to also fail when no checksum file is published. Warning: --fast disables all checksum verification, including for releases that do publish checksums — do not use in production or CI environments
  • MCP Python dependencies: Resolved by uv with a 3-day exclude-newer window; Dependabot also waits 3 days before proposing dependency PRs. This does not apply to installed security tools
  • Go SDK: SHA256 verified against go.dev published hashes when available; warns on API failure, hard-fails with --require-checksums
  • Git repos: Cloned at HEAD, deps installed in isolated venvs (setup.py is NOT executed)
  • Build from source: Runs make (as root on Linux) -- review what you're building

The .versions file logs what was installed and when.

Known Limitations

Checksum verification is best-effort by default. Some upstream releases do not publish checksums or signatures, so downloads may proceed without cryptographic verification in those cases. Use --require-checksums to fail-closed when no checksum file is available. Go SDK downloads are SHA256-verified against go.dev when the API is reachable; use --require-checksums to hard-fail if it is not.

--fast skips all checksum verification for binary releases (both SHA256 checks and the missing-checksum warning), including releases that do publish checksums. This trades integrity verification for speed. It is mutually exclusive with --require-checksums. Do not use --fast in CI pipelines or environments where supply-chain integrity matters.

Windows Defender false positives

If you clone this repo onto a Windows-mounted path (e.g. C:\Users\<you>\... or any folder visible from Windows while you work in WSL), Microsoft Defender and other AV products may quarantine individual files. Defensive content -- IOC reference tables, sample obfuscated PowerShell, malware analysis snippets, exploit PoC strings inside .claude/skills/, workflows/, and parts of mcp_server/ -- contains the same byte-strings real attackers use, so signature- and ML-based engines can flag them. Common detections include Trojan:Script/Wacatac.B!ml, HackTool:*, and generic Heur.* verdicts.

These are false positives in the context of a security toolkit. To work with the repo on Windows you have three options:

  1. Add a Defender exclusion for the repo folder (recommended for a personal dev box). Run from an elevated PowerShell:

    Add-MpPreference -ExclusionPath "C:\path\to\cybersec-toolkit"
    
  2. Restore individual files from quarantine via Windows Security -> Virus & threat protection -> Protection history -> "Allow on device". Per-file, but does not prevent re-detection on update.

  3. Keep the repo inside the WSL filesystem (e.g. ~/cybersec-toolkit in your distro). Defender does not scan WSL2's vhdx by default, so detections do not occur. scripts/sync-wsl.sh already does this for the MCP server subdirectory.

Files removed by Defender will appear as D in git status. The content is preserved in git history; restore with git checkout -- <path> once an exclusion is in place.

License

MIT License -- see LICENSE for details.

For contribution workflow and review expectations, see CONTRIBUTING.md. For community behavior expectations, see CODE_OF_CONDUCT.md. For vulnerability reporting, see SECURITY.md.

Disclaimer

This project is provided for educational, defensive, and explicitly authorized security testing only. Use it only on systems you own or have written permission to assess, and follow all applicable laws, rules of engagement, third-party tool licenses, and service terms.

The toolkit includes dual-use offensive and defensive tools. Some commands can scan networks, execute exploits, modify systems, or trigger security alerts. MCP/AI integrations are guarded by safety policies, but users remain responsible for reviewing scope, prompts, commands, and outputs before running actions.

The project is provided "as is", without warranty. Maintainers are not responsible for misuse, damage, data loss, service disruption, or legal consequences from using this toolkit.

Ver o original no GitHub

Bom para

Relacionados