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 ReverseSSH? How the Reverse Shell Tunneling Tool Works

A reverse shell tool that speaks native SSH and hides inside TLS or WebSockets. Testers love it, and so do intruders. How to tell them apart.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
7 min read
Type
Tunneling tool (dual-use)

In short

ReverseSSH is an open-source tool that lets an operator manage reverse shells with ordinary SSH commands. A small client on the target dials out to a server over TCP, TLS, HTTP or WebSockets. Through that one connection the operator gets a shell, file transfer and port forwarding. Penetration testers and intruders both use it.

Key takeaways

What it is
An open-source reverse shell manager, published as reverse_ssh by NHAS, that uses native SSH syntax and supports SCP, SFTP and port forwarding.
How it works
The client calls out from the target to a catcher server, so inbound firewall rules do not stop it. The session can be wrapped in TLS or WebSockets.
Why it matters
Outbound SSH-style tunnels are hard to spot. One connection gives an operator a shell, a SOCKS proxy into the network and file transfer.
What Odin Research saw
36 ReverseSSH endpoints on 30 hosts in Monograph 27, 16 on port 3232. Two TLS-wrapped listeners were published for blocking; 8 look-alikes were mail servers.
What to do first
Hunt for self-signed certificates named after their own address and port, and for outbound sessions to port 3232 from servers.

What is ReverseSSH?

ReverseSSH is an open-source tool that lets an operator manage and connect to reverse shells using native SSH commands. A client on the target dials out to a server, and the operator then uses SSH, SCP and SFTP through that link. Its README describes mutual client and server authentication for trusted control channels.

This page covers the reverse_ssh project published by NHAS on GitHub, which Odin Research's reports cite. Odin also refers to it by its short name, rssh.

The idea is simple. Most firewalls block inbound connections but allow outbound ones. A reverse shell turns the connection around: the target calls the operator. ReverseSSH adds the comfort of real SSH on top, including port forwarding, so the operator can reach other hosts behind the firewall.

That makes ReverseSSH a dual-use tool. Red teams use it in authorized tests. Intruders use it for persistence and command and control. A ReverseSSH listener alone does not show which.

How ReverseSSH works

ReverseSSH has a catcher server and a client.

  1. The server runs on an operator-controlled host and waits for clients. Odin Research saw it most often on port 3232, which the project's own examples use.
  2. The client is a single binary placed on the target. It dials out and registers with the server.
  3. The operator connects to the server with an ordinary SSH client and picks a registered target.

The README lists several network transports beyond plain SSH: HTTP, WebSockets and TLS. They exist for networks where deep packet inspection blocks outbound SSH. Wrapped in TLS on port 443, the session looks much like web traffic.

Once connected, the operator gets the features of SSH itself. The README lists native SCP and SFTP for file transfer, plus dynamic, local and remote port forwarding. Dynamic forwarding turns the target into a SOCKS proxy, a common route to lateral movement.

MITRE ATT&CK files this behavior under Protocol Tunneling (T1572): wrapping traffic in another protocol to avoid filtering or reach systems that are otherwise unreachable.

How attackers use ReverseSSH

For an intruder, ReverseSSH solves three problems at once. It keeps access after a reboot or a password change. It gives a proxy into the internal network. It blends into SSH or HTTPS traffic that many firewalls allow.

Hunt.io describes ReverseSSH as hard to detect for exactly that reason: it uses legitimate SSH over outbound connections that firewalls often permit. Its advice is to watch for abnormal outbound SSH sessions and review traffic behavior.

Public case reporting exists but is thin. In May 2025, an independent researcher writing at dmpdump analyzed a low-detection Linux backdoor. Pivoting on its server led to an NHAS reverse_ssh client configured with the same address and port. The author called a link to a Chinese threat actor "likely", based on circumstantial hosting and proxy clues, not confirmed attribution.

ReverseSSH also fits a wider pattern. Odin Research groups it with FRP, Platypus and Hak5 Cloud C2 as tools that keep access from the inside out.

What Odin Research observed

ReverseSSH appears in two Odin Research studies, both over two-week windows ending 18 November 2026.

  • Monograph 12. Monograph 12 counted 30 ReverseSSH records on 23 IPs. Eleven listened on port 3232: four as plaintext SSH and seven behind self-signed TLS certificates with the subject CN=:3232. Plaintext listeners sent banners such as SSH-2.0-Go.
  • Monograph 27. Monograph 27 found ReverseSSH to be the largest of nine persistent-access families: 36 endpoints on 30 hosts, 16 on port 3232. Five on dedicated cloud hosting are confirmed.
  • Two published hosts. Only two hosts, one in Brazil and one in Singapore, were published for blocking. Both wrap SSH in TLS under a self-signed certificate named after their own address and port, and share a TLS fingerprint.
  • Held back on purpose. Two plain HTTP listeners stayed in analyst review, because a testing tool alone is not a hostile signal. A listener on Korea Telecom home broadband went on a short watchlist instead.
  • Mail server look-alikes. Eight "ReverseSSH" matches were POP3 and POP3S mail servers at an Italian hosting provider. Blocking them would have cut legitimate email.

