Four interfaces, one library
Interactive shell, CLI runner, encrypted REST/WebSocket API and an MCP server — the same 468 modules behind each.
← Store · // rustsploit
Modular offensive tooling for embedded and network targets, written in Rust and inspired by RouterSploit and Metasploit. One binary exposes the same module library through four interfaces, with built-in service and TLS fingerprinting.
// what it is
Rustsploit began as a Rust rewrite of RouterSploit and has grown into a broad offensive framework for routers, cameras, appliances and general network services. A single binary carries an ever-growing library of exploit, scanner and credential modules that register themselves natively.
The same module library is driven through four interfaces: an interactive shell, a one-shot command-line runner, a post-quantum-encrypted REST/WebSocket API, and a Model Context Protocol server — so it fits a manual session, a script, a service, or an AI-driven workflow equally well.
Service identification is built in: Recog fingerprinting names what is listening, and JARM/JA3 TLS fingerprinting characterises encrypted services before you ever send a module at them.
// capabilities
Interactive shell, CLI runner, encrypted REST/WebSocket API and an MCP server — the same 468 modules behind each.
Exploits, scanners and credential modules register themselves natively, so the library grows without wiring.
Identifies services and devices from their banners before you choose a module.
Characterises encrypted services to tell appliances apart and spot what a port really runs.
The REST/WebSocket control channel is encrypted with post-quantum primitives.
Routers, cameras, appliances and network services — the devices other frameworks treat as an afterthought.
// under the hood
// what you pay for
Rustsploit’s source is public. What you pay for is the engineer who built it.
// the fine print
Authorized, lawful use only. Offensive-security software published for legitimate testing, research and education. You alone are responsible for how you use it and must hold explicit written authorization for any system you target.
No liability. Provided as-is and without warranty; to the maximum extent permitted by law, Cyber Sec and Stephan Botes accept no liability for misuse.
What the fee buys. The engineer’s time — setup, fixes and customisation. The source is public, so you pay for the work, not for access.
Questions about scope, licensing or authorization? Get in touch first.