And welcome back.
Time to touch on a subject of post exploitation.
We have traveled a long way from the beginning, we covered the information gathering where we try to
get as much information about our target that we would find useful for a future attack.
After it, we scanned our target from technical aspect and we discovered it's open ports and softwares
that it runs.
We then used different tools to figure out whether that target has any known durability that we might
be able to exploit.
And then we exploited many different targets from the anticipatable to Windows seven and Windows 10.
We both saw how to exploit its vulnerabilities and then after it, we created our own payloads that
we executed on the target system.
Now comes the part after the exploitation.
What are we going to do now that we're on the target system?
What are we looking for and what cool things can we even do?
Well, we have lots and lots of options, depending on what we want to find, of course, for example,
the most simple thing we can do is scroll through their file system and look through what files and
programs they have on their machine.
Maybe we could find something interesting, such as saved passwords instead of a file or some other
important files for the company that are laying on that machine unprotected.
We could also download files from that machine and also upload files to it in case we want to send another
payload or another executable that we want to run on their system.
We can do all of this with our interpreter Shell.
Just be running a few comments.
Talking about passwords, that is also something that we would look for, we could try to extract saved
passwords from browsers, for example.
Remember, when you click on that button that says, remember me once you log into some Web page?
Well, those passwords could be stored somewhere on their machine.
And why would we go for passwords, you might be asking?
Well, getting Target's online accounts just expands our access to them.
Imagine you were to get their PayPal password and gain access to their PayPal account.
That wouldn't be so pretty for them since you would have access to all of their funds.
Another thing we could try to do is gain access to the entire network from the target machine that we
hacked may be inside of Companies Network.
You managed to get access to one machine, but it doesn't have all the things you might need.
Maybe some important files could be on some other machine from that same network.
In that case, you would want to try to hack that other machine from the machine that you already hacked.
Now, you might be wondering, well, why not from our Linux machine?
Well, maybe machines that belong to that network have more trust between one another.
Maybe they exchange files or communicate with some other software altogether on that same network.
In that sense, it would be easier to get access to one of those machines from a system that is already
inside of their network.
Right.
Maybe we would also want to run our key logger on the machine we got access to.
Now, Kielburger is a program that captures every keyboard input from that machine.
So with this, not only we could maybe capture some passwords that the user of that machine would input
in some secure website or software, but we would also be able to see everything else that he or she
typed from what they searched on the Internet to maybe the messages that they're sending on social media
from that machine or basically anything that they type in the keyboard.
We will be able to see it.
Amazing, right?
You can picture post exploitation as some type of information gathering on the target system.
And these things that we talked about are just a small portion of what we can do once we hack a machine.
Now, the Fed briefly talked about post exploitation theory, let us see what available tools and comments
we can use to achieve all of the things that we mentioned and even more so in the next video.