WEBVTT

00:00:00.000 --> 00:00:03.848 align:middle line:90%


00:00:03.848 --> 00:00:06.253 align:middle line:90%
[MUSIC PLAYING]

00:00:06.253 --> 00:00:10.110 align:middle line:90%


00:00:10.110 --> 00:00:13.560 align:middle line:84%
Injecting payloads into
Windows portable executables.

00:00:13.560 --> 00:00:15.750 align:middle line:84%
In the previous video,
we explored the process

00:00:15.750 --> 00:00:19.470 align:middle line:84%
of encoding both Windows and
Linux payloads with the Shikata

00:00:19.470 --> 00:00:21.690 align:middle line:84%
Ga Nai encoder, and
also took a look

00:00:21.690 --> 00:00:25.260 align:middle line:84%
at how to increase the number
of encoding iterations performed

00:00:25.260 --> 00:00:26.380 align:middle line:90%
on our payloads.

00:00:26.380 --> 00:00:28.380 align:middle line:84%
In this video, we're going
to take a look at how

00:00:28.380 --> 00:00:31.680 align:middle line:84%
to inject payloads into
Windows portable executables,

00:00:31.680 --> 00:00:33.870 align:middle line:84%
with the objective
being to, again,

00:00:33.870 --> 00:00:37.840 align:middle line:84%
evade or avoid signature-based
antivirus detection.

00:00:37.840 --> 00:00:40.090 align:middle line:90%
So let's get started.

00:00:40.090 --> 00:00:42.150 align:middle line:84%
So, I'm just going to
switch over to my Kali VM,

00:00:42.150 --> 00:00:44.490 align:middle line:84%
and we can actually explore
how this can be done

00:00:44.490 --> 00:00:47.940 align:middle line:90%
through the use of MSF Venom.

00:00:47.940 --> 00:00:51.120 align:middle line:84%
All right, so I'm
back on Kali and we

00:00:51.120 --> 00:00:55.810 align:middle line:84%
can get started by typing in
the MS venom command here.

00:00:55.810 --> 00:00:57.480 align:middle line:84%
And at the bottom
here, you will see

00:00:57.480 --> 00:00:59.250 align:middle line:84%
that we have the X
option, which allows

00:00:59.250 --> 00:01:01.210 align:middle line:90%
us to specify a template.

00:01:01.210 --> 00:01:04.410 align:middle line:84%
So this allows us to specify
a custom executable file

00:01:04.410 --> 00:01:07.210 align:middle line:84%
to use as a template
that again, in this case,

00:01:07.210 --> 00:01:09.570 align:middle line:84%
we are trying to inject
our payload into.

00:01:09.570 --> 00:01:12.070 align:middle line:90%
So we can utilize the X option.

00:01:12.070 --> 00:01:15.600 align:middle line:84%
You can also utilize the
K option in conjunction

00:01:15.600 --> 00:01:20.070 align:middle line:84%
with the X option to essentially
preserve the template behavior

00:01:20.070 --> 00:01:22.620 align:middle line:84%
and inject the payload
as a new thread.

00:01:22.620 --> 00:01:24.960 align:middle line:84%
So all of this
can come into play

00:01:24.960 --> 00:01:26.640 align:middle line:84%
whenever you're
trying to utilize

00:01:26.640 --> 00:01:29.280 align:middle line:84%
a legitimate
executable, and again

00:01:29.280 --> 00:01:32.260 align:middle line:84%
try and inject your payload
into the legitimate executable.

00:01:32.260 --> 00:01:34.200 align:middle line:84%
So in order to do
this, we'll first

00:01:34.200 --> 00:01:37.350 align:middle line:84%
of all require a legitimate
portable executable.

00:01:37.350 --> 00:01:39.780 align:middle line:84%
You can find one
know browsing online,

00:01:39.780 --> 00:01:43.210 align:middle line:84%
and of course, the option
or the choice is up to you.

00:01:43.210 --> 00:01:46.020 align:middle line:84%
Some portable
executables may not

00:01:46.020 --> 00:01:48.150 align:middle line:84%
allow for successful
injection, so you

00:01:48.150 --> 00:01:49.380 align:middle line:90%
need to be aware of that.

00:01:49.380 --> 00:01:51.990 align:middle line:84%
In my experience, one
of the best options

00:01:51.990 --> 00:01:55.330 align:middle line:84%
that you can utilize is
the WinRAR executable here.

00:01:55.330 --> 00:01:58.950 align:middle line:84%
So WinRAR is essentially a
file archiver for Windows,

