Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ngn13/ezcat
an easy interface for managing multiple linux & windows reverse shells over DNS
https://github.com/ngn13/ezcat
netcat reverse-shell-generator reverse-shell-handler revshell shell
Last synced: 8 days ago
JSON representation
an easy interface for managing multiple linux & windows reverse shells over DNS
- Host: GitHub
- URL: https://github.com/ngn13/ezcat
- Owner: ngn13
- License: gpl-3.0
- Created: 2023-09-09T16:59:39.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2024-09-08T00:49:51.000Z (2 months ago)
- Last Synced: 2024-09-08T01:42:39.056Z (2 months ago)
- Topics: netcat, reverse-shell-generator, reverse-shell-handler, revshell, shell
- Language: Go
- Homepage:
- Size: 4.84 MB
- Stars: 6
- Watchers: 3
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# ezcat 🐱 easy reverse shell handler
https://github.com/ngn13/ezcat/assets/78868991/75c3c7c5-6768-47e4-9ef1-0a9e66710773
---
> [!NOTE]
> I'm migrating the agent communication from DNS to TCP because there is really no reason to use DNS
> since the reverse shell connection goes over plain TCP anyway, [see this PR](https://github.com/ngn13/ezcat/pull/82)
### 📋 Features
- Easy to install
- Simple web interface
- Agent communication over DNS
- Receive TCP reverse shells
- Linux & Windows support
- Self deletion because why not
### 🚀 Install
You can easily install ezcat with docker:
```
docker run --rm --network host \
-e PASSWORD=securepassword \
ghcr.io/ngn13/ezcat
```
### ⚙️ Configuration
Configuration is handled with environment variables, here are all the options:
- **`PASSWORD`**: Used to change the login password, by default it's `ezcat`, and for security, you should
definitely change it
- **`SHELLIP`**: By default ezcat will try to detect your interface IP address (giving priority to tunnel interfaces).
If you want set this IP address to something else by default, you can use the `SHELLIP` environment variable
- **`DISABLE_MEGAMIND`**: When set to `1`, it disables the "no shells?" megamind meme that's displayed on the dashboard if you don't have
any active shells
- **`HTTP_PORT`**: Used to change the port that the API server will listen on, default is 5566
- **`AGENT_PORT`**: Used to change the agent communication port, default is 1053
- **`API_URL`**: Used to change the API URL for the front-end application
- **`DATA_DIR`**: Directory that the server will use to store stage builds, default is `./data`
- **`STATIC_DIR`**: Used to change the front-end application (static) directory, it's pre-set in the Dockerfile,
you don't need to worry about it unless you are working on something
- **`PAYLOAD_DIR`**: Specifies the directory that contains the payloads, it's pre-set in the Dockerfile, just like
the `STATIC_DIR` option, don't worry about it
- **`DEBUG`**: When set to `1`, it enables debug output for the server and the stage builds
### ⚒️ Build
To build ezcat, install a recent version go. Then download and [extract the latest release](http://github.com/ngn13/ezcat/releases/latest).
- To build the server, install a recent version of go, change directory into the `server/` directory and run:
```bash
go build
```
- To build the front-end application, install a recent version of node and npm change directory into the `app/` directory and run:
```bash
npm i
npm run build
```
To build different payloads during runtime, you will need GNU `coreutils` and `bash`, `build-essential` tools and optionally `mingw`
for windows builds. After installing these tools, you can run the `server/` binary with the desired configuration.