Welcome to a basic overview of how to get started using the Viper tool, for your various hacking needs.

This won't be a comprehensive guide, but rather a quick start overview, to get you going.

First of all, if you don't already own it, you can download the Viper tool in-game from here: www.viper.com <- This address is for use within the Grey Hack game.
Viper requires metaxploit.so and crypto.so to function properly. Both can be found on your Hackshop.

To keep this simple, we will be limiting the amount of commands used during this mission.

We'll infiltrate a target IP and escalate to root. Then we'll have a look at a few things you can do while you're inside a system, without having to leave Viper.

More complicated scenarios might follow in the future, this one is focused on the very basics and aimed at players new to Viper.

nmap
This will generally be your first step after accepting a contract. The command shows you the status of ports and services running at the scanned IP.
Usage: nmap [IP/DOMAIN]
Example: nmap 105.204.124.106

As you can see, nmap gives us a convenient overview of obvious targets to get into the network.
Either the router at port 0, or the http service at port 80.

exploitscan
Pokes at an exposed port/library, checking for any known vulnerabilities.
Usage: exploitscan [LIB/IP][PORT][PASS/LANIP]
Example: exploitscan 105.204.124.106 80 OR 105.204.124.106 0

It's important to note, that 'Exploitscan' leaves evidence logs on target machines you scan, if your scan returns a shell option. These logs can be traced by other players.

Never exploitscan from your home machine or from an unsecured system.
Be especially careful when exploitscanning other players.

In this instance, we managed to find a shell-giving vulnerability (scii_fresu) in the first memory address we scanned. (0x2173DC79)
I'll also run an exploitscan on port 80.

exploit
Use a previously discovered vulnerability to gain access or escalation.
Usage: exploit [IP/LIB][PORT][MEM][VULN][IP/PASS]
Example: exploit 105.204.124.106 0 0x2173DC79 scii_fresu

The exploit will give us guest shell access. This is how you would normally utilize a simple exploit scanner.
In Viper we have a more efficient way of utilizing the exploits found by the scanner.

targets
Shows a list of all your discovered exploits. What user, IP and access type it gives.
Usage: targets
Example: targets

Here is both the guest shell we found on the router, as well as a user shell found on the http service.

use
Utilizes one of the exploits found, to give you the stated access.
Usage: use [INDEX ID]
Example: use 3

We're now in the system. Let's start the process of escalating to root.

cat
Reads a text file
Usage: cat [PATH]
Example: cat /etc/passwd

We have a hash for root access, let's crack it.

crack
Deciphers a hash.
Usage: crack [HASH]
Example: crack b812f6777367c7d2bde2f3ec42f738d3

We've got root credentials, time to prepare for escalation.

jump
Creates a jump file in a designated directory. A jump file is required to use sudo in Viper.
Usage: jump [PATH]
Example: jump /home/Aileydo

We can now sudo to root. But while we're here, let us also show how to upload any files you might need, onto a target PC.

put
Uploads file to target destination.
Usage: put [HOSTPATH][DESPATH]
Example: put /lib/metaxploit.so /home/Aileydo

As an example, we have now uploaded metaxploit.so to the target computer.
Useful for bringing ScanLan.exe with you, onto target networks.

Now that we've brought metaxploit.so onto the target machine, let's locally load it into Viper.

getlib
Adds metaxploit to the library list, from wherever specified. Requires a previously generated jumpfile to be specified.
Usage: [METAPATH][JUMPPATH]
Example: getlib /home/Aileydo/metaxploit.so /home/Aileydo/jumpfile

If we didn't already have the root credentials from reading the /passwd, or if we were here as a guest shell instead of a user shell, we could now attempt to locally escalate.

We can do this by looking for vulnerabilities in the local libs with the exploitscan command.
For the sake of being thorough, we'll be showing you how to do that as well.

ls
Shows the content of the specified path.
Usage: ls [PATH]
Example: ls /lib

We now know which libraries are present on this machine, for us to exploitscan for vulnerabilities.

exploitscan
Pokes at an exposed port/library, checking for any known vulnerabilities.
Usage: exploitscan [LIB]
Example: exploitscan init.so

To learn how to use the same shortcuts as the ones showcased in the picture above, make sure you read about vars in the bonus section.

There we are, user access once again. We can now cat /etc/passwd just like we did during the previous sections.

We're now ready to sudo to root.

sudo
Change to user or escalate to root
Usage: sudo [USER][PASSWORD][JUMPPATH]
Example: sudo root olders /home/Aileydo/jumpfile

We now have root. Congratulations! Let's show a couple of useful tools while we're in here.

grab
Shows emails information, bank information or both.
Usage: grab [BANK/EMAIL/ALL]
Example: grab all

Yoink. You can never have too many credentials.
Before we go, let's have a look at all the files on the system, see if there's anything we want before we go.

fs
Lists the whole filesystem at once. Great for getting an overview.
Usage: fs
Example: fs

That's a lot of stuff.
Why don't we download that .jpg file? A picture of a lake house sounds pleasant.

get
Downloads target file to target directory.
Usage: [REMPATH][DESTPATH]
Example: get /home/Aileydo/lake_house.jpg /home/guest

We now have a nice picture of a lake house in our guest directory! Fantastic.
Let us remove the jumpFile we created earlier.

rm
Removes files. Bypasses the Trash folder.
Usage: (-r)[PATH]
Example: rm /home/Aileydo/jumpFile

Target eliminated. Before we skedaddle on out of here, let's just be certain we aren't leaving any tracks behind.

corruptlogs
Clears logs on local system.
Usage: corruptlogs
Example: corruptlogs

Alright! You can now safely exit the system.
You have now learned the absolute basics of penetrating target networks using Viper.

Tired of typing out all those long words? Are your poor little sausages getting sore?
Well have I got some good news for you! Welcome to variable commands!

vars
Shows all the shortcut commands currently loaded in Viper.
This allows you to execute long commands with your preferred shortcut.

As you can see, es comes as a default shortcut for exploitscan.
Let's add a couple of our own!

addvar
Adds a shortcut command.
Usage: [INDEX][VALUE]
Example: addvar x targets
Example: addvar ex exploit

We now have a shortcut for calling our targets menu as well as for the exploit command.

Our shortcut list now looks like this:

For thoroughness sake, let's also show how to remove one of those shortcuts.

delvar
Deletes a shortcut command.
Usage: [INDEX]
Example: delvar ex


So this:
exploitscan 105.204.124.106 80
Becomes this:
es 105.204.124.106 80
Think about your fingers! Use shortcuts!

Alright, you have your own preferred shortcuts. Sweet.
Before we close Viper, let's make sure to save our new settings.

save-settings
This saves your preferences to /Config/Viper.conf

There you go, all saved and ready to go.

apt-get
As an alternative to visiting the official in-game website to download the tool, you can now also add the repository address to your apt-get sources.

apt-get addrepo 170.220.64.188
This adds 170.220.64.188, which is currently the official repository, to your trusted sources.

apt-get update
This refreshes your sources and allows you to download whatever is new.


apt-get install viper
This downloads the Viper tool to your machine.


If an update is pushed out, then you can update the tool with the following commands:
apt-get update
apt-get upgrade
Allow the update and there you go.

When using this method, it is recommended that you make sure your "official sources" is shut off and secured in your /etc/apt/sources.txt

If you require help with anything else regarding the Viper tool, feel free to stop by the Discord[discord.gg]

You should also feel free to ask for help in the in-game general chat.
GrumpyBunny is there and able to take questions more often than not.
Shoutout to Volk for making the tool.
Credits to me for writing this.
Thanks to Flames_Yue for reminding me to include dependencies.