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 Platypus? The Open-Source Reverse Shell Manager

A Go console that keeps many remote shells in one place: what it is, why it matters and the few signs it leaves on a network.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
5 min read
Type
Shell manager

In short

Platypus is an open-source tool written in Go that manages many remote shell sessions from one console. It is published on GitHub by WangYihang under the LGPL-3.0 license. Odin Research describes it as a reverse-shell multiplexer with REST and WebSocket control and a default port of 23590. It is dual-use.

Key takeaways

What it is
An LGPL-3.0 Go project on GitHub that its author calls a cross-platform machine manager, used to handle many reverse shells at once.
How it works
Remote agents connect out to a Platypus listener, and the operator manages the sessions over REST and WebSocket. The default port is 23590.
Why it matters
Outbound shells pass most firewalls, and one console can hold many machines, which suits both red teams and intruders.
What Odin Research saw
Two Platypus candidates, none confirmed: one on port 23590 in Japan and one on 443 in the US with a platypus-ingress certificate.
What to do first
Filter server egress, flag connections to port 23590 and check TLS sessions for the platypus-ingress certificate subject.

What is Platypus?

Platypus is an open-source tool, written in Go, for managing many remote shell sessions from one console. It is published on GitHub by WangYihang under the GNU LGPL-3.0 license, and the repository describes it as a modern, cross-platform machine manager. Odin Research classes it as a reverse-shell multiplexer.

The repository was created in August 2018 and was still being updated in November 2026. On 21 November 2026 it had 1,663 stars and 224 forks on GitHub.

A reverse shell turns the usual connection around. Instead of the operator connecting in, a small agent on the remote machine connects out to the operator's server. Outbound connections pass most firewalls more easily than inbound ones. A tool like Platypus collects many of those sessions in one place so the operator can switch between them.

Platypus is dual-use. Red teams and penetration testers use shell managers to keep engagements organized. Intruders use the same kind of tool to keep a backdoor channel open.

How Platypus works

Odin Research's Monograph 27 describes Platypus as a Go manager for many reverse-shell sessions at once, with REST and WebSocket control and a default port of 23590. In practice that means three parts:

  1. A listener on the operator's server that waits for incoming shell sessions.
  2. Sessions from remote machines, each kept open and labelled in the console.
  3. A control interface over REST and WebSocket, so the operator or a script can list sessions and send commands.

Two MITRE ATT&CK techniques describe the network side. A shell on port 23590 is a protocol on a port it is not usually tied to, which is T1571, Non-Standard Port. Control over HTTP or WebSocket fits T1071.001, Web Protocols, which lets command-and-control traffic blend with web use. Commands sent through the shell fall under Command and Scripting Interpreter (T1059).

How attackers use Platypus

Monograph 27 groups Platypus with ReverseSSH as tunnel multiplexers. In Odin's model, these tools and hardware drop-boxes give an operator the same thing: a durable outbound control channel. The session runs over HTTP, SSH inside TLS or WebSocket, and some operators bounce it through a relay first.

That design helps an intruder in three ways:

  • It passes perimeter firewalls, because the remote machine starts the connection.
  • It scales. One console can hold many machines at once.
  • It hides in web traffic when the listener sits on port 443 behind TLS.

The model in Monograph 27 groups families by role. It does not describe one attributed campaign, and no logs from inside target networks were available.

What Odin Research observed

Platypus was a small part of Monograph 27, which covered 89 endpoints on 74 hosts across nine drop-box, tunnel and backdoor families.

  • Two candidates, none confirmed. One listened on the default port 23590 at Evoxt in Japan. The other listened on port 443 at ROUTE 95 in the United States and presented the certificate subject CN=platypus-ingress. Both addresses are withheld.
  • Small next to its peers. ReverseSSH had 36 endpoints in the same study, and the two tunnel multiplexers together made up 38.
  • No shared hosts. No host in the study ran two families, so nothing tied the Platypus candidates to other tools.

The lesson: a Platypus listener is a lead. Without a second signal, it may just as well belong to a tester.

How to detect Platypus

  • The default port. Outbound connections from your hosts to port 23590 on an external server are rare and worth checking.
  • The certificate subject. A TLS session that presents platypus-ingress points to a Platypus listener behind port 443.
  • Long-lived outbound sessions. A server that holds an idle TLS or WebSocket session open to an unknown host for hours deserves a look.
  • Process lineage. Look for shells whose parent is an unknown binary with a network connection, using EDR data.

Monograph 27 carries a Suricata signature for Platypus API control traffic, a Sigma rule for unapproved ReverseSSH or Platypus tunnel clients on Linux, and a YARA rule for ReverseSSH and Platypus manifests. The rules are in the Defense Kit.

How to defend against reverse-shell managers

  1. Filter egress. Let servers reach only the destinations they need. Default-deny outbound traffic on high ports.
  2. Inspect TLS where you can. Certificate subjects and odd ports are only visible if you look at them.
  3. Segment networks. Network segmentation limits what one shell can reach.
  4. Allowlist testers. Keep a list of approved red-team hosts so real alerts stand out.

Platypus compared with other tunnel and shell tools

ToolRoleIn Odin reportsNotes
PlatypusGo reverse-shell multiplexer2 candidates (Monograph 27)Default port 23590
ReverseSSHReverseSSH multiplexer36 endpoints, 5 confirmed (Monograph 27)16 on its default port 3232
Hak5 Cloud C2Hardware drop-box hub23 endpoints, 6 confirmed (Monograph 27)Manages implants such as the LAN Turtle
Ligolo-ngTunnelling and pivoting toolMonographs 06 and 23Encrypted pivots

Frequently asked questions about Platypus

What is Platypus?

Platypus is an open-source Go tool for managing many remote shell sessions from one console. Its GitHub repository describes it as a modern, cross-platform machine manager.

Is Platypus malware?

No. It is a public, LGPL-3.0 licensed tool. It is dual-use: testers use it to organize shells during engagements, and intruders can use it to keep access.

Who made Platypus?

Platypus is published on GitHub by WangYihang. The repository was created in August 2018.

What port does Platypus use?

Odin Research reports a default port of 23590. One Platypus candidate in Monograph 27 used that port, and another sat on 443 behind TLS.

How do I detect Platypus?

Flag outbound connections to port 23590, TLS sessions with a platypus-ingress certificate subject and long-lived outbound sessions from servers. Odin Research publishes Suricata, Sigma and YARA rules for it in its Defense Kit.

Platypus vs ReverseSSH: what is the difference?

Both manage outbound shell sessions. In Monograph 27, Odin Research saw 36 ReverseSSH endpoints with 5 confirmed, against 2 unconfirmed Platypus candidates.

Sources

  1. GitHub REST API, WangYihang/Platypus repository metadata. api.github.com/repos/WangYihang/Platypus (checked 21 November 2026)
  2. MITRE ATT&CK, T1571 Non-Standard Port. attack.mitre.org/techniques/T1571/ (checked 21 November 2026)
  3. MITRE ATT&CK, T1071.001 Application Layer Protocol: Web Protocols. attack.mitre.org/techniques/T1071/001/ (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