Which tools route through Tor
Only tools that speak SOCKS natively are sent through Tor. These are the Go scanners and curl:httpx -proxy socks5://127.0.0.1:9050) or sets the standard proxy environment variables. No command injection, no wrappers.
Why payload tools stay direct
Injection and payload tools (sqlmap, ghauri, commix, sstimap, lfimap, nosqli and friends) are built on Python’srequests, which needs an extra package for SOCKS and otherwise throws an error on every request, flooding and hanging the run. Tor is also impractically slow for payload work and its exits are frequently blocked. So these tools stay direct, but they are still paced by the same adaptive model. You get evasion where it helps and reliability where Tor would hurt.
D0pam1ne uses each tool’s native SOCKS support, not proxychains. proxychains injects a library at load time, which crashes some tools on Apple Silicon, so it is deliberately avoided.
Exit-IP rotation
When a tool is routed through Tor, D0pam1ne asks Tor for a fresh circuit (aNEWNYM signal on the control port), so the next tool goes out through a different exit IP. Tor rate-limits circuit changes internally, so this is safe to request often. If the control port is not available, the lane keeps a fixed exit rather than failing.
Setting it up
Install the Tor and proxychains tools from the Tools page (category Attack · Evasion (Tor)). D0pam1ne lays down a dedicated Tor config with SOCKS on9050 and a control port on 9051, and a launcher so the control port accepts the rotation signal.
Under the hood
Two environment variables tie recon and Pro together:
Recon never sets a global proxy, because that would break the Python tools; it routes only the Go HTTP tools through Tor and keeps the rest direct.
