Docs / Run scans

Nodes and egress

A node is one of your machines, enrolled to run scans. This page covers enrolling one, the address its scans leave from, proxies, and the engines and wordlists it uses.

Nodes

A node is one of your hosts, enrolled to run scans. Every account starts with one, default-node-1, and you can add more in the dashboard under Arsenal, then Nodes, then Deploy. To enrol a host, run sudo crossfyre node init on it. Signed in with crossfyre login, it takes the oldest node on your account that has not come online and that no other machine has claimed, and gives it a new key, so a key the dashboard showed for that node stops working. A node you add waits behind any older one that has not come online. Without a session, node init asks for a node key instead: the dashboard shows one when you create a node, and again when you rotate a node's key. Enrolment installs the node's engines, provisions the local database, and installs an OS service so the node survives reboots.

The node service runs a supervisor that keeps every registered node online; each reports a heartbeat so the dashboard shows it online or offline. Bring them up or down with crossfyre node up / crossfyre node down, check local daemons with crossfyre node status, or the whole fleet with crossfyre node list.

Egress: a scan leaves from the node host's own address, or through the proxy the node is set to use. VPN and Tor tunnels can be saved but do not carry scan traffic yet.

Proxies & egress

A node can send its scans and Bench requests through one proxy: HTTP, HTTPS, SOCKS4 or SOCKS5, from your Proxies page. Point every node at one proxy with a fixed exit, and that exit is the one address your client allow-lists. If the proxy is down, the node's scans fail rather than going out directly. Without a proxy, a node sends from its host's own address.

On a proxied node, port scans and origin discovery do not run, the crawler's headless browser tier is skipped, and DNS lookups for subdomain discovery go to public resolvers from the node itself.

Manage proxies from the Proxies page: add them individually or in bulk, tag them, test connectivity on demand, and schedule recurring health checks. Each check fetches crossfyre.io through the proxy from our Frankfurt server and reports the exit address; a test you run from a node fetches it from that node instead. Proxy credentials are encrypted at rest.

Whose address the target sees. Every probe that touches your target leaves from one of your own machines, or from the proxy you chose for it. No scan traffic is sent from Crossfyre's servers.

Bring your own egress. Add a residential or mobile provider's gateway on the Proxies page and pick it on a node; that node's scans then leave through the provider. The Workbench sends from the machine it runs on.

VPN tunnels do not carry scan traffic yet. Enrol a host or pick a proxy whose address your client expects, and use these settings only for engagements you are contracted to run, not to avoid attribution.

Extensions

Engines are installed on a node as extensions. crossfyre extension install voyage from the terminal, or subscribe from the marketplace in the dashboard under Arsenal and the node picks it up.

The marketplace lists what is available and what a node already has. Today that is the five core engines, and anything added later installs the same way.

Wordlists

Crossfyre ships default wordlists and lets you upload your own, scoped to your team. Engines (ambulo, voyage) pull from them during active discovery. Manage them from the Wordlists page.