[Autogenerated] Okay the moment of truth.
Let's see if that works and it doesn't will fix whatever needs to be fixed.
Let's open this in terminal here.
That's going to be good enough for our purposes.
There's a terminal Visual Studio now.
But of course you can use the command window outside of
the visuals to the environment here.
In any case,
I'm going to go to X 64 debug where we have all our
executable so we have the injector here.
The executable itself and the injected DLL as well.
The thing that we want to to inject.
So the next step is to select the process to be our victim,
so to speak, where you want to inject that DLL so we can use anything really.
But let's just select something that is easily identifiable.
Maybe use paint.
So here's paint looks like it's nicely painted here.
So if I go to process explore just to verify that
the deal is not there just yet.
Let's find paint here is paint.
Let's switch to D.
L.
S.
And if you look at the letter I once we have these names sorted,
injected DLL is nowhere here to be found.
So it's not in the process just yet.
Of course the message box will help us see that but we want to see that.
In fact in process Explorer.
So now we are ready to run our experiment here.
Let's go ahead and use an injector.
We need the process idea.
Of course, that's the first thing.
So going back to process explorer.
I miss the process idea there.
We have 2560.
Okay 25 60 then our path to the DLL, Another four things to work correctly.
We should always specify a full path.
Otherwise the current directory of the target process is going to be used,
which we don't normally control.
So we don't want to have that kind of dependency on our hands here.
It's going to use e DEv share demo here and then x 60 for debug and injected.
DLL.
Okay, here goes mhm.
So if we open up here,
we can see that the message box indeed appeared that's
the message box from process to 5 60.
So that means these things things worked.
And now the process is done because the message box has been
dismissed and now the weight on the threat is over.
And if you go to process Explorer,
we can see hopefully that our DLL is here and indeed it is here that's injected.
DLL is now living within the ams spain process happily ever after, so to speak.
Until M.
S paint is done and then the dealer will be loaded.
So here's a way to inject a DLL into a target process by using a remote thread