WEBVTT

00:00:01.000 --> 00:00:03.999
(Aaron) We talked about a bunch of things about TrickBot,

00:00:04.000 --> 00:00:06.000
where it came from, what it is, why it's dangerous.

00:00:06.000 --> 00:00:08.333
We detonated it in a live environment,

00:00:08.333 --> 00:00:12.000
we definitely tricked TrickBot into thinking it was on a real system,

00:00:12.000 --> 00:00:13.500
and we were able to leverage that behavior,

00:00:13.500 --> 00:00:15.666
it actually really performed really well for us,

00:00:15.666 --> 00:00:18.999
kind of better than it does in other live demos.

00:00:19.000 --> 00:00:20.999
As far as live demos goes, that was pretty good.

00:00:21.000 --> 00:00:24.666
And then we also extracted from that behavior a ton of

00:00:24.666 --> 00:00:27.666
indicators on the host and indicators on the network that can

00:00:27.666 --> 00:00:29.999
be used to identify a new environment.

00:00:30.000 --> 00:00:33.500
(Tyler) The security industry has definitely shifted from thinking that,

00:00:33.500 --> 00:00:36.000
not necessarily away from prevention,

00:00:36.000 --> 00:00:38.999
but understanding that prevention is only one piece of it,

00:00:39.000 --> 00:00:41.250
you kind of have to move into the mindset that

00:00:41.250 --> 00:00:43.000
eventually you are going to get compromised.

00:00:43.000 --> 00:00:44.199
And so with TrickBot,

00:00:44.199 --> 00:00:47.199
eventually somebody is going to click on that link or

00:00:47.199 --> 00:00:48.999
download that document and run it.

00:00:49.000 --> 00:00:50.999
Eventually, TrickBot will get installed.

00:00:51.000 --> 00:00:52.000
(Aaron) Right.

00:00:52.000 --> 00:00:53.999
(Tyler) So, you definitely want to be looking out for it.

00:00:54.000 --> 00:00:54.400
You know,

00:00:54.400 --> 00:00:58.285
we looked at a number of different indicators on both the host

00:00:58.285 --> 00:01:00.999
and the network on how you can detect it.

00:01:01.000 --> 00:01:04.000
You know, it throws things into very specific directories.

00:01:04.000 --> 00:01:08.250
We talked about the grabber_temp file that it kind of leaves

00:01:08.250 --> 00:01:11.000
as an artifact when a specific plugin runs.

00:01:11.000 --> 00:01:11.999
(Aaron) Yeah, absolutely.

00:01:12.000 --> 00:01:13.333
(Tyler) With all these,

00:01:13.333 --> 00:01:15.888
if you have the ability to search across your host for something like

00:01:15.888 --> 00:01:19.000
that or write some type of signature around that,

00:01:19.000 --> 00:01:21.000
then that's going to help detect it.

00:01:21.000 --> 00:01:23.000
You know, when you were looking at the network piece,

00:01:23.000 --> 00:01:25.363
the JA3 signatures that you developed, well,

00:01:25.363 --> 00:01:28.999
one of them was unique, the server one was not.

00:01:29.000 --> 00:01:30.000
(Aaron) Right.

00:01:30.000 --> 00:01:32.000
(Tyler) And it was already known to be related to TrickBot.

00:01:32.000 --> 00:01:34.000
So we can definitely look at that,

00:01:34.000 --> 00:01:37.454
look for like the user agent that we saw and the server name,

00:01:37.454 --> 00:01:39.999
and just all those types of things.

00:01:40.000 --> 00:01:43.899
You know, we kind of take those steps to do the analysis on the malware,

00:01:43.899 --> 00:01:44.799
like we did,

00:01:44.799 --> 00:01:47.000
and get these indicators and then search for them within your network.

00:01:47.000 --> 00:01:47.999
(Aaron) Yeah, absolutely.

00:01:48.000 --> 00:01:52.500
And hopefully the users gain some of the capability and really benefited from

00:01:52.500 --> 00:01:56.000
the wealth of knowledge and capability you bring to the table.

00:01:56.000 --> 00:01:57.555
So, thank you so much for that,

00:01:57.555 --> 00:02:00.000
really thankful to have you not only respond in the field,

00:02:00.000 --> 00:02:00.999
which we are all lucky to have,

00:02:01.000 --> 00:02:03.857
but also to have you here and take the time like you

00:02:03.857 --> 00:02:06.000
have experienced with these infections,

00:02:06.000 --> 00:02:09.615
you have the experience to be able to do this analysis in a safe way,

00:02:09.615 --> 00:02:12.384
kind of not like me where I detonated it on the plane on my live

00:02:12.384 --> 00:02:15.000
box and then have to like cover that real quick.

00:02:15.000 --> 00:02:17.000
And then really for the users,

00:02:17.000 --> 00:02:20.142
we're going to make available all of the indicators that

00:02:20.142 --> 00:02:20.999
we've identified in the demo content.

00:02:21.000 --> 00:02:23.799
We have some Sigma signatures that we're going to develop based on some

00:02:23.799 --> 00:02:27.000
Sysmon activity that we'll upload to the project as well.

00:02:27.000 --> 00:02:29.999
And we're just really happy to hopefully have you back again soon.

00:02:30.000 --> 00:02:31.000
(Tyler) Oh, yeah.

00:02:31.000 --> 00:02:31.999
(Aaron) I mean, I guess it's like a good and a bad thing.

00:02:32.000 --> 00:02:32.666
If you're back soon,

00:02:32.666 --> 00:02:36.363
it means another really bad malware outbreak has happened and we

00:02:36.363 --> 00:02:38.000
need to figure out what's going on with it.

00:02:38.000 --> 00:02:39.000
(Tyler) Yeah, but you know what, this is the fun stuff.

00:02:39.000 --> 00:02:42.999
Doing the analysis, this is what I find enjoyable and I think a lot of people do.

00:02:43.000 --> 00:02:43.857
And so,

00:02:43.857 --> 00:02:47.333
there're all these different techniques and tools that we can use

00:02:47.333 --> 00:02:50.499
to help others who don't either have these skills or have the

00:02:50.499 --> 00:02:51.999
time to go and do this on their own.

00:02:52.000 --> 00:02:56.000
So absolutely, I'm looking forward to anything else that we analyze.

00:02:56.000 --> 00:02:56.399
(Aaron) Excellent.

00:02:56.399 --> 00:02:57.999
Well, I can't wait for the next one,

00:02:58.000 --> 00:03:01.000
and thanks for joining us for Malware Analysis and

00:03:01.000 --> 00:03:09.000
Detection with our focus on TrickBot, at Pluralsight.
