Skip to content
StrikeCyberStrikeCyber
Field Manual · Attack technique

Web Shells

Reviewed 13 November 2026Attack technique 2 min read

Quick answer

A web shell is a small malicious script placed on a web server that lets an attacker run commands through ordinary web requests. It is the most common way attackers keep access after exploiting a vulnerable web application, file transfer platform or edge device, and it often survives the patch that fixed the original flaw.

On this page
01

How It Works

After exploiting a vulnerability such as an unrestricted file upload, deserialisation flaw or remote code execution bug, the attacker writes a script in the server's language (PHP, ASPX, JSP and so on) into a web-accessible folder. Visiting that URL with the right parameters runs commands on the server. Modern web shells are tiny, obfuscated, password protected and named to blend in with legitimate files. On appliances such as VPNs and email gateways, attackers have planted shells in places that persist through upgrades.

02

Why It Matters

Patching closes the door but does not remove an intruder who is already inside. Many mass-exploitation campaigns plant web shells on thousands of servers within hours of a vulnerability becoming public, then return weeks later to steal data or deploy ransomware. Organisations that patched late but did not hunt for shells have been breached through access gained before the patch.

03

How to Test for It

  1. After any exploited vulnerability on an internet-facing server, hunt for files created or changed around the exposure window in web-accessible folders.
  2. Test web applications for the flaws that lead to shells: file upload controls, path traversal and remote code execution.
  3. Check whether the web server's account can write to folders it serves, and whether it can run system commands.
  4. Check that endpoint detection covers web servers and alerts when a web server process starts a shell or command interpreter.
  5. Use the vendor's integrity-checking tool on appliances, which often detects modified files.
04

How to Reduce the Risk

Patch internet-facing systems urgently, then hunt for persistence rather than assuming the patch was enough. Make web roots read-only to the web server's account, block execution in upload folders, run file integrity monitoring on web content, alert on web server processes spawning shells, and segment web servers so a compromise cannot reach the internal network.

05

Regulatory and Framework Context

In Australia, ASD's ACSC has published joint guidance on detecting and preventing web shell malware, and many ASD alerts on exploited edge devices advise hunting for web shells after patching.

Being exploited now

Threat Radar →

The latest related vulnerabilities confirmed as exploited in the wild.

Latest intel on this topic

Updated hourly from the daily briefing. More in vulnerability news and security alerts.

Common questions

Does patching remove a web shell?

No. A patch fixes the vulnerability but leaves any file the attacker already wrote. You need to hunt for and remove persistence separately.

How do you find a web shell?

Look for recently created or modified scripts in web folders, web server processes starting command shells, unusual requests to rarely used files, and integrity-check differences on appliances.

For testers: finding write-ups

How this shows up in a penetration test report, with severity, verification and remediation, in the StrikeOps Findings Library.

Change log

  1. 13 November 2026First published.
1300 654 898