WEBVTT

00:00:00.424 --> 00:00:04.423
(Aaron) Yeah, we can assume that, yeah.

00:00:04.424 --> 00:00:05.424
Good to go verify.

00:00:05.424 --> 00:00:05.924
(Tyler) So,

00:00:05.924 --> 00:00:08.787
I'm going to jump over then to Process Monitor so we

00:00:08.787 --> 00:00:10.424
can see exactly what TrickBot did.

00:00:10.424 --> 00:00:13.424
So I'm just going to minimize Regshot here.

00:00:13.424 --> 00:00:15.423
And the way that I'm going to do that is I'm going to use

00:00:15.424 --> 00:00:18.424
Process Monitor's filtering capability.

00:00:18.424 --> 00:00:21.423
So I'm going to first filter on process name,

00:00:21.424 --> 00:00:24.424
and we'll only look at our original malware,

00:00:24.424 --> 00:00:26.424
the TrickBot.exe.

00:00:26.424 --> 00:00:27.423
So I'm going to add that filter.

00:00:27.424 --> 00:00:31.423
And then, so if I do that and click Apply,

00:00:31.424 --> 00:00:33.424
it still gives us 1300 events that we would have to look through.

00:00:33.424 --> 00:00:35.423
I don't want to look through 1300 events individually.

00:00:35.424 --> 00:00:35.995
(Aaron) Sure.

00:00:35.995 --> 00:00:38.424
That's better than 150, 000, but still.

00:00:38.424 --> 00:00:38.924
(Tyler) Yeah.

00:00:38.924 --> 00:00:41.423
But still, way too many that we're going to go through.

00:00:41.424 --> 00:00:42.424
(Aaron) Not how you want to spend your Saturday?

00:00:42.424 --> 00:00:43.424
(Tyler) Right, exactly.

00:00:43.424 --> 00:00:46.424
So what I'm going to do is then I'm going to filter by operation,

00:00:46.424 --> 00:00:51.424
and operation are basically all the things that Process Monitor recorded.

00:00:51.424 --> 00:00:53.423
So I'm going to focus on two different ones.

00:00:53.424 --> 00:00:58.424
I'm going to focus on WriteFile, so anytime this process wrote to a file.

00:00:58.424 --> 00:01:00.424
(Aaron) Correct, and that's what we looked at in Regshot,

00:01:00.424 --> 00:01:01.424
so now we're trying to attribute what did that.

00:01:01.424 --> 00:01:03.423
(Tyler) Right, exactly.

00:01:03.424 --> 00:01:06.424
And then I'm also going to do RegSetValue,

00:01:06.424 --> 00:01:10.424
and so this is anytime that TrickBot modified anything in the registry.

00:01:10.424 --> 00:01:11.423
(Aaron) Okay, great.

00:01:11.424 --> 00:01:12.423
(Tyler) So I'm going to do that and click OK.

00:01:12.424 --> 00:01:15.424
And, it actually doesn't give us any events, which is kind of interesting.

00:01:15.424 --> 00:01:19.423
That means that either we're not looking at the right event

00:01:19.424 --> 00:01:23.674
or the right operation or TrickBot did something else in

00:01:23.674 --> 00:01:25.424
order to kind of get around that.

00:01:25.424 --> 00:01:26.423
(Aaron) That's interesting.

00:01:26.424 --> 00:01:30.224
(Tyler) So what I'm going to do then is I'm going to kind of add

00:01:30.224 --> 00:01:33.423
a new process that we're going to look at.

00:01:33.424 --> 00:01:36.424
So, we know that TrickBot has ran svchost.

00:01:36.424 --> 00:01:40.424
However, there's a large number of svchosts on the system,

00:01:40.424 --> 00:01:41.424
so I'm going to hold off on that.

00:01:41.424 --> 00:01:45.924
Then I'm going to go down to this other one that we saw that was created,

00:01:45.924 --> 00:01:46.424
the ttic.

00:01:46.424 --> 00:01:47.424
(Aaron) That's one of the files that was created.

00:01:47.424 --> 00:01:48.090
(Tyler) Right.

00:01:48.090 --> 00:01:48.423
Right.

00:01:48.424 --> 00:01:50.424
And we're going to see if that did anything.

00:01:50.424 --> 00:01:54.424
And we're still not seeing anything, so, and this is how malware analysis works.

00:01:54.424 --> 00:01:59.049
You start by looking at something and then you kind of iteratively go

00:01:59.049 --> 00:02:01.424
through and just do more and more to see what you can find.

00:02:01.424 --> 00:02:03.924
(Aaron) Make educated guesses about what direction you're

00:02:03.924 --> 00:02:07.423
going to take to identify what's going on.

00:02:07.424 --> 00:02:12.423
(Tyler) So what I'm going to do, let's start looking at some other operations.

00:02:12.424 --> 00:02:16.924
One that is often used is this one called SetDispositionInformationFile,

00:02:16.924 --> 00:02:23.424
and this is often used, so if a file gets renamed or if a file gets deleted,

