Five engines for recon and vulnerability scanning, written in Rust, that you run from the terminal on systems you are authorized to test. Each one works on its own, with no account, and nothing leaves your machine unless you connect it to the Crossfyre platform yourself.
| Engine | What it does |
|---|---|
voyage |
Finds subdomains, from passive sources and wordlist brute-forcing. |
doorward |
Scans hosts and ports, with service detection. |
ambulo |
Fuzzes paths and parameters to discover content. |
toolmark |
Fingerprints services and technologies, and flags CVE leads by version. |
plessor |
Tests for vulnerabilities with nuclei-compatible templates and an injection engine, and confirms each finding before it reports it. |
Alongside them: crossfyre, the CLI that installs and updates everything, node, the agent that runs the engines for the platform, oast, an out-of-band server you can host so plessor confirms blind bugs on your own domain, and mobile, Crossfyre Mobile for Android, which is on Google Play.
This repository began as voyage, the standalone subdomain finder, and its history is kept on that branch. ambulo began as mach.
On Linux (x86_64 or aarch64) or macOS (Intel or Apple silicon):
curl -fsSL https://get.crossfyre.io/install.sh | sudo bashOn Windows, in PowerShell run as administrator:
irm https://get.crossfyre.io/install.ps1 | iexOr from the apt repository, on Debian, Ubuntu or Kali
curl -fsSLO https://bins.crossfyre.io/apt/crossfyre-archive-keyring.gpg
echo "5dd16a4067070a7763afe58deb829c5129618af9ac3bc096637345b6f43cc020 crossfyre-archive-keyring.gpg" | sha256sum -c - && sudo tee /usr/share/keyrings/crossfyre-archive-keyring.gpg < crossfyre-archive-keyring.gpg > /dev/null
sudo tee /etc/apt/sources.list.d/crossfyre.sources > /dev/null <<'EOF'
Types: deb
URIs: https://bins.crossfyre.io/apt
Suites: stable
Components: main
Signed-By: /usr/share/keyrings/crossfyre-archive-keyring.gpg
EOF
sudo apt update
sudo apt install crossfyre crossfyre-archive-keyringThe keyring is installed only if its SHA-256 matches. Its key's fingerprint is 992F106C6CF032E43A3CA8BED5D92DAC3BA8CDBF. After that, sudo apt upgrade keeps the CLI current.
Or the CLI on its own, from Homebrew or Scoop
brew install clickswave/tap/crossfyrescoop bucket add clickswave https://github.com/clickswave/scoop-bucket
scoop install clickswave/crossfyreThese install the crossfyre CLI for your own user, and the package manager keeps it current. The engines and the node service go into a system directory, so for those use the installer above.
crossfyre update all updates the engines. crossfyre.io/docs/install covers the .deb, signature checks and removal.
When the CLI fetches from bins.crossfyre.io, the request's User-Agent carries its name, version and platform and whether it is an install, an update or a check of the release manifest, and nothing else.
# Subdomains of a domain
voyage scan --domain example.com --wordlist-path /usr/share/seclists/Discovery/DNS/subdomains-top1million-5000.txt
# Ports and services across a range
doorward scan --targets 10.0.0.0/24 --ports top-1000 --service-detection
# Content discovery, fuzzing the path at ::FUZZ::
ambulo scan --url https://example.com/::FUZZ:: --wordlist-path /usr/share/seclists/Discovery/Web-Content/common.txtWordlists are read only from a few directories, since the daemon would otherwise read any file a request names: /usr/share/wordlists and /usr/share/seclists on Linux, and Homebrew's seclists on macOS. The temp directory is read only for the lists the node hands over. Add your own directories with CFX_WORDLIST_ROOTS, separated like PATH.
In a terminal voyage, doorward and ambulo draw a live dashboard. toolmark and plessor finish a single target in seconds, so they print JSON unless you put --tui before scan, as in toolmark --tui scan https://example.com. Piped or redirected, every engine writes newline-delimited JSON, one event per line, and exits non-zero if the run ends in an error. voyage, doorward and ambulo save findings as they go, so a stopped scan resumes where it left off. Add --help to any command for the rest.
From 0.1.38, crossfyre completions <shell> prints a completion script for bash, zsh, fish, powershell or elvish: crossfyre completions bash > ~/.local/share/bash-completion/completions/crossfyre. Each engine takes the same command, as in voyage completions zsh.
From 0.1.38, crossfyre mcp serves toolmark and plessor to an MCP client over stdio, so an agent can fingerprint a service, test endpoints for injection and replay single requests, and refuses any destination that a scope file you write does not list. See crossfyre/MCP.md.
Enrol the host as a node and the same engines run under the Crossfyre platform, with a fleet of nodes, scheduled scans, pacing tuned to each target, and one dashboard for your team:
crossfyre login
crossfyre node initThe platform is optional. Nothing here needs it.
With a stable Rust toolchain:
git clone https://github.com/clickswave/crossfyre-toolchain.git
cd crossfyre-toolchain
cargo build --releaseOr install one engine with cargo install --git https://github.com/clickswave/crossfyre-toolchain.git ambulo.
A source build sets up no services, so before the first scan start the Postgres container the engines keep their state in (this needs Docker), then the daemon of each engine you use:
crossfyre db up
ambulo --daemon &The container is published on 127.0.0.1 only, with a generated password kept in the toolchain's config.toml, which the engines read when they start.
cfx-script embeds Python, so building it needs one. On Linux that is your distribution's Python and its development files. On macOS it has to be Python 3.10 or later, and the python3 that comes with the Xcode command line tools is 3.9, so name another one: PYO3_PYTHON=/opt/homebrew/bin/python3 cargo build --release. Windows needs no Python to build it, and Python 3.10 or later to run scripts.
A source build, like the binaries on the Releases page, is the open build. The installer ships the first-party build, which adds the authorization checks, per-node egress isolation, tuned pacing and the browser-fingerprint transport.
Running an engine as a daemon on another address
Every engine can run as a daemon (--daemon) that its client talks to over loopback. The protocol is unauthenticated, so the bind address is the security boundary. CFX_DAEMON_BIND moves the listener to another IP, and CFX_DAEMON_TOKEN makes it require a token, which the clients and the node read from the same variable. If you move the listener, set the token: ambulo takes a wordlist path, so an open daemon can be made to read files.
What else is in this repository
| Crate | What it does |
|---|---|
core |
What crossfyre and node share: sign-in, installs and updates, the release manifest check, the node service and the Web Tracer. |
capture |
The Web Tracer's capture core, used by the desktop proxy and the Android app. |
cfx-script |
Runs .cfx scripts in an embedded Python interpreter. |
tui |
The terminal dashboard every engine draws. |
finding |
The one shape every engine reports a finding in. |
transport |
The engines' HTTP client. |
dguard |
The daemon listener policy. |
scope |
The destinations an operator may test, and the guard that refuses the rest. |
mcp |
The crossfyre mcp server: the engines as MCP tools, fenced by a scope file you write, with an audit line for every call. |
spec |
Reads OpenAPI, Swagger, Postman, HAR and Insomnia files. |
surface |
Describes a scanned attack surface and diffs it between runs. |
adaptive |
The engines' pacing and retry decisions, with an untuned baseline. |
relsign |
Signs the release manifest. Used to build releases, not shipped. |
Only scan systems you own or have written permission to test. Unauthorized scanning is illegal in most places and can disrupt the systems you point it at.
Issues and pull requests are welcome. Open pull requests against dev; main tracks the latest release. See CONTRIBUTING.md. To report a security issue, see SECURITY.md or email team@clickswave.org rather than opening a public issue.

