Now what you may not have known is that we actually went into singles in the
previous portion of the skill.
See, you can't do one without the other or multiples of the others,
and that's where like the inline and other stuff comes into play it that we'll
get into later.
But when you create a Stager to be able to open up that backdoor channel of
communication,
you have to include at least one payload.
And when we do this, we're creating a singles because we're just using one.
And the payload that we used was the reverse shell, Windows X 64, made a Peter
reverse TCP.
That single payload came back over to our system to be able to allow us using
MSF console
to go through and have communication and commit whatever we want to do.
Now we're going to go back to our screen here for a second.
And we see that our options for the actual payload that we selected are visible
for us.
Let me zoom in here for you a second.
And I wanted to show you the options because you can also see that we're using
that single payload of reverse TCP.
If I zoom out and scroll down to the bottom, you can see that the session has
already been established.
We did this using that single payload when we executed dummy.exe on that
Windows system
to go back and communicate to our listener here in MSF console.
So we're just using one single payload wrapped up and dummy.exe was our stage
for a Stager to be able to go into that target system.
I know you're probably wondering why I didn't clarify this in the previous one.
And it's because these two go hand in hand and I wanted to show the difference
between two specifically here.
So bear with me.
It's this is one of the easiest ways that I learned it and I was taught by a
very good person who was really good with Metasploit.
And the use of a single payload inside of our Stager allows us to manipulate
through that shell.
Now, I want to give you an example of this once that payload of that single
payload is in use.
If we zoom out and we go inside of our MSF console, we can say sessions and
then we can say -c.
The -c is going to be able to allow us to issue a command to that session.
Now the command that we want to use is something simple.
Let's say like a task list.
And we're going to say -i to indicate the session that we're currently
connected with that single payload session.
And this one as I zoom in for you here, you can see that the ID on this active
session is number three.
So the -i is going to be followed by the number three.
And when we do this three and press enter, it runs task list as if it's running
inside the command shell on that.
Windows system is a zoom in for us and show you specifically.
Along with the bunch of information that goes with this as well too.
If you zoom up to the top of this word actually, "brand", and we can make it -
there we go.
Oh, we were almost there.
There we go.
You can see here that it has the image name being the process that's actually
coming up inside of details.
Along with the PID, the session name, meaning what's it running under, like for
instance, secure system, PID 104, is running as a service on the particular
system.
And session's number, meaning how many times this is being invoked or related
to that, and along with membusage.
Membusage will come in later when we start getting into like knobsled, things
like that.
But as you could see here, that the command inside of that session through the
use of that single payload allows us large amounts of capability, but it's just
one single payload.
And as we start moving into the different portions of the skill, you'll see
where we start to get into stages.
And with inline, we're going to try to run multiple commands inside of our
multiple payloads that we sent over to that target system.