WEBVTT

00:00:00.032 --> 00:00:01.031
(Aaron) Got it.

00:00:01.032 --> 00:00:03.031
Getting into this, can we detonate it?

00:00:03.032 --> 00:00:04.032
Let's do it.

00:00:04.032 --> 00:00:06.831
(Tyler) So I've got a number of tools here that we've talked about in our

00:00:06.831 --> 00:00:11.032
previous Play by Plays about when we set up the sandbox.

00:00:11.032 --> 00:00:13.032
But we're going to run three different tools.

00:00:13.032 --> 00:00:16.032
On the right-hand side here I have Process Explorer,

00:00:16.032 --> 00:00:18.932
and again we're just using Process Explorer to kind of

00:00:18.932 --> 00:00:21.032
watch to see what the malware does.

00:00:21.032 --> 00:00:23.032
It's more of a visual indicator for us.

00:00:23.032 --> 00:00:24.031
But then we have two other tools,

00:00:24.032 --> 00:00:27.032
which are going to be used to monitor its behavior.

00:00:27.032 --> 00:00:31.031
Now the first is Regshot, and I'm going to go ahead and launch Regshot.

00:00:31.032 --> 00:00:35.032
Regshot, again, takes snapshots at points in time and then compares the two.

00:00:35.032 --> 00:00:38.032
So I'm going to tell it to take its first snapshot,

00:00:38.032 --> 00:00:41.032
and this'll take a couple seconds to maybe a minute or so,

00:00:41.032 --> 00:00:45.032
really depending upon how busy your system is,

00:00:45.032 --> 00:00:47.031
the resources, and so on.

00:00:47.032 --> 00:00:50.032
(Aaron) Right, we also talked about,

00:00:50.032 --> 00:00:51.632
when you've ran it on Windows 10 you've been having

00:00:51.632 --> 00:00:53.032
problems recently with the current version.

00:00:53.032 --> 00:00:56.032
(Tyler) Yeah, Regshot can kind of lock up every once in a while,

00:00:56.032 --> 00:01:00.031
and it seems to do that on some of the later versions of Windows 10.

00:01:00.032 --> 00:01:03.031
But on Windows 7, for the most part, it seems to be okay.

00:01:03.032 --> 00:01:05.032
(Aaron) So that's good to know in case you run into that.

00:01:05.032 --> 00:01:05.476
(Tyler) Right.

00:01:05.476 --> 00:01:09.032
So, I'm just going to minimize that, and then we've got Process Monitor here.

00:01:09.032 --> 00:01:12.746
What I'm going to do is I'm going to click on the little magnifying

00:01:12.746 --> 00:01:17.032
glass up here and it's going to start capturing data.

00:01:17.032 --> 00:01:18.031
So that's going.

00:01:18.032 --> 00:01:21.031
You can see down, it's already captured a little bit.

00:01:21.032 --> 00:01:23.032
I have a bunch of filters in place to kind of ignore

00:01:23.032 --> 00:01:24.032
some of the normal system traffic.

00:01:24.032 --> 00:01:25.032
(Aaron) Excellent.

00:01:25.032 --> 00:01:30.031
(Tyler) So then I'm going to minimize this, and now we're going to run TrickBot.

00:01:30.032 --> 00:01:35.032
Now the thing to watch is, I'm going to kind of pull Process Explorer over here,

00:01:35.032 --> 00:01:38.031
watch Process Explorer because as soon as we launch it,

00:01:38.032 --> 00:01:40.031
it's going to start doing things.

00:01:40.032 --> 00:01:42.032
And while Process Monitor is recording stuff,

00:01:42.032 --> 00:01:44.032
Regshot will be able to do our comparison,

00:01:44.032 --> 00:01:48.031
this will at least give us an idea of what it's doing.

00:01:48.032 --> 00:01:50.031
So I'm going to launch it.

00:01:50.032 --> 00:01:52.032
So there it kind of started up,

00:01:52.032 --> 00:01:55.131
and you can see that the CPU is kind of spiking for that process,

00:01:55.131 --> 00:01:58.031
or it was, and so it's definitely doing something.

00:01:58.032 --> 00:02:00.032
(Aaron) And it's not normally,

00:02:00.032 --> 00:02:03.032
in a normal infection it's not going to be called TrickBot.

00:02:03.032 --> 00:02:04.032
That'd be too easy.

00:02:04.032 --> 00:02:05.032
(Tyler) No.

00:02:05.032 --> 00:02:06.850
It's going to be called something that kind of looks

00:02:06.850 --> 00:02:09.032
benign or something like that.

00:02:09.032 --> 00:02:12.032
But TrickBot is kind of doing its thing.

00:02:12.032 --> 00:02:16.032
Probably in the background it's already set up some of its persistence.

00:02:16.032 --> 00:02:18.782
And what we'll see here in probably about a minute or

00:02:18.782 --> 00:02:22.032
two is that TrickBot is going to,

00:02:22.032 --> 00:02:24.031
a second version of TrickBot is going to get launched,

00:02:24.032 --> 00:02:26.031
and then this TrickBot will go away.

00:02:26.032 --> 00:02:29.032
And it's here you see that TrickBot started back up.

00:02:29.032 --> 00:02:31.032
The other one shut back down.