How to detect ReverseSSH

  • Self-referencing certificates. A self-signed certificate whose common name is its own IP:port, or CN=:3232, is rare on real services and a strong second signal.
  • Outbound to 3232. Servers that open sessions to port 3232 deserve a look, especially when the process is not a known SSH client.
  • SSH banners on odd ports. An SSH-2.0-Go banner on 3232, 8082 or 8443 points to a Go-based SSH server rather than OpenSSH.
  • WebSocket tunnels. In decrypted HTTP, look for an /rssh/ws request with an Upgrade: websocket header.
  • Command lines. On Linux hosts, look for reverse_ssh or :3232 in process arguments, or ssh -R to unusual ports.
  • Skip mail ports. Ignore matches on 110, 143, 465, 993 and 995; Odin found mail servers there.

Odin Research publishes rules for these signals. Monograph 12 has a Suricata signature for ReverseSSH banners, a Sigma rule for Hak5 or ReverseSSH tunnels and a YARA rule for provisioning files. Monograph 27 adds a Suricata signature for ReverseSSH WebSocket tunnels, Sigma and YARA rules, and a KQL hunt. All are in the Defense Kit. Pair TLS fingerprints such as JARM with a certificate check before acting.

How to defend against ReverseSSH

  1. Control egress. Servers should reach the internet only through named destinations. An unexplained long-lived TLS session from a server is a lead.
  2. Segment the network. Segmentation limits what a SOCKS proxy on one host can reach.
  3. Audit edge Linux hosts. Monograph 27 recommends checking for unapproved ReverseSSH, stunnel and Node.js proxy processes.
  4. Register approved tests. If your red team uses ReverseSSH, record its hosts so real alerts stand out.
  5. Block with evidence. Block listeners with a second hostile signal. Keep plain installs and mail-port matches off block lists to avoid false positives.

ReverseSSH compared with other tunneling tools

ToolHow it tunnelsWhat Odin Research saw
ReverseSSHNative SSH over TCP, TLS, HTTP or WebSockets; shell, SFTP and SOCKS in one link36 endpoints, 16 on 3232; 2 TLS-wrapped hosts published (Monograph 27)
FRPReverse proxy that exposes services behind NAT114 relays, 86 with a dashboard on 7500 (Monograph 12)
PlatypusTunnel multiplexer for shells and proxyingGrouped with ReverseSSH as a tunnel multiplexer (Monograph 27)
Hak5 Cloud C2Controller for hardware drop-box implants23 endpoints; one published next to a GoPhish server (Monograph 27)

Frequently asked questions about ReverseSSH

What is ReverseSSH?

ReverseSSH is an open-source tool that manages reverse shells using native SSH commands. A client on the target calls out to a server over TCP, TLS, HTTP or WebSockets, and the operator gets a shell, file transfer and port forwarding.

Is ReverseSSH malware?

No. It is a dual-use tool published openly on GitHub and used by penetration testers. A ReverseSSH client you did not install on your own server should be handled as a backdoor.

Is ReverseSSH legal to use?

Yes, on systems you own or are authorized to test. Installing it on systems without permission is illegal in most countries.

What port does ReverseSSH use?

The project's examples use port 3232, and Odin Research saw 16 of 36 endpoints there. Operators can wrap it in TLS on 443 or other ports.

Who made ReverseSSH?

The reverse_ssh project is published on GitHub by NHAS. Odin Research's reports cite that repository.

How do I detect ReverseSSH?

Look for self-signed certificates named after their own IP and port, sessions to port 3232, SSH-2.0-Go banners on unusual ports, /rssh/ws WebSocket upgrades and reverse_ssh in command lines. Odin Research publishes Suricata, Sigma, YARA and KQL rules in its Defense Kit.

ReverseSSH vs FRP: what is the difference?

FRP is a reverse proxy that exposes a service behind NAT through a relay. ReverseSSH gives an operator a full SSH session on the target, with shell, file transfer and SOCKS proxying over one connection.

Why did a mail server match a ReverseSSH rule?

Some mail servers' banners and certificates resemble a tool signature. Odin Research found eight such POP3 and POP3S servers, so matches on mail ports should be excluded from ReverseSSH hunting.

Sources

  1. NHAS, reverse_ssh README, GitHub. raw.githubusercontent.com/NHAS/reverse_ssh/main/README.md (checked 21 November 2026)
  2. MITRE ATT&CK, Protocol Tunneling, T1572. attack.mitre.org/techniques/T1572/ (checked 21 November 2026)
  3. Hunt.io, ReverseSSH malware family overview. hunt.io/malware-families/reversessh (checked 21 November 2026)
  4. dmpdump, "Likely Chinese Threat Actor Uses Low Detection Linux Backdoor and NHAS Reverse SSH", 1 May 2025. dmpdump.github.io/posts/Low_Detection_backdoor_NHAS_RSSH (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