00:01:58.950 --> 00:02:00.270 align:middle line:90%
and it's very popular.

00:02:00.270 --> 00:02:02.650 align:middle line:84%
And again, in my case
and in my testing,

00:02:02.650 --> 00:02:04.420 align:middle line:84%
this has worked
really, really well.

00:02:04.420 --> 00:02:06.330 align:middle line:84%
So in our particular
scenario, we

00:02:06.330 --> 00:02:09.389 align:middle line:84%
are going to generate a
32-bit Meterpreter payload

00:02:09.389 --> 00:02:13.360 align:middle line:84%
and then essentially inject it
into the WinRAR set up file.

00:02:13.360 --> 00:02:15.540 align:middle line:84%
So we can head over
to Download, and we

00:02:15.540 --> 00:02:17.953 align:middle line:84%
can download the
32-bit setup file here,

00:02:17.953 --> 00:02:18.870 align:middle line:90%
which I'm going to do.

00:02:18.870 --> 00:02:20.760 align:middle line:84%
There we are, Save
File, and that's

00:02:20.760 --> 00:02:22.470 align:middle line:90%
in my Downloads directory.

00:02:22.470 --> 00:02:24.930 align:middle line:84%
What I'm now going to do is
just clear up my terminal

00:02:24.930 --> 00:02:27.630 align:middle line:84%
and we can begin the process
of generating the payload

00:02:27.630 --> 00:02:31.050 align:middle line:84%
and then injecting it
within one command.

00:02:31.050 --> 00:02:32.500 align:middle line:84%
All right, so in
order to do this,

00:02:32.500 --> 00:02:35.730 align:middle line:84%
we again go through the process
of specifying the payload as

00:02:35.730 --> 00:02:39.150 align:middle line:84%
well as the architecture, if
it's not already explicitly

00:02:39.150 --> 00:02:40.440 align:middle line:90%
defined within the payload.

00:02:40.440 --> 00:02:44.250 align:middle line:84%
And in our case, because we're
using a 32-bit Meterpreter

00:02:44.250 --> 00:02:46.360 align:middle line:84%
module, again, that
should be no problem.

00:02:46.360 --> 00:02:49.840 align:middle line:84%
So we're to say
Windows Meterpreter,

00:02:49.840 --> 00:02:52.670 align:middle line:90%
and then reverse TCP.

00:02:52.670 --> 00:02:54.960 align:middle line:84%
And we specify the
LHOST option here,

00:02:54.960 --> 00:02:58.110 align:middle line:84%
which is going to be your Kali
Linux IP, or the attacker's IP

00:02:58.110 --> 00:02:58.610 align:middle line:90%
address.

00:02:58.610 --> 00:03:01.190 align:middle line:90%
In my case, it's 10.10.10.5.

00:03:01.190 --> 00:03:03.920 align:middle line:84%
We then specify the port
option, which in this case

00:03:03.920 --> 00:03:05.870 align:middle line:90%
is going to be 1234.

00:03:05.870 --> 00:03:07.850 align:middle line:90%
Again, feel free to change that.

00:03:07.850 --> 00:03:11.090 align:middle line:84%
We can then specify our encoder,
which as we already know,

00:03:11.090 --> 00:03:16.400 align:middle line:84%
is going to be Shikata Ga
Nai, so X86 shikata_ganai.

00:03:16.400 --> 00:03:17.060 align:middle line:90%
There we are.

00:03:17.060 --> 00:03:20.280 align:middle line:84%
We can then increase the
encoding iterations to 10,

00:03:20.280 --> 00:03:21.200 align:middle line:90%
if we want.

00:03:21.200 --> 00:03:23.720 align:middle line:84%
And then this is where
we specify the format.

00:03:23.720 --> 00:03:26.390 align:middle line:84%
So we can say the
format is an executable,

00:03:26.390 --> 00:03:29.900 align:middle line:84%
and we can then specify
the X flag or the X option

00:03:29.900 --> 00:03:32.510 align:middle line:84%
to essentially
inject our payload

00:03:32.510 --> 00:03:36.140 align:middle line:84%
into the executable or
the portable executable

00:03:36.140 --> 00:03:37.880 align:middle line:90%
that we will now specify.

00:03:37.880 --> 00:03:41.720 align:middle line:84%
So now is where you specify
the actual WinRAR executable

00:03:41.720 --> 00:03:42.590 align:middle line:90%
that we downloaded.

