CLI Usage
... or how you can use secator as your pentesting swiss-knife.
secator is first and foremost a command-line interface (CLI). This page describes how to use it in-depth.
Usage
secator --help # General help
secator x # List available tasks
secator w # List available workflows
secator s # List available scans
secator u # List available utilitiesRunning tasks
You can run any of the supported tasks out-of-the box using the secator x (execute) subcommand:
Find subdomains of a domain using offline sources with subfinder:
secator x subfinder wikipedia.orgFind information about an URL with httpx:
secator x httpx wikipedia.orgFuzz URLs with ffuf with max 100 requests / second and matching select HTTP codes:
secator x ffuf http://testphp.vulnweb.com/FUZZ -rl 100 -mc 200,201,300,500Find open ports and associated vulnerabilities with nmap using proxychains as a proxy:
secator x nmap myhost.com -p 443,80,8080,8081,21 -proxy proxychainsFind user accounts with maigret:
secator x maigret elonmuskRunning workflows
A workflow is a set of pre-defined tasks.
You can run some pre-written workflows using the secator w (workflow) subcommand:
To perform a basic host recon (open ports, network + HTTP vulnerabilities):
To perform a basic subdomain discovery (subdomain + root URLs):
To perform URL crawling:
To perform URL fuzzing:
To perform code vulnerability scan:
To find user accounts for a username:
Running scans
A scan is a set of workflows that run one after the other.
You can run some pre-written scans using the secator s subcommand:
Running utils
secator provides a number of utilities that can be useful when doing pentesting.
Proxy
You can get a random proxy:
Reverse shells
You can spawn reverse shells in any language, and optional netcat listener:
Serve
You can run an HTTP server to serve payloads:
Recording
You can record pentesting sessions as a GIF:
Configuring secator
To configure secator, use the following commands:
To see the full available configuration options, get the default configuration using secator c default.
Running a worker [optional]
You can enable enable distributed runs by starting secator workers. All tasks / workflows / scans will be sent to the workers for execution.
You can run a worker using the file system as a broker and result backend:
Last updated
Was this helpful?