Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Proxychains forces an ordinary application’s TCP connections through one or more SOCKS or HTTP proxies, which is how testers run tools that have no proxy support of their own.

What Is Proxychains?
Proxychains solves a narrow problem neatly. Many command-line tools have no idea what a proxy is: they call the operating system, open a socket, and expect to reach the destination directly. Proxychains sits underneath them and redirects those connections through a chain of SOCKS or HTTP proxies, without the application knowing anything has changed.
It does this with LD_PRELOAD on Linux, loading a small library ahead of the standard C library and intercepting the connect() call. Prefix a command and its network traffic goes out through the proxy instead of the local interface. The actively maintained version is proxychains-ng, which is what ships in current security distributions.
The usual context is pivoting. A tester has access to one machine inside a network and opens a dynamic SOCKS proxy through it, commonly with an SSH client or a purpose-built tunnelling tool. That proxy can reach the internal network; the tester’s laptop cannot. Proxychains bridges the gap, so tools running on the laptop operate as though they were on the internal segment.
The same approach appears where traffic has to leave through a corporate proxy, or where an engagement requires requests to originate from a specific jurisdiction.
| Mode | Behaviour |
|---|---|
strict_chain | Uses every proxy in the list, in order; fails if any one is down |
dynamic_chain | Uses the listed proxies in order but skips any that are unreachable |
random_chain | Picks proxies at random for each connection |
round_robin_chain | Rotates through the list connection by connection |
Configuration lives in /etc/proxychains.conf or a file supplied on the command line, with the proxy list at the bottom and options such as proxy_dns and the connection timeout above it. In practice, dynamic_chain with a single SOCKS5 entry covers the majority of real use.
Proxychains handles TCP and nothing else. That one sentence explains most of the confusion around it:
proxy_dns routes name resolution through the proxy instead, which avoids leaking the hostnames you are querying to the local resolver.Performance is the other constraint. Every connection carries the round trip of the tunnel, so a scan that takes a minute directly can take an hour through a chain. Experienced testers narrow their target lists and port ranges before they start rather than discovering this halfway through.
Proxychains itself is invisible on the network: what defenders see is the pivot it depends on. The signals are therefore the same ones that reveal tunnelling in general. An internal host accepting connections and immediately opening many outbound sessions to other internal addresses is the clearest. So are long-lived encrypted sessions from a workstation to an external address, SSH from segments that have no reason to use it, and a single source producing connection attempts across many destination ports in sequence.
Host telemetry adds more. Execution of the proxychains or proxychains4 binary, unusual LD_PRELOAD environment variables on running processes, and new listening sockets on endpoints are all cheap to collect and rarely legitimate on a user device. Zeek connection logs make the internal fan-out pattern easy to query after the fact.
Default-deny egress through an inspecting proxy removes the simplest tunnel exits. Internal segmentation decides how much a pivot is worth once established, because a proxy is only as useful as the networks the pivot host can reach. Restricting who may run SSH clients and administrative tooling on standard workstations closes another common route, and application control on servers prevents an attacker from dropping a tunnelling binary in the first place.
If you want to know how far a single foothold travels in your environment, our Infrastructure Security Testing Services exercise exactly that path under controlled conditions.
Partly. Because it only intercepts standard TCP connections, raw packet scans such as SYN scanning bypass it completely and will either fail or leak directly. Scans must use TCP connect mode and disable host discovery, since ICMP is not proxied either. Even then, scanning through a tunnel is slow, so keep target lists and port ranges tight.
No. A VPN creates a virtual network interface and routes traffic at the network layer for the whole system, covering every protocol. Proxychains intercepts library calls for a single process and handles TCP only. That makes it lighter and easier to use through an existing SOCKS proxy, but it leaves ICMP, UDP, and raw sockets outside its reach.
It can. By default, name resolution may use the local resolver, which means the hostnames being looked up are visible on the originating network even though the connections themselves go through the proxy. Enabling the proxy_dns option sends resolution through the chain instead. Testers should verify behaviour with a packet capture rather than assuming it.
Look for the pivot rather than the tool. Workstations that accept inbound connections, hosts generating sequential connection attempts across many internal addresses and ports, long-lived encrypted sessions from user devices, and SSH activity in segments that never use it are all strong signals. Endpoint logs showing proxychains execution or unexpected LD_PRELOAD values confirm it.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.