00:03:42.590 --> 00:03:45.630 align:middle line:84%
So that is stored in
my Downloads directory,

00:03:45.630 --> 00:03:49.020 align:middle line:84%
and you can see we have
the WinRAR 6.02 .exe there,

00:03:49.020 --> 00:03:52.040 align:middle line:84%
so we're going to specify
that as the actual portable

00:03:52.040 --> 00:03:54.980 align:middle line:84%
executable that we want to
inject our payload into.

00:03:54.980 --> 00:03:59.540 align:middle line:84%
After this, we can then
output our final executable

00:03:59.540 --> 00:04:00.560 align:middle line:90%
into any directory.

00:04:00.560 --> 00:04:03.200 align:middle line:84%
In our case, I'm going
to specify or save it

00:04:03.200 --> 00:04:05.510 align:middle line:84%
into the Windows
Payloads folder,

00:04:05.510 --> 00:04:09.530 align:middle line:84%
and I'm just going to call
it WinRAR.exe, all right?

00:04:09.530 --> 00:04:12.170 align:middle line:84%
And we're just going to
hit Enter and give that

00:04:12.170 --> 00:04:12.830 align:middle line:90%
a few seconds.

00:04:12.830 --> 00:04:21.650 align:middle line:90%


00:04:21.650 --> 00:04:22.150 align:middle line:90%
All right.

00:04:22.150 --> 00:04:25.990 align:middle line:84%
As you can see, you want to pay
close attention to the output

00:04:25.990 --> 00:04:27.850 align:middle line:90%
generated by MS Venom.

00:04:27.850 --> 00:04:31.090 align:middle line:84%
So first and foremost,
it specifies the platform

00:04:31.090 --> 00:04:33.700 align:middle line:84%
correctly as Windows, as
well as the architecture,

00:04:33.700 --> 00:04:36.340 align:middle line:84%
and then it utilizes the
Shikata Ga Nai encoder

00:04:36.340 --> 00:04:39.280 align:middle line:84%
and goes through 10 iterations
of encoding the payload

00:04:39.280 --> 00:04:40.540 align:middle line:90%
with Shikata Ga Nai.

00:04:40.540 --> 00:04:42.460 align:middle line:84%
And at the end here,
it doesn't give us

00:04:42.460 --> 00:04:44.860 align:middle line:84%
any error here or
any error message

00:04:44.860 --> 00:04:47.570 align:middle line:84%
that could indicate that the
injection process failed.

00:04:47.570 --> 00:04:51.280 align:middle line:84%
So if we check out the actual
Windows Payloads directory,

00:04:51.280 --> 00:04:52.930 align:middle line:84%
we should be able
to see that we have

00:04:52.930 --> 00:04:57.220 align:middle line:84%
the WinRAR.exe right over here,
and we can now transfer this

00:04:57.220 --> 00:04:58.280 align:middle line:90%
over to the target.

00:04:58.280 --> 00:05:01.360 align:middle line:84%
So what I'll do is I
will set up a web server

00:05:01.360 --> 00:05:03.590 align:middle line:84%
to host these files
within this directory.

00:05:03.590 --> 00:05:08.560 align:middle line:84%
So I'm going to say sudo
Python m simple HTTP server.

00:05:08.560 --> 00:05:10.300 align:middle line:84%
There we are,
simple HTTP server,

00:05:10.300 --> 00:05:12.280 align:middle line:90%
and I'll host this on port 80.

00:05:12.280 --> 00:05:14.170 align:middle line:84%
We now want to set
up our listener,

00:05:14.170 --> 00:05:15.590 align:middle line:90%
or multi handler if you will.

00:05:15.590 --> 00:05:19.950 align:middle line:84%
So I'm going to open
up MSF console, give

00:05:19.950 --> 00:05:21.690 align:middle line:90%
that a few seconds to start up.

00:05:21.690 --> 00:05:28.860 align:middle line:90%


00:05:28.860 --> 00:05:32.300 align:middle line:84%
We are then going to
specify the multi handler,

00:05:32.300 --> 00:05:35.490 align:middle line:84%
set the payload that we used
to generate our executables,

00:05:35.490 --> 00:05:41.240 align:middle line:84%
so set payload to Windows,
Meterpreter, reverse TCP,

00:05:41.240 --> 00:05:44.130 align:middle line:84%
and then set the LHOST
options accordingly.

00:05:44.130 --> 00:05:48.530 align:middle line:84%
So LHOST is going to be equal
to whatever value we specify,

00:05:48.530 --> 00:05:50.840 align:middle line:84%
which in this case
is 10.10.10.5,

