-
Notifications
You must be signed in to change notification settings - Fork 0
Modules
Melvin PETIT edited this page Jun 17, 2026
·
1 revision
Kraken's functionality lives in independent tentacle modules under
lib/modules/. Each one is selected from the Usage,
prompts for a target, validates it, runs its steps and writes results
into the current session.
| Key | Module | Page | Primary tools |
|---|---|---|---|
| 1 | Reconnaissance | Reconnaissance |
dig / host, subfinder, whois
|
| 2 | Port scanning | Port Scanning |
nmap, /dev/tcp
|
| 3 | Web enumeration | Web Enumeration | curl |
| 4 | Vulnerability assessment | Vulnerability Assessment |
openssl, curl
|
| 5 | Reporting | Reporting | none (aggregates files) |
Every module:
- exposes a single entry point
kraken_<name>_run, - writes into
${KRAKEN_OUTPUT_DIR}/<name>_<target>/, - validates input with
kraken_valid_target, - degrades gracefully when an external tool is missing.
See Architecture for the full module contract and Extending Kraken to add your own.
Modules never hard-fail on a missing tool. For example, the recon
module prefers dig, falls back to host, then nslookup, then
getent. The scan module uses nmap when present and a pure-Bash
/dev/tcp probe otherwise. Install only what you need.
Kraken Pentest Framework · MIT License · Maintained by Melvin PETIT · For authorized security testing only.
Getting started
Reference
Modules
Development
More