00:02:31.032 --> 00:02:35.032
So now it kind of got, you know, changed around a little bit.

00:02:35.032 --> 00:02:37.031
It's probably running from a different place.

00:02:37.032 --> 00:02:41.143
And you can even see in the description and the company name of

00:02:41.143 --> 00:02:44.032
TrickBot that's on there are kind of these random words,

00:02:44.032 --> 00:02:49.031
and malware authors will put that in there to kind of make it look real.

00:02:49.032 --> 00:02:51.031
(Aaron) Yeah, so when I booted that up in _____,

00:02:51.032 --> 00:02:55.031
I saw the company name there, the Y1000 LogiGear,

00:02:55.032 --> 00:02:56.031
and I saw the description.

00:02:56.032 --> 00:02:58.032
I also saw a version number.

00:02:58.032 --> 00:03:00.032
It was like 3.3 .4 or something like that.

00:03:00.032 --> 00:03:02.031
(Tyler) Yeah, that's probably just some random one.

00:03:02.032 --> 00:03:04.032
Just some random version number.

00:03:04.032 --> 00:03:06.281
(Aaron) I thought that'd be too nice of them to put the software to

00:03:06.281 --> 00:03:10.031
finalize the whole version number in there for us.

00:03:10.032 --> 00:03:14.031
(Tyler) So, what ended up happening, if you're watching,

00:03:14.032 --> 00:03:21.032
TrickBot kind of launched svchost.exe, and svchost is a normal Windows program,

00:03:21.032 --> 00:03:22.031
and then it kind of killed that.

00:03:22.032 --> 00:03:24.031
If we wait a little bit longer,

00:03:24.032 --> 00:03:26.031
we're going to see svchost kind of start up again,

00:03:26.032 --> 00:03:31.032
and that's kind of the main malware process at that point.

00:03:31.032 --> 00:03:34.317
What's going on here is that TrickBot is using a

00:03:34.317 --> 00:03:36.031
technique called process hollowing,

00:03:36.032 --> 00:03:39.809
and essentially what that is is TrickBot will start up

00:03:39.809 --> 00:03:44.032
a legitimate program like svchost, which is a normal Windows program,

00:03:44.032 --> 00:03:47.032
but it'll start it up in what's called suspended mode.

00:03:47.032 --> 00:03:49.032
In other words, it loads everything into memory,

00:03:49.032 --> 00:03:52.032
but then it doesn't allow it to execute.

00:03:52.032 --> 00:03:55.031
And once all that legitimate program gets loaded up into memory,

00:03:55.032 --> 00:03:59.031
it then copies all of the malicious code into that process in memory.

00:03:59.032 --> 00:04:01.782
It kind of hollows it out and throws in the malicious

00:04:01.782 --> 00:04:05.032
code and then tells the process, okay, now you can start executing.

00:04:05.032 --> 00:04:08.365
(Aaron) Because that memory location has been deemed

00:04:08.365 --> 00:04:10.698
allowed to execute within the Windows OS,

00:04:10.698 --> 00:04:11.032
right?

00:04:11.032 --> 00:04:13.032
And so if you then place the executable code in there,

00:04:13.032 --> 00:04:14.031
it'll run under that context?

00:04:14.032 --> 00:04:16.031
(Tyler) Exactly.

00:04:16.031 --> 00:04:21.031
And, so we can see that svchost has started running again.

00:04:21.031 --> 00:04:25.032
Not only that, all of our tools, just looking at the process list,

00:04:25.032 --> 00:04:26.031
you see svchost running here.

00:04:26.032 --> 00:04:28.032
You don't see TrickBot.

00:04:28.032 --> 00:04:30.032
So even though this host, I can guarantee you this host,

00:04:30.032 --> 00:04:33.031
or this process is a malicious process in memory,

00:04:33.032 --> 00:04:35.732
if I were just coming there and just using,

00:04:35.732 --> 00:04:39.032
like Task Manager to see what's there, I would see svchost.

00:04:39.032 --> 00:04:39.213
Additionally,

00:04:39.213 --> 00:04:42.365
one of the things that we can do really fast is we can do

00:04:42.365 --> 00:04:44.031
something called Verify Image Signatures.

00:04:44.032 --> 00:04:48.698
So what this means is Process Explorer is going to go through and it's going

00:04:48.698 --> 00:04:51.032
to verify all the code signatures on all the processes.

00:04:51.032 --> 00:04:54.032
Watch what happens when we do that.

00:04:54.032 --> 00:04:59.032
This svchost that we know is malicious is verified as Microsoft.

00:04:59.032 --> 00:05:02.032
And the reason that is is because you can't do,

00:05:02.032 --> 00:05:04.031
you can't verify a code signature of something in memory,

00:05:04.032 --> 00:05:05.031
because as soon as it gets put into memory,

00:05:05.032 --> 00:05:07.031
it changes all over the place.

00:05:07.032 --> 00:05:09.031
So, tools like Process Explorer,

00:05:09.032 --> 00:05:14.032
when they verify code signatures they have to go back to the file on disk.

00:05:14.032 --> 00:05:17.031
And just by looking at this process, it's pointing back to svchost,

00:05:17.032 --> 00:05:20.032
svchost it verifies.
