rofl0r / proxychains-ng

proxychains ng (new generation) - a preloader which hooks calls to sockets in dynamically linked programs and redirects it through one or more socks/http proxies. continuation of the unmaintained proxychains project. the sf.net page is currently not updated, use releases from github release page instead.
http://sourceforge.net/projects/proxychains-ng/files
GNU General Public License v2.0
9.82k stars 1.08k forks source link

proxychains+nmap/telnet shows that all ports open #91

Open ghost opened 9 years ago

ghost commented 9 years ago

When I use nmap or telnet with procxychains4, it seems that all ports open,just like this:

proxychains4 -q nmap -n 202...* | head Starting Nmap 6.40 ( http://nmap.org ) at 2015-10-16 22:26 CST Nmap scan report for 202...* Host is up (0.00034s latency). PORT STATE SERVICE 1/tcp open tcpmux 3/tcp open compressnet 4/tcp open unknown 6/tcp open unknown 7/tcp open echo

proxychains4 -q telnet 202...* 7777 Trying 202...... Connected to 202.... Escape character is '^]'.

Why do such things happen?

rofl0r commented 9 years ago

can you check if the older releases of proxychains-ng ( https://github.com/rofl0r/proxychains-ng/releases ) also exhibit this behaviour ?

ghost commented 9 years ago

I used 4.9 and 4.8.1 to test it.It seems that it still has that problem. :(

thinkycx commented 6 years ago

I have the same problem. When use proxychains4 curl www.google.com, it works well. However, when use proxychains4 nmap -Pn -sT 61.135.169.121 , all ports are open. Is there anyone fix this problem?

log

Starting Nmap 7.01 ( https://nmap.org ) at 2018-05-01 22:26 CST
Nmap scan report for 61.135.169.121  (224.0.0.1)
Host is up (0.0043s latency).
rDNS record for 224.0.0.1: all-systems.mcast.net
PORT      STATE SERVICE
1/tcp     open  tcpmux
3/tcp     open  compressnet
4/tcp     open  unknown
6/tcp     open  unknown
7/tcp     open  echo
9/tcp     open  discard
13/tcp    open  daytime
17/tcp    open  qotd
19/tcp    open  chargen
20/tcp    open  ftp-data
21/tcp    open  ftp
22/tcp    open  ssh
23/tcp    open  telnet
24/tcp    open  priv-mail
MasonQAQ commented 5 years ago

I have the same problem. When use proxychains4 curl www.google.com, it works well. However, when use proxychains4 nmap -Pn -sT 61.135.169.121 , all ports are open. Is there anyone fix this problem?

log

Starting Nmap 7.01 ( https://nmap.org ) at 2018-05-01 22:26 CST
Nmap scan report for 61.135.169.121  (224.0.0.1)
Host is up (0.0043s latency).
rDNS record for 224.0.0.1: all-systems.mcast.net
PORT      STATE SERVICE
1/tcp     open  tcpmux
3/tcp     open  compressnet
4/tcp     open  unknown
6/tcp     open  unknown
7/tcp     open  echo
9/tcp     open  discard
13/tcp    open  daytime
17/tcp    open  qotd
19/tcp    open  chargen
20/tcp    open  ftp-data
21/tcp    open  ftp
22/tcp    open  ssh
23/tcp    open  telnet
24/tcp    open  priv-mail

Hello, do you solve the problem, I hava the same problem, all ports open!

rofl0r commented 5 years ago

https://github.com/rofl0r/proxychains-ng/issues?utf8=%E2%9C%93&q=is%3Aissue+nmap