When you face an unfamiliar router, the hardest question is where to start. routersploit answers it with autopwn, a scanner module that probes the device and tells you which of the framework’s exploit modules look relevant to it. Instead of scrolling hundreds of module names and guessing, you run one scan and get a shortlist built for the hardware in front of you. This guide shows you how to run autopwn against a router in your own lab, how to read what it prints, and how to follow up on its suggestions the careful way.
What autopwn does
Autopwn is a scanner, and scanning is a discovery step. You load it with use scanners/autopwn, point it at a target, and run it. The module probes the device and checks it against the framework’s library of router exploit modules, then reports the ones that match or look promising for that target.
That report is a starting point, not a verdict. Autopwn does not prove a router is vulnerable; it tells you where a closer look is worthwhile. Each module it names still needs to be read, loaded, and confirmed individually, usually with its check command. Thinking of autopwn as a knowledgeable friend tapping a few modules on the shoulder, rather than an oracle, will keep your expectations exactly right.
Before you scan
Two minutes of preparation make the scan meaningful. First, your target should be a device you own or have permission to test, ideally a spare router on an isolated lab segment, the standard setup for learning this framework. Second, confirm the basics about it: its admin address, which is commonly 192.168.1.1, and the fact that you can open its admin page from your computer. If you cannot reach the admin page in a browser, the scanner cannot reach the device either, and fixing that simple connectivity comes first.
It also helps to know the router’s model and firmware version before you scan, which you can read off the label on the box or the admin page’s status screen. Autopwn’s suggestions become far easier to judge when you can compare them against the exact hardware and firmware sitting in front of you.
Load the scanner and set the target
At the rsf prompt, load the module:
use scanners/autopwn
Read it before running it, the way you should read every module. show info describes what the scanner does, and show options lists its settings. Like most modules, autopwn needs a target and works with a port setting for the device’s web interface, which defaults to the standard web port.
Set the target to your lab router’s address:
set target 192.168.1.1
If your router’s admin interface lives on a different port, set that too with set port followed by the number. A quick second look at show options confirms both values are in place before anything runs.
Run the scan
Start it with run, then let it work. Autopwn works through its checks against your device, printing progress as it goes. A scan is not instant; the module has a lot of candidates to consider, and a slower, older router answers requests at its own pace. Resist the urge to interrupt it. A partial scan gives you a partial shortlist and no way to know what you missed.
While it runs, you will see the names of exploit modules appear as the scanner finds candidates worth reporting. By the time the prompt returns, you have your result: a list of modules the scanner considers relevant to this specific router.
Read the results properly
Now slow down, because this is where the value is. For each module the scan names, ask three questions. Does the module’s vendor match your router’s maker? Does it name your model, or at least your model family? Does it mention firmware near the version your router runs? A module that lines up on all three deserves a full investigation. One that matches only on vendor is a weaker hint, worth a read but not a conclusion.
An empty result deserves respect too. If autopwn reports nothing promising, the likely meanings are that your router is reasonably current, that its firmware is patched against what the library knows, or that the framework simply has no modules for your model. All three are plausible, and none of them is a failure of your session. A quiet scan of an up-to-date router is the outcome good maintenance produces.
Follow up the careful way
For a promising module, the follow-up has a fixed order. Load it with use and its full path. Read show info closely, and note the exact devices and firmware the author wrote it for. Set your target again inside this module, since options do not carry across modules. Then, where the module supports it, run check:
check
The check tests whether your target looks vulnerable without running the full exploit, which is the proportionate way to confirm a scanner’s suggestion on your own hardware. What you do with a confirmed result is a judgment call covered by the defensive guide below: on a lab box, it is a lesson; on your real router, it is a prompt to update firmware or retire the device.
Know the scanner’s limits
Autopwn can only match your router against modules the framework actually has. A brand-new model, an obscure brand, or a very recent vulnerability may have no module yet, so a clean scan never guarantees a secure device. It also leans on the device answering its probes in recognizable ways, so unusual configurations can hide a router from it or make it look like a different model. Treat the scan as strong evidence, gathered quickly, inside a wider habit of keeping firmware updated and defaults changed.
Keep notes from every scan
A scan you do not write down is a scan you will end up repeating. Keep a short note for each run: the router’s model and firmware version, the date, the modules autopwn suggested, and what check said about each one. Three or four lines per session is plenty, and the habit pays for itself the first time you update the router’s firmware and want to compare the new scan against the old one.
Notes also protect you from a subtle trap: trusting your memory of a shortlist. Module names are long, similar to each other, and easy to mix up a week later. The written list from the day, checked against the router in front of you, is the version worth acting on. Security testers treat this record-keeping as part of the work itself, and on your own network it doubles as a history of how your router’s posture changed over time.
Conclusion
Autopwn earns its place as the usual first move in routersploit: load it with use scanners/autopwn, set your own router as the target, run it, and read the shortlist of exploit modules it considers relevant. Judge each suggestion against your router’s model and firmware, then follow up individually with show info and check before drawing any conclusions. Paired with a lab setup and a little patience, one scan turns an unfamiliar router from a mystery into a clear, short list of things worth checking.
Read next: