Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Odin Research / What is / Tunnels and remote access

What Is Ligolo-ng? How the TUN Tunneling Tool Works

A pentester's pivoting tool that gives an operator a routed path into a private network through one outbound connection. What it does and how to catch it.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
5 min read
Type
Tunneling tool

In short

Ligolo-ng is an open-source tunneling tool that lets an operator reach an internal network through a reverse TCP or TLS connection. A proxy on the operator's machine creates a virtual TUN network interface, and a small agent on the target forwards the traffic. Penetration testers use it for pivoting, and intruders use it for lateral movement.

Key takeaways

What it is
A lightweight tunneling and pivoting tool published on GitHub (nicocha30/ligolo-ng) that uses a TUN interface instead of SOCKS.
How it works
An unprivileged agent on the target dials out to a proxy. The proxy routes packets from a virtual interface through that one encrypted connection.
Why it matters
It turns one foothold into network-level access to internal subnets, and its traffic looks like an ordinary outbound TLS session.
What Odin Research saw
347 recently active Ligolo-ng relays on 310 IPs in 42 countries. 37.2% used port 11601 and 27.1% used 443. None was confirmed hostile.
What to do first
Block outbound TCP 11601 to 11610, hunt non-browser TLS from user hosts, and correlate tunnels with risky sign-ins.

What is Ligolo-ng?

Ligolo-ng is an open-source tunneling tool that gives an operator access to an internal network through a reverse TCP or TLS connection. It uses a virtual TUN network interface rather than a SOCKS proxy, so ordinary tools can reach internal hosts directly. Penetration testers use it to pivot, and attackers use it the same way.

Its documentation calls it a lightweight, fast tool for pentesters. The project is published on GitHub as nicocha30/ligolo-ng.

Ligolo-ng solves a common problem in penetration testing. After gaining a foothold on one host, the tester wants to scan and reach the private network behind it. Older approaches wrap every tool in a SOCKS proxy. Ligolo-ng makes the remote network look like a local route instead.

That convenience is also why intruders like it. It turns a single foothold into broad network access for lateral movement.

How Ligolo-ng works

Ligolo-ng has two parts:

  1. The proxy (relay). It runs on the operator's side and must be able to create a TUN interface. Packets sent to that interface are translated and forwarded to the agent's network. Instead of SOCKS, it uses a userland network stack built on gVisor.
  2. The agent. It runs on the target and connects back to the proxy. It does not need administrative rights. Because it runs unprivileged, it opens normal sockets rather than raw packets. For example, a SYN scan becomes a full TCP connect from the agent.

According to its documentation, Ligolo-ng supports multiple tunnels, reverse and bind connections, listeners on the agent and automatic Let's Encrypt certificates. It carries TCP, UDP and ICMP echo requests. Its documentation reports throughput above 100 Mbit/s in a test.

Odin Research adds one more detail. On Windows, the TUN interface relies on wintun.dll. All traffic between agent and relay travels over a single TLS or WebSocket stream. MITRE ATT&CK calls this pattern Protocol Tunneling (T1572): wrapping traffic inside another protocol to avoid detection or reach otherwise unreachable systems.

How attackers use Ligolo-ng

In an intrusion, Ligolo-ng usually appears after initial access. A typical pattern looks like this:

  1. The attacker gains a foothold, for example through phishing, stolen sessions or an exposed service.
  2. They drop the small Go agent on that host. It dials out to a relay on a cloud server, often on port 443 so the traffic passes firewalls.
  3. The relay adds a route to the internal subnet. The attacker now runs scanners and admin tools as if they were on the internal network.

Odin Research's Monograph 06 places Ligolo-ng at the end of a chain that starts with adversary-in-the-middle phishing. Proxies such as Evilginx capture session cookies and get past MFA. A tunnel relay then carries the attacker into internal networks.

Is Ligolo-ng legal? Yes, as a tool. Using it on networks you are not authorized to test is not.

What Odin Research observed

  • 347 recently active relays. Monograph 06 found 347 recently active Ligolo-ng relays on 310 IP addresses in 42 countries. Global records held 938 Ligolo-ng servers in 54 countries.
  • Default port and HTTPS. 129 relays (37.2%) listened on TCP 11601, the unchanged default relay port. Another 94 (27.1%) used 443. Smaller groups used 80, 8443, 8080 and 2083, and five used sequential ports from 11602 for multiple agents.
  • Mainstream clouds. The largest hosts were OVH, Microsoft, DigitalOcean, UpCloud, Amazon and Contabo. The United States, India, France, Germany, Russia and Singapore held 66.3% of relays.
  • No confirmed hostile relays. Five were suspected and 342 were candidates. At port and banner level, a hostile relay looks the same as an authorized red team relay.
  • Feed labels are not attribution. Eleven hosts that third-party feeds tag as YoroTrooper-related carried Ligolo-ng labels. Only one appeared among recently active relays, so the addresses stay unpublished.
  • A second study. Monograph 23 found 36 more Ligolo-ng endpoints on 33 hosts, 14 on 443 and 10 on 11601. One suspected relay presented the tool's built-in self-signed certificate, CN=__AGENTS.

How to detect Ligolo-ng

  • Default ports. Outbound TLS to ports 11601 to 11610 from any internal host is a cheap, high-value alert.
  • The self-signed certificate. A server certificate with the subject CN=__AGENTS points to Ligolo-ng's built-in self-signed mode.
  • Agent command lines. Look for processes with a connect target and Ligolo flags such as -ignore-cert, -accept-fingerprint or -retry, even when the binary is renamed.
  • Unsanctioned wintun.dll loads. On Windows, a process that loads wintun.dll without an approved VPN client deserves a look.
  • Identity correlation. Join risky sign-ins with non-browser TLS or WebSocket connections from the same user within 24 hours. This catches renamed agents that dial plain port 443.

Monograph 06 carries Suricata signatures for Ligolo-ng ports, a Sentinel KQL query that links tunnels to risky Entra ID sign-ins, and Sigma rules for Ligolo-ng agents on Linux and Windows. Monograph 23 adds a Sigma rule for Ligolo-ng on Linux. All are in the Defense Kit.

How to defend against Ligolo-ng tunnels

  1. Default-deny egress. Block outbound TCP 11601 to 11610, and allow servers to reach only the destinations they need.
  2. Force traffic through inspection. Send user traffic through a proxy that blocks direct TLS from non-browser processes.
  3. Segment the network. Network segmentation limits what a tunnel can reach, even if an agent runs.
  4. Use phishing-resistant MFA. Tunnels often follow stolen sessions. Odin Research recommends origin-bound passkeys as a defense against AiTM proxies.
  5. Hunt before you block. Treat external relays as leads. Block an address only with endpoint evidence that your hosts reached it.

Ligolo-ng compared with other tunneling tools

ToolHow it tunnelsWhat Odin Research saw
Ligolo-ngTUN interface over one TLS or WebSocket stream347 active relays, mostly on 11601 and 443
FRPReverse proxy that exposes internal servicesControl panels as a baseline in Monograph 06
ReverseSSHReverse SSH with SOCKS5 and SFTP36 endpoints, 16 on port 3232 (Monograph 27)
SOCKS with proxychainsPer-tool socket hookingOlder approach; handles ICMP and UDP poorly

Frequently asked questions about Ligolo-ng

What is Ligolo-ng?

Ligolo-ng is an open-source tunneling tool for penetration testers. It gives an operator access to an internal network through a reverse TCP or TLS connection, using a virtual TUN interface instead of SOCKS.

Is Ligolo-ng malware?

No. Ligolo-ng is a legitimate pentest tool. Attackers abuse it for pivoting and lateral movement, which is why defenders hunt for it.

Is Ligolo-ng legal?

Yes, when you use it on networks you own or are authorized to test. Using it to reach networks without permission is illegal in most countries.

What port does Ligolo-ng use?

Odin Research found that 37.2% of active relays used TCP 11601, the unchanged default relay port. Many operators move it to 443 to blend with HTTPS traffic.

Does the Ligolo-ng agent need admin rights?

No. The documentation says the agent runs without high privileges. Only the proxy side needs rights to create a TUN interface.

How do I detect Ligolo-ng?

Alert on outbound TLS to ports 11601 to 11610, look for the CN=__AGENTS certificate and Ligolo flags in command lines, watch unsanctioned wintun.dll loads, and correlate tunnels with risky sign-ins.

Ligolo-ng vs SOCKS proxies: what is the difference?

SOCKS-based tools wrap each program in a proxy and handle ICMP and UDP poorly. Ligolo-ng routes whole subnets through a TUN interface, so tools work as if they were on the internal network.

Sources

  1. Ligolo-ng documentation. docs.ligolo.ng/ (checked 21 November 2026)
  2. MITRE ATT&CK, T1572 Protocol Tunneling. attack.mitre.org/techniques/T1572/ (checked 21 November 2026)

Related tools and terms

All Odin Research explanations · Brandefense glossary

Odin Research

Get the rules, not just the definition

Every Odin Research report ships with verified indicators and detection rules you can load today.

Open the Defense Kit