Skip to content
reverseshell

Blog

Groovy Reverse Shell: The Jenkins Script Console Classic
How a Groovy reverse shell works on the JVM, the one used against the Jenkins script console, and where else Groovy execution shows up.
groovyjenkinsreverse-shell
Reverse Shells In Containers: The Network Namespace Is The Trap
Container reverse shell testing fails when operators forget network namespaces, minimal images, missing tools, and Kubernetes policy.
containerskubernetesreverse-shell
Reverse Shell Lab Cleanup: The Part People Skip Until Evidence Gets Messy
Authorized reverse shell testing should leave clean notes, stopped listeners, known artifacts, and logs that make sense later.
labcleanuppentest
macOS Reverse Shell: zsh, an Old Bash, and Maybe No Python
How reverse shells work on macOS targets — which interpreters ship, why the default shell is zsh, and the SIP/TCC realities of authorized Mac testing.
macosreverse-shellbash
PowerShell -EncodedCommand: Why Base64, and the UTF-16 Gotcha
How PowerShell -EncodedCommand works, why testers base64-encode reverse shell payloads to dodge quoting, and the UTF-16LE encoding mistake that breaks it.
powershellencodingreverse-shell
Picking The Right Reverse Shell Payload Is Mostly About The Target Runtime
Payload choice should follow target runtime, shell availability, egress path, quoting context, and evidence needs.
payloadsruntimereverse-shell
The Reverse Shell Workflow for OSCP and CTFs
A repeatable reverse shell workflow for exams and CTFs: listener first, enumerate interpreters, pick the payload, catch on 443, upgrade the TTY, and note it for the report.
oscpctfreverse-shell