Terminal-first recon, scanning, AI-assisted workflows, and operator tooling in one open source project.
Changelog • Install • Quick Start • Commands • Docs
Zypheron CLI is an AI-native security CLI built around practical terminal workflows rather than disconnected scripts and raw output dumps.
It combines:
- A Go-based CLI and TUI
- AI model integration across local and hosted providers
- Toolchain-aware workflows for recon, scanning, and operator tasks
- Local session, loot, and artifact storage under
~/.zypheron - Bootstrap and release installers for both source-based and packaged installs
This repository is the open source CLI. It is intended for authorized security testing, research, and operator workflow automation.
Zypheron is free and open source. This repository should be treated as a local-first security CLI and self-hostable tooling project.
The production release candidate targets the local/self-hosted OSS path: Go CLI, Python AI runtime, optional FastAPI service, local tool orchestration, and packaged CLI artifacts. Hosted SaaS-only surfaces are not launch blockers for this RC.
Deferred for the OSS RC:
- Enterprise Teams API endpoints may return
501 Not Implemented - streaming chat protocol support; chat currently uses the non-streaming path
- full autonomous exploitation; autopent remains approval-gated and safety-first
- hosted billing/dashboard production polish
Package-manager artifacts are generated on tagged releases, but public apt, Homebrew, AUR, and DNF repository publishing requires the matching external repos/taps to be configured. Until those are live, use the source bootstrap or release binary installer.
Install paths — pick one.
Full repo, local development workflow, automated dependency setup.
git clone https://github.com/KKingZero/Zypheron-CLI.git
cd Zypheron-CLI
bash scripts/install/setup-hybrid.shsetup-hybrid.sh builds the Go CLI into ~/.local/bin/zypheron, runs zypheron install-deps for Python dependencies, and installs bash/zsh completion.
Common overrides:
# Custom install dir
ZYPHERON_INSTALL_DIR="$HOME/.local/bin" bash scripts/install/setup-hybrid.sh
# Skip external tool install (manage them yourself)
ZYPHERON_INSTALL_TOOLS=none bash scripts/install/setup-hybrid.sh
# Install every supported external tool
ZYPHERON_INSTALL_TOOLS=all bash scripts/install/setup-hybrid.shUse these if the bootstrap fails with missing Go checksums, a missing zypheron
command, or Python dependency errors.
# From the repo root
cd Zypheron-CLI
# Generate missing Go checksums
cd zypheron-go
go mod tidy
# Build and install the CLI locally
mkdir -p "$HOME/.local/bin"
go build -o "$HOME/.local/bin/zypheron" ./cmd/zypheron
export PATH="$HOME/.local/bin:$PATH"
# Confirm the CLI is installed
zypheron --version
zypheron --help
# Install Python AI engine dependencies
cd ..
zypheron install-deps
# Optional large dependency packs
zypheron install-deps --security --web --mcp
zypheron install-deps --all
# Check the full install
zypheron doctorIf zypheron is still not found, add this to your shell profile:
export PATH="$HOME/.local/bin:$PATH"Packaged CLI without cloning the repo.
curl -sSfL https://download.zypheron.net/install.sh | bashOverrides:
ZYPHERON_VERSION=v2.0.0 curl -sSfL https://download.zypheron.net/install.sh | bash
ZYPHERON_INSTALL_DIR="$HOME/.local/bin" curl -sSfL https://download.zypheron.net/install.sh | bashThe release installer detects OS/arch, downloads the matching archive + SHA256SUMS, verifies the checksum, and installs the zypheron binary.
Tagged releases build .deb and .rpm artifacts. Homebrew and AUR use
source-build templates under packaging/ so SQLite-backed features
are built with CGO enabled on the user's system.
Direct package artifact installs:
# Debian / Ubuntu / Kali / Parrot
curl -LO https://download.zypheron.net/v2.0.0/zypheron_2.0.0_amd64.deb
sudo apt install ./zypheron_2.0.0_amd64.deb
# Fedora / RHEL-family
curl -LO https://download.zypheron.net/v2.0.0/zypheron-2.0.0-1.x86_64.rpm
sudo dnf install ./zypheron-2.0.0-1.x86_64.rpmOnce the package repositories are published, the intended commands are:
sudo apt install zypheron
brew install KKingZero/zypheron/zypheron
yay -S zypheron
sudo dnf install zypheronSee docs/INSTALL.md for the publication checklist.
Standalone installers for external tools (hydra, nuclei, amass, metasploit, ropper, volatility3, one_gadget, ghidra, SecLists, rockyou). Use these when you already have the Zypheron CLI installed and just need the tool ecosystem.
# Debian / Ubuntu / Kali / Parrot / Mint / Pop!_OS / elementary
sudo bash scripts/install/install-tools.sh
# Arch / Manjaro / EndeavourOS / Garuda / BlackArch
sudo bash scripts/install/install-tools-arch.sh
# Fedora / RHEL 8+ / CentOS Stream / Rocky / Alma / Oracle Linux / Amazon Linux 2023
sudo bash scripts/install/install-tools-rpm.shAll three installers share the same env-flag surface:
| Flag | Effect |
|---|---|
ZYPHERON_MIN_FREE_MB=<mb> |
Override disk preflight (default 3072 = 3 GB) |
ZYPHERON_ALLOW_REMOTE_INSTALLERS=1 |
Enable Metasploit omnibus fallback (pinned commit + SHA256) |
ZYPHERON_BUILD_GO=1 |
Also build zypheron-go from source when present |
ZYPHERON_GO_DL_VERSION=1.24.2 |
Go tarball version to pull from go.dev when apt/pacman/dnf is too old |
ZYPHERON_INSTALL_LOG=<path> |
Log destination (default /var/log/zypheron-install.log) |
Arch-only flags:
| Flag | Effect |
|---|---|
ZYPHERON_ENABLE_BLACKARCH=1 |
Enable BlackArch pacman repo (SHA256-pinned strap.sh) |
ZYPHERON_AUR_HELPER=paru|yay |
Preferred AUR helper (default: paru, falls back to yay, bootstraps paru-bin if neither present) |
ZYPHERON_ALLOW_AUR_SKIPREVIEW=1 |
Skip interactive PKGBUILD review (off by default, not recommended) |
Interactive installer, never auto-runs from the main installers.
sudo bash scripts/install/install-c2.sh- Sliver installs from Kali/Parrot apt when available, otherwise from a pinned GitHub release tarball verified against an embedded SHA256. Set
ZYPHERON_ALLOW_UNVERIFIED_SLIVER=1to fall through to the upstreamcurl | bashinstaller (not recommended). - Empire installs from
powershell-empireapt pkg on Kali/Parrot; otherwise clonesBC-SECURITY/Empireinto/opt/Empire(override withZYPHERON_EMPIRE_DIR) and runs./setup/install.shafter consent. - Havoc is intentionally excluded — install manually from the upstream project.
After install, Empire usage via zypheron exploit --c2 empire expects:
export EMPIRE_HOST=https://127.0.0.1:1337
export EMPIRE_USER=<username>
export EMPIRE_PASS=<password>
# Optional, loopback/RFC1918 only:
export EMPIRE_INSECURE_TLS=1Shortest end-to-end path for a new box:
# 1. Clone + bootstrap
git clone https://github.com/KKingZero/Zypheron-CLI.git
cd Zypheron-CLI
bash scripts/install/setup-hybrid.sh
# 2. Install the external pentest tool ecosystem (pick one)
sudo bash scripts/install/install-tools.sh # Debian / Ubuntu / Kali / Parrot / Mint
sudo bash scripts/install/install-tools-arch.sh # Arch / Manjaro / BlackArch
sudo bash scripts/install/install-tools-rpm.sh # Fedora / RHEL / Rocky / Alma
# 3. Verify
zypheron doctor
zypheron tools check
# 4. Launch
zypheronOptional follow-ups:
# C2 frameworks (Sliver, Empire) — interactive, opt-in per framework
sudo bash scripts/install/install-c2.sh
# Install Python-side AI/ML dependencies
zypheron install-deps --all
# Check CLI version
zypheron --versionFor a clean release-candidate gate from source:
./scripts/setup_api_test_env.sh --allow-online
./scripts/setup_ai_test_env.sh --allow-online
./scripts/run_all_tests.sh --ci
./scripts/local_smoke_test.sh --setup-api-env --allow-onlinerun_all_tests.sh --ci runs the API tests, AI runtime tests, Go tests with a
workspace GOTMPDIR, and integration checks.
Zypheron CLI is built for operator workflow acceleration, not just command wrapping.
Current project capabilities include:
- AI-assisted terminal workflows
- Interactive TUI with model selection and persisted provider/model settings
- Recon, scanning, and structured terminal output flows
- Workflow execution and session storage
- Dorking and AI-guided query enhancement
- Active Directory, cloud, and broader offensive workflow modules in the CLI
- Integration points for common security tools and local model runtimes
- Updater support for packaged releases
The project is terminal-first. Some workflows depend on external tools being installed locally.
# TUI
zypheron
zypheron tui
# Health checks
zypheron doctor
zypheron install-deps --all
# Scan and recon
zypheron scan example.com
zypheron scan example.com --web
zypheron recon example.com
# AI-assisted dorking
zypheron dork "exposed login portals"
zypheron dork "admin panels" --ai-guided
# AI chat
zypheron chat "How would you approach this target?"
# Workflows and sessions
zypheron workflow list
ZYPHERON_ENABLE_AUTOPENT=1 zypheron autopent example.com
# Tooling and environment
zypheron tools check
zypheron tools install-all --critical-only --yes
# Updates
zypheron update checkRun zypheron --help or zypheron <command> --help for the current command surface in your build.
Zypheron supports local and hosted model providers. In the TUI, selecting a hosted model without a configured API key now prompts for the key and stores it for reuse.
Typical provider setup paths:
- Local models through Ollama
- Hosted models through provider API keys in Zypheron config/key storage
If you want to verify your environment after setup:
zypheron doctor
zypheronMany workflows call external tools. Either let setup-hybrid.sh install the critical set:
ZYPHERON_INSTALL_TOOLS=critical bash scripts/install/setup-hybrid.shOr skip that step and run the dedicated per-distro installer afterwards (bigger tool set, hardened with pinned versions + SHA256-verified remote installers):
ZYPHERON_INSTALL_TOOLS=none bash scripts/install/setup-hybrid.sh
# Then one of:
sudo bash scripts/install/install-tools.sh # Debian / Ubuntu / Kali / Parrot
sudo bash scripts/install/install-tools-arch.sh # Arch family
sudo bash scripts/install/install-tools-rpm.sh # RedHat / Fedora family
zypheron tools checkSliver and Empire are not installed by the main installer. Opt in with:
sudo bash scripts/install/install-c2.shUse guided mode to review operator-controlled C2 setup steps. With no other action it prints guidance only; with an explicit action such as --listener, it prints the checklist first and then attempts only that requested action.
zypheron exploit --c2 sliver --guided
zypheron exploit --c2 empire --guided --listener httpSee the Install section for details on verification and env flags.
Minimum local requirements:
- Go
1.24+for source bootstrap and local builds - Python
3.9+ - Linux, macOS, or WSL
Kali or a similarly equipped Linux environment is recommended for heavier offensive workflows.
| Guide | Description |
|---|---|
| docs/QUICKSTART.md | Fast install and first run |
| docs/INSTALL.md | Installation and environment setup |
| docs/SETUP_AND_USE.md | Practical setup and usage |
| docs/CLI_REFERENCE.md | CLI command reference |
| docs/AI_GUIDE.md | AI providers, keys, and model behavior |
| docs/MCP_INTEGRATION.md | MCP and integration details |
| docs/TOOL_CHAINS.md | Toolchain workflows |
| docs/BUILD_AND_TEST.md | Local build and validation |
| docs/HELP.md | Troubleshooting |
- CODE_OF_CONDUCT.md
- .github/ISSUE_TEMPLATE/bug_report.md
- .github/ISSUE_TEMPLATE/feature_request.md
- .github/PULL_REQUEST_TEMPLATE.md
For authorized security testing only. Always obtain written permission before scanning, exploiting, or interacting with systems you do not own.
MIT License. See LICENSE.