00:02:23.424 --> 00:02:24.423
this is the operation that's recorded.

00:02:24.424 --> 00:02:25.424
(Aaron) Okay.

00:02:25.424 --> 00:02:26.423
(Tyler) We're still not seeing anything,

00:02:26.424 --> 00:02:29.424
so we're going to take this from a different approach.

00:02:29.424 --> 00:02:32.424
We're not finding the process that's doing this.

00:02:32.424 --> 00:02:34.424
We're not finding the operation that's doing that.

00:02:34.424 --> 00:02:38.424
But we still want to at least, you know, let's have a goal in mind.

00:02:38.424 --> 00:02:44.424
So, our goal right now is going to be let's figure out who copied this tticmb,

00:02:44.424 --> 00:02:47.423
that file name over because we did see that in Regshot.

00:02:47.424 --> 00:02:49.423
(Aaron) And by who, we mean which process, right?

00:02:49.424 --> 00:02:50.424
(Tyler) Which process, yes.

00:02:50.424 --> 00:02:53.424
So what I'm going to do is I'm just going to remove all the ones that we added,

00:02:53.424 --> 00:02:54.424
and then I'm going to filter on something different.

00:02:54.424 --> 00:02:59.424
I'm going to filter on Path ends with,

00:02:59.424 --> 00:03:02.824
and then I'm just going to quickly copy this

00:03:02.824 --> 00:03:09.424
executable file name here and add that in.

00:03:09.424 --> 00:03:11.423
And so now when I click OK,

00:03:11.424 --> 00:03:16.924
hopefully Process Monitor recorded some event and some process where this

00:03:16.924 --> 00:03:20.423
file was accessed or modified or touched in some way.

00:03:20.424 --> 00:03:22.424
(Aaron) Right, and this is process-independent now.

00:03:22.424 --> 00:03:23.423
We're looking across all processes.

00:03:23.424 --> 00:03:24.424
(Tyler) Right.

00:03:24.424 --> 00:03:26.424
And great, so we get a whole bunch.

00:03:26.424 --> 00:03:28.424
We have 130 events.

00:03:28.424 --> 00:03:31.757
And if we look to see who did that, it was svchost,

00:03:31.757 --> 00:03:34.424
at least initially, which is interesting.

00:03:34.424 --> 00:03:38.424
You remember svchost was the process that TrickBot hollows out.

00:03:38.424 --> 00:03:42.424
So probably what happened here is that TrickBot went in,

00:03:42.424 --> 00:03:44.424
it launched svchost, hollowed it out,

00:03:44.424 --> 00:03:49.423
and it didn't do anything malicious like copying files or moving files over

00:03:49.424 --> 00:03:52.424
until it was underneath svchost or acting as svchost.

00:03:52.424 --> 00:03:54.423
(Aaron) Which would be smart for the malware to do, right?

00:03:54.424 --> 00:03:55.424
(Tyler) Exactly, exactly.

00:03:55.424 --> 00:03:56.924
(Aaron) Whatever is the initial process name is not

00:03:56.924 --> 00:03:58.424
necessarily part of your configuration baseline.

00:03:58.424 --> 00:04:00.423
(Tyler) Right, exactly.

00:04:00.424 --> 00:04:05.424
And we can see here that it wrote the file a number of times,

00:04:05.424 --> 00:04:07.424
and in fact if we start looking through here,

00:04:07.424 --> 00:04:10.424
we can go to the very last write file,

00:04:10.424 --> 00:04:14.423
and we see that at the very end the last time svchost wrote this file,

00:04:14.424 --> 00:04:19.423
it wrote it at an offset of about 655k and then a length of 48k.

00:04:19.423 --> 00:04:20.424
So if we add those two together,

00:04:20.423 --> 00:04:27.624
that will actually match the the current file size,

00:04:27.624 --> 00:04:28.424
yeah.

00:04:28.424 --> 00:04:31.424
(Aaron) So that's a good verification is what we're seeing,

00:04:31.424 --> 00:04:32.424
that we're looking at the exact same file.

00:04:32.424 --> 00:04:33.423
(Tyler) Right, exactly.

00:04:33.424 --> 00:04:34.424
(Aaron) And we're caught up to current events.

00:04:34.424 --> 00:04:35.424
(Tyler) Exactly.

00:04:35.424 --> 00:04:39.757
And we can see that there are some other processes which touched this one,

00:04:39.757 --> 00:04:43.424
this file; however, if you look really fast through these,

00:04:43.424 --> 00:04:47.424
the only one that wrote to it was svchost.

00:04:47.424 --> 00:04:50.423
So these could be other normal Windows processes that we're modifying,

00:04:50.424 --> 00:04:51.424
and it could be the malware.

00:04:51.424 --> 00:04:52.423
We don't know.

00:04:52.424 --> 00:04:56.424
But the only one we know for sure that copied that file over was this svchost.

00:04:56.424 --> 00:04:59.424
(Aaron) Got it.