00:05:50.840 --> 00:05:54.320 align:middle line:90%
and then LPORT is 1234.

00:05:54.320 --> 00:05:56.840 align:middle line:84%
And we can just Run to
start up the handler.

00:05:56.840 --> 00:05:57.410 align:middle line:90%
There we are.

00:05:57.410 --> 00:06:01.220 align:middle line:84%
So we can now switch over
to the Windows system.

00:06:01.220 --> 00:06:03.530 align:middle line:84%
And I'm back on the Windows
system, and right over

00:06:03.530 --> 00:06:06.920 align:middle line:84%
here through the web server,
I can download the WinRAR.exe

00:06:06.920 --> 00:06:08.370 align:middle line:90%
that we generated.

00:06:08.370 --> 00:06:10.220 align:middle line:84%
So I'm going to hit
Save and store it

00:06:10.220 --> 00:06:11.570 align:middle line:90%
within the Downloads folder.

00:06:11.570 --> 00:06:13.490 align:middle line:90%
There we are, Save, Close.

00:06:13.490 --> 00:06:15.240 align:middle line:84%
And if we open up
the Downloads folder,

00:06:15.240 --> 00:06:19.020 align:middle line:84%
you can see that actually looks
like the WinRAR setup file.

00:06:19.020 --> 00:06:20.840 align:middle line:84%
However, because
we did not specify

00:06:20.840 --> 00:06:23.150 align:middle line:84%
the K option to maintain
the functionality

00:06:23.150 --> 00:06:25.460 align:middle line:84%
of the executable,
what will happen here

00:06:25.460 --> 00:06:27.010 align:middle line:84%
is when we double
click on it, it

00:06:27.010 --> 00:06:30.050 align:middle line:84%
will actually not provide us
with the WinRAR installer.

00:06:30.050 --> 00:06:32.690 align:middle line:84%
It'll just execute
the actual payload.

00:06:32.690 --> 00:06:35.990 align:middle line:84%
However, if you take a look
at the actual file description

00:06:35.990 --> 00:06:39.230 align:middle line:84%
here, you can see it still
maintains the actual company

00:06:39.230 --> 00:06:43.080 align:middle line:84%
and developer that actually
developed WinRAR, which again,

00:06:43.080 --> 00:06:45.650 align:middle line:84%
can help with the authenticity
when you're trying to perform

00:06:45.650 --> 00:06:46.790 align:middle line:90%
a client side attack.

00:06:46.790 --> 00:06:48.900 align:middle line:84%
It also provides it
with a file version.

00:06:48.900 --> 00:06:51.440 align:middle line:84%
So if we double click on it,
because it's an installer,

00:06:51.440 --> 00:06:53.493 align:middle line:84%
it'll prompt me to
enter a password here,

00:06:53.493 --> 00:06:54.410 align:middle line:90%
which I'm going to do.

00:06:54.410 --> 00:06:56.810 align:middle line:90%
So I am, and there we are.

00:06:56.810 --> 00:06:59.328 align:middle line:90%


00:06:59.328 --> 00:06:59.870 align:middle line:90%
There we are.

00:06:59.870 --> 00:07:01.370 align:middle line:84%
And once we execute
it, it is going

00:07:01.370 --> 00:07:03.690 align:middle line:84%
to execute the
payload in memory.

00:07:03.690 --> 00:07:05.720 align:middle line:84%
So we can now switch
over to the Kali VM

00:07:05.720 --> 00:07:09.190 align:middle line:84%
and see whether we got
a Meterpreter session.

00:07:09.190 --> 00:07:11.380 align:middle line:84%
All right, so I'm back on
Kali, and as you can see,

00:07:11.380 --> 00:07:12.970 align:middle line:90%
we get a Meterpreter session.

00:07:12.970 --> 00:07:16.180 align:middle line:84%
And if I type in sysinfo, you
can see we still have access

00:07:16.180 --> 00:07:17.630 align:middle line:90%
to the Windows system.

00:07:17.630 --> 00:07:18.130 align:middle line:90%
All right.

00:07:18.130 --> 00:07:21.820 align:middle line:84%
Now, once you've established
access on a target system

00:07:21.820 --> 00:07:23.740 align:middle line:84%
through a client
side attack, one

00:07:23.740 --> 00:07:26.110 align:middle line:84%
of the commands I would
recommend that you run

00:07:26.110 --> 00:07:31.690 align:middle line:84%
is the actual post-exploitation
module called migrate, right?

00:07:31.690 --> 00:07:33.880 align:middle line:84%
Now, this
post-exploitation module

00:07:33.880 --> 00:07:36.220 align:middle line:84%
is a Windows
post-exploitation module

00:07:36.220 --> 00:07:40.930 align:middle line:84%
that will manage the actual
process that the Meterpreter

00:07:40.930 --> 00:07:43.510 align:middle line:84%
payload is currently
running on to another one,

00:07:43.510 --> 00:07:46.510 align:middle line:84%
or it'll inject it into
another one in the event

00:07:46.510 --> 00:07:49.660 align:middle line:84%
that process is eventually
stopped by Windows.

00:07:49.660 --> 00:07:51.730 align:middle line:84%
This can be very
useful in, again,

00:07:51.730 --> 00:07:53.090 align:middle line:90%
preventing that from happening.

00:07:53.090 --> 00:07:56.050 align:middle line:84%
So when I hit run
post-Windows manage migrate,

00:07:56.050 --> 00:07:59.330 align:middle line:84%
it'll actually migrate the
process into another one.

00:07:59.330 --> 00:08:01.600 align:middle line:84%
And in this case, it's
going to call or spawn

00:08:01.600 --> 00:08:05.320 align:middle line:84%
the notepad.exe process, and it
will migrate into that process

00:08:05.320 --> 00:08:07.720 align:middle line:84%
and it will then provide
you with the process ID.

00:08:07.720 --> 00:08:09.220 align:middle line:84%
At this point, you
really don't need

00:08:09.220 --> 00:08:11.530 align:middle line:84%
to worry about these
post-exploitation modules.

00:08:11.530 --> 00:08:13.180 align:middle line:84%
We'll explore them
when we actually

00:08:13.180 --> 00:08:16.000 align:middle line:84%
get into the actual
post-exploitation phase

00:08:16.000 --> 00:08:17.630 align:middle line:90%
or section of this course.

00:08:17.630 --> 00:08:19.450 align:middle line:84%
So again, we have
successfully been

00:08:19.450 --> 00:08:20.960 align:middle line:90%
able to migrate our process.

00:08:20.960 --> 00:08:23.800 align:middle line:84%
And again, if we type in
sysinfo, we still have access.

00:08:23.800 --> 00:08:25.118 align:middle line:90%
I can list all the files here.

00:08:25.118 --> 00:08:27.160 align:middle line:84%
So we're currently within
the Downloads directory

00:08:27.160 --> 00:08:29.830 align:middle line:84%
on the target system, and
we can see that it actually

00:08:29.830 --> 00:08:33.260 align:middle line:84%
lists out the contents of the
Downloads directory perfectly.

00:08:33.260 --> 00:08:33.760 align:middle line:90%
All right?

00:08:33.760 --> 00:08:36.429 align:middle line:84%
Now, the other option that
I mentioned, you can use

00:08:36.429 --> 00:08:37.690 align:middle line:90%
is the K option.

00:08:37.690 --> 00:08:39.700 align:middle line:84%
Now, the K option
will essentially

00:08:39.700 --> 00:08:41.620 align:middle line:84%
maintain the actual
functionality

00:08:41.620 --> 00:08:43.480 align:middle line:84%
of the portable
executable that you're

00:08:43.480 --> 00:08:45.100 align:middle line:90%
injecting your payload into.

00:08:45.100 --> 00:08:49.540 align:middle line:84%
Now, what this means is that if
we again inject our Meterpreter

00:08:49.540 --> 00:08:53.500 align:middle line:84%
payload into the WinRAR
setup file, what will happen

00:08:53.500 --> 00:08:56.260 align:middle line:84%
is when we transfer that
executable onto the target

00:08:56.260 --> 00:08:58.340 align:middle line:84%
system and the
target clicks on it,

00:08:58.340 --> 00:09:02.150 align:middle line:84%
it will actually launch up
the WinRAR setup or installer,

00:09:02.150 --> 00:09:04.570 align:middle line:84%
so it's going to maintain
the original functionality

00:09:04.570 --> 00:09:06.340 align:middle line:90%
of the portable executable.

00:09:06.340 --> 00:09:09.250 align:middle line:84%
And it's then going to execute
the interpreter payload

00:09:09.250 --> 00:09:12.700 align:middle line:84%
and again consequently provide
us with a Meterpreter session.

00:09:12.700 --> 00:09:17.360 align:middle line:84%
However, this will not work
for most portable executables

