Repository navigation
[!] Error Exit code = 127 When Running rustscan (Even Without Nmap Flags) #862
Description
Hi all!
I'm encountering a consistent issue when using rustscan to scan servers. Every scan results in an error code 127, regardless of the command used.
For example:
When running a basic scan:
rustscan -a 10.129.6.185 -- -sV -sC
→ Error code 127 appears.
Even when explicitly avoiding Nmap-related features:
rustscan -a 10.129.6.185 --ulimit 5000
→ The same error code 127 is displayed.
I researched the error online, and many sources indicate that exit code 127 typically means "command not found" (often because nmap is missing from the system's PATH or not installed at all). However, this doesn't explain why the error occurs even on commands that shouldn't depend on Nmap.
Could you please advise on the following?
My desktop environment is Windows Subsystem for Linux, the rustscan is the newest version.
Thank you in advance for your assistance—I really appreciate your help in resolving this.
Activity
PsypherPunk commentedon Feb 10, 2026
Hi, @jiajy0427. By default RustScan will always pass its results through to Nmap.
If you want it not to do that, add
--scripts noneto the end of your command. i.e.rustscan -a 10.129.6.185 --ulimit 5000 --scripts noneusing your example.bee-san commentedon Oct 2, 2026
RustScan runs Nmap by default, including when no arguments follow
--. To scan without running Nmap, userustscan -a <target> --ulimit 5000 --scripts none. Otherwise, install Nmap and make sure it is available in the same WSL environment's PATH.Closing as answered. Improving the diagnostic for a missing Nmap binary remains tracked in #691.