Web Shell
A malicious script on a web server giving remote command access.
What it is
A script planted on a web server that accepts attacker input through HTTP requests and executes commands or file operations on the host. It turns a normal web request into a remote control interface.
Why it matters
Web shells are a durable foothold on internet-facing servers and ride entirely over expected web ports, so detecting them often means scrutinizing the server's own request logs and unexpected new files rather than just the network edge.
In practice
Spotting POST requests to an obscure new .aspx file in the web logs, the telltale traffic of an attacker driving a freshly dropped web shell.
What to look for
- New scripts in web folders.
- Web server processes spawning cmd, sh or PowerShell.
- POST requests to files that are rarely visited.
Common mistake
Deleting the file and stopping. Find how it got there and what it was used for.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- PCAP Triage
A first pass over a capture: conversations, protocol mix, DNS, HTTP hosts and TLS names.
- Network Case
A host suspected of beaconing: work its capture from scope to beacon, then the port recall and subnet math behind it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Burp Suite Commercial
An intercepting proxy for testing web apps by hand and with its scanner.
-
ZAP Open source
An open source web app scanner and proxy, often run in CI pipelines.
-
Cloudflare WAF Commercial
Blocks common web attacks at the edge while the code gets fixed.
Read next
- Reverse Shell: A compromised host that dials out to give the attacker a shell.
- Bind Shell: A shell that listens on a port for the attacker to connect in.
- Data Staging: Collecting and bundling stolen data before it leaves the network.