Catch a reverse shell without a VPS or port forwarding
Free, and no account needed for one session. Create a listener and follow along.
Create a listenerAuthorized use only. Use RevSheller only on CTFs, your own labs, training platforms and engagements where you have permission.
The listener problem
A reverse shell needs something listening that the target can reach. In a lab that is surprisingly annoying. At home you sit behind NAT, so you would have to forward a port on a router you may not control, and your ISP may use carrier-grade NAT that makes it impossible. On a laptop at a conference, a coffee shop or a university network, you do not control the router at all.
The usual workarounds each cost something:
- A VPS works, but you pay for it, patch it, lock it down and remember to destroy it. An exposed netcat listener on a public IP is also open to anyone who scans it.
- A TCP tunnel gives you a public address, but free tiers rotate addresses, limit connections, and need a client that stays running.
- Port forwarding ties you to one network and exposes your own machine.
RevSheller is a hosted listener on Cloudflare's edge. The target connects out to it over HTTPS/WSS on port 443, and you work in a terminal in your browser. There is nothing to host, expose or forward.
Step 1: create a session
Open revsheller.com and create a listener. You can try one session without signing up. Registering is free during the beta and unlocks every feature. Each session gets its own subdomain and a per-session target token, so a payload only works for the session it was made for.
Step 2: pick a payload
The payload is the command you run on the machine you are authorized to test. Start with Auto. It tries a Python WebSocket client first, falls back to a curl or wget HTTP relay, then to bash, and Windows targets get a PowerShell stager. If you know the target has a particular runtime, the generator also offers WebSocket and HTTP relay variants for Python, PowerShell, PHP, Node.js, Ruby, Perl, C#, Java and Go, plus encodings such as Base64 for awkward quoting situations.
Because everything is HTTPS or WSS on 443, it usually passes egress rules that block unusual outbound ports.
Step 3: run it and connect
- Copy the payload from the generator.
- Run it on your target: your CTF box, a VM in your home lab, or a system covered by your scope document.
- The terminal in your browser attaches when the target connects. Resize works, and so do interactive programs, because the session is a proper terminal rather than a line buffer.
- When you are finished, delete the session from the interface. Idle sessions also time out.
Reverse versus forward
Most of the time you want a reverse session as above. If the target already has a bind shell on a public host and port, a forward session makes RevSheller dial out to it and relay it to your browser. Forward shells can only reach public internet addresses: private ranges, localhost and port 25 are blocked. For targets on a VPN-only lab network, see the THM and HTB guide.
An honest limitation
Cloudflare does not accept inbound raw TCP. A classic nc or bash -i >& /dev/tcp/... one-liner cannot connect directly to the edge, so use the generated payloads. If your target can only make raw TCP connections, the bridge agent can carry them from your own machine.
Privacy
Shell I/O is relayed live to your browser and is not written to disk or logged. Tokens travel in headers, not URLs.
FAQ
Do I need an account to try it?
No. One anonymous session is allowed. Registered accounts get the full free beta.
Why doesn't nc connect to my session?
See the limitation above: use the Auto or language-specific payloads, or the bridge agent.
Is shell traffic stored?
No. It is relayed live and not stored.
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