Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Chisel is a TCP and UDP tunnel carried over HTTP and secured with SSH, used to pivot through networks by wrapping arbitrary traffic in connections that firewalls already permit.

What Is Chisel?
Chisel is a tunnelling tool: a single Go binary that runs as a client on one host and a server on another, carries TCP and UDP traffic inside an HTTP or WebSocket connection, and secures that traffic with the SSH protocol. It is widely used in penetration testing because it solves the pivoting problem with almost no friction, and it is used by intrusion sets for exactly the same reason.
The problem it solves is this. A tester or an attacker has code execution on one internal host. The networks they want to reach are not routable from where they are sitting, outbound connections are filtered, and nothing listens for inbound traffic. What almost always still works is an outbound HTTP connection through the corporate proxy, because that is how the organisation’s own software updates and telemetry leave. Chisel turns that one permitted channel into a general-purpose route.
Chisel’s most used arrangement is a reverse SOCKS proxy. A server listens on infrastructure the tester controls. The client runs on the compromised internal host and dials out to it. Once connected, the tunnel is reversed: a SOCKS5 proxy opens on the tester’s own machine, and traffic sent to it emerges from the internal host. From that point, any SOCKS-aware tool can reach internal addresses as though it were sitting on the internal segment.
Three properties make it convenient:
Chisel is one instrument in a category, and defenders should think about the category rather than the binary name:
-L, -R, and -D does the same work with a client that is already installed on every Linux host and most Windows ones.In MITRE ATT&CK terms this is T1572 Protocol Tunnelling, usually alongside T1090 Proxy and T1572’s close relative T1071 Application Layer Protocol. It enables lateral movement, supports command and control, and provides the channel for data exfiltration.
Signature matching on the binary is the weakest control available, since recompiling a Go program with a different name takes seconds. Behaviour is where the detections live.
Egress filtering remains the control that does most of the work. Permit outbound traffic only through an authenticated proxy, allowlist destination categories for servers, and block direct outbound connections from server segments entirely. Apply network segmentation so that a pivot from a compromised workstation reaches a small area rather than the whole estate. Use application allowlisting on servers so that an unsigned binary cannot execute at all. Finally, decide a policy position on sanctioned tunnelling services and enforce it, because an unmanaged ngrok or Cloudflare Tunnel account is an unmonitored route into your network that no reputation feed will ever flag.
At Privia Security, our Red Team Services test these egress and segmentation assumptions directly, and document which pivot attempts were detected and which were not.
Because it uses a channel the organisation has already decided to permit. Blocking outbound HTTP and WebSocket traffic outright is not an option for most estates, and the tunnel’s payload is encrypted inside it. The practical controls are therefore forcing all egress through an authenticated proxy, allowlisting destinations for servers, and alerting on connection patterns rather than content.
No. It is a legitimate open-source networking utility with ordinary administrative uses, and it is published openly. Intrusion sets and ransomware affiliates use it because it is small, portable, and effective, which is also why testers use it. Detection should focus on whether a tunnel to an unapproved destination exists at all, not on the name of the executable that created it.
Flow analysis. Long-lived sessions to a single external destination with steady bidirectional volume, connections to IP addresses with no preceding DNS lookup, TLS fingerprints matching no known application, and unsigned binaries in user-writable directories holding sustained network connections. Internally, a host suddenly contacting many new destinations and ports is often a clearer signal than the external leg.
Take an explicit policy position rather than leaving it undecided. These are legitimate services with valid certificates and high domain reputation, which is exactly why attackers use them for persistent access. Either sanction specific accounts and monitor them, or block the domains and the client binaries outright. The dangerous state is unmanaged use that no reputation-based control will flag.
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.