00:09:17.360 --> 00:09:17.860 align:middle line:90%
out there.

00:09:17.860 --> 00:09:20.410 align:middle line:84%
And in the case of WinRAR,
let's actually test

00:09:20.410 --> 00:09:21.950 align:middle line:90%
and see whether this will work.

00:09:21.950 --> 00:09:23.530 align:middle line:84%
So I'll use the
previous command,

00:09:23.530 --> 00:09:26.890 align:middle line:84%
and I'll just call
this WinRAR New.

00:09:26.890 --> 00:09:28.510 align:middle line:84%
We'll just call it
WinRAR New, so I'm

00:09:28.510 --> 00:09:32.200 align:middle line:84%
going to output it into a new
executable called WinRAR New.

00:09:32.200 --> 00:09:36.010 align:middle line:84%
And right over here, after
we specify the actual X

00:09:36.010 --> 00:09:38.860 align:middle line:84%
option or before that, we
can specify the K option.

00:09:38.860 --> 00:09:40.870 align:middle line:84%
That'll keep the
original functionality

00:09:40.870 --> 00:09:42.390 align:middle line:90%
of the WinRAR setup file.

00:09:42.390 --> 00:09:43.610 align:middle line:90%
This is the file here.

00:09:43.610 --> 00:09:45.580 align:middle line:84%
So if we hit Enter,
we should get an error

00:09:45.580 --> 00:09:49.510 align:middle line:84%
because this particular portable
executable may not provide us

00:09:49.510 --> 00:09:51.670 align:middle line:84%
with the ability to
actually inject the payload,

00:09:51.670 --> 00:09:56.048 align:middle line:84%
and furthermore, retain
the original functionality.

00:09:56.048 --> 00:09:56.590 align:middle line:90%
There we are.

00:09:56.590 --> 00:09:58.900 align:middle line:84%
So as you can see at the
end, it's still this error.

00:09:58.900 --> 00:10:02.290 align:middle line:84%
The template file doesn't have
any exports to inject into.

00:10:02.290 --> 00:10:04.690 align:middle line:84%
So again, this will
require a lot of testing,

00:10:04.690 --> 00:10:08.200 align:middle line:84%
and you can try it out with
various portable executables

00:10:08.200 --> 00:10:11.560 align:middle line:84%
or setup files and see which
ones you have luck with.

00:10:11.560 --> 00:10:13.660 align:middle line:84%
As I said, this
technique is really not

00:10:13.660 --> 00:10:16.360 align:middle line:84%
used anymore, primarily
because of the fact that

00:10:16.360 --> 00:10:18.940 align:middle line:84%
antivirus solutions have
become much more advanced

00:10:18.940 --> 00:10:20.560 align:middle line:84%
and their signature
database is quite

00:10:20.560 --> 00:10:23.680 align:middle line:84%
comprehensive in regards
to the ability to detect

00:10:23.680 --> 00:10:27.040 align:middle line:84%
payloads, especially payloads
generated by MSF Venom.

00:10:27.040 --> 00:10:28.790 align:middle line:84%
However, this
technique will again

00:10:28.790 --> 00:10:31.510 align:middle line:84%
help you in furthermore
modifying or changing

00:10:31.510 --> 00:10:33.400 align:middle line:84%
the actual signature,
because you are now

00:10:33.400 --> 00:10:37.280 align:middle line:84%
injecting the actual shellcode
into a legitimate executable.

00:10:37.280 --> 00:10:40.660 align:middle line:84%
So again, you can test this with
other executables, if you want.

00:10:40.660 --> 00:10:42.730 align:middle line:84%
And yeah, that's pretty
much going to be it

00:10:42.730 --> 00:10:45.600 align:middle line:90%
for this demonstration.

00:10:45.600 --> 00:10:47.540 align:middle line:84%
All right, so in
the next video, we

00:10:47.540 --> 00:10:50.210 align:middle line:84%
will be exploring the
process of automating

00:10:50.210 --> 00:10:53.000 align:middle line:84%
some of the Metasploit commands
that are quite repetitive,

00:10:53.000 --> 00:10:55.130 align:middle line:84%
and we'll be able
to accomplish this

00:10:55.130 --> 00:10:57.740 align:middle line:84%
through the use of a
Metasploit RC script,

00:10:57.740 --> 00:10:59.760 align:middle line:90%
or a Metasploit resource script.

00:10:59.760 --> 00:11:02.230 align:middle line:90%
So I'll see you there.

00:11:02.230 --> 00:11:03.000 align:middle line:90%