WEBVTT

00:00:01.000 --> 00:00:03.125
(Aaron) We're going to get into actually detonating the

00:00:03.125 --> 00:00:04.000
TrickBot malware and see what's going on,

00:00:04.000 --> 00:00:05.999
but first, let's set the scene.

00:00:06.000 --> 00:00:07.999
So, you have a malware sample.

00:00:08.000 --> 00:00:08.999
Where'd you get it from?

00:00:09.000 --> 00:00:12.000
(Tyler) There are a lot of places where you can get malware from online,

00:00:12.000 --> 00:00:15.999
and one of the places that I found out is one of the best places to get it,

00:00:16.000 --> 00:00:20.000
especially for new malware samples, is malware-traffic- analysis.net.

00:00:20.000 --> 00:00:23.999
This is a website run by a man named Brad Duncan,

00:00:24.000 --> 00:00:24.999
and he will go through,

00:00:25.000 --> 00:00:27.999
he will get new samples of malware and just kind of analyze it.

00:00:28.000 --> 00:00:32.000
And the best part about it is anything that he analyzes, he releases.

00:00:32.000 --> 00:00:35.000
Any of the network traffic that he captures, he'll release as well.

00:00:35.000 --> 00:00:37.000
So you can just go to the site, see how he analyzed it,

00:00:37.000 --> 00:00:39.375
and then download new samples and see if your

00:00:39.375 --> 00:00:44.799
analysis matches up to what he found, to see if the sample acts differently,

00:00:44.799 --> 00:00:45.999
and so on.

00:00:46.000 --> 00:00:47.000
(Aaron) Just for reference,

00:00:47.000 --> 00:00:50.800
I've looked around using Google and trying to identify

00:00:50.800 --> 00:00:52.000
different places you can get malware.

00:00:52.000 --> 00:00:54.000
And first, that's kind of a weird Google to do.

00:00:54.000 --> 00:00:55.000
Where can I get malware?

00:00:55.000 --> 00:00:58.625
And it's like, uh, your email, sites you shouldn't be visiting,

00:00:58.625 --> 00:00:59.000
things like that.

00:00:59.000 --> 00:01:00.000
(Tyler) Your parents.

00:01:00.000 --> 00:01:01.999
(Aaron) Your parents.

00:01:02.000 --> 00:01:04.999
So it was really difficult to find a good source,

00:01:05.000 --> 00:01:07.000
so I'm really glad that you gave this to me,

00:01:07.000 --> 00:01:09.999
and I hope this helps the people watching this as well.

00:01:10.000 --> 00:01:11.000
So, awesome.

00:01:11.000 --> 00:01:12.000
So that's, we're getting that sample.

00:01:12.000 --> 00:01:15.999
This is the sample you're using, correct, is the sample from this site?

00:01:16.000 --> 00:01:17.000
(Tyler) Yes, I believe so, yeah.

00:01:17.000 --> 00:01:19.000
(Aaron) And then what else are we doing?

00:01:19.000 --> 00:01:21.750
Because we talked about different options when we set

00:01:21.750 --> 00:01:24.000
up our malware analysis sandbox, different snapshots we might use.

00:01:24.000 --> 00:01:26.000
We know we're using Windows 7 OS.

00:01:26.000 --> 00:01:27.000
What's the rest of the setup?

00:01:27.000 --> 00:01:27.600
(Tyler) So,

00:01:27.600 --> 00:01:32.000
the way that I've set up my sandbox that we're going to analyze this in is

00:01:32.000 --> 00:01:35.750
normally I would just have it set up networking-wise in host-only networking

00:01:35.750 --> 00:01:40.000
mode so that the malware can't get out onto the internet.

00:01:40.000 --> 00:01:42.999
And what I would do is I would kind of run it once,

00:01:43.000 --> 00:01:45.750
have something like FakeNet running in the background to kind

00:01:45.750 --> 00:01:48.000
of capture the malware's network traffic,

00:01:48.000 --> 00:01:51.000
and then kind of see where it went and see if I wanted to open it up from there.

00:01:51.000 --> 00:01:51.333
However,

00:01:51.333 --> 00:01:55.500
because TrickBot is the way that it is and it goes out and it

00:01:55.500 --> 00:01:58.999
downloads modules and it could take a little bit to run,

00:01:59.000 --> 00:02:04.000
I just went ahead and set up my sandbox in NAT mode.

00:02:04.000 --> 00:02:06.000
So it is going to be going out to the internet.

00:02:06.000 --> 00:02:11.999
I'm connected to an anonymous internet connection through my cell phone company,

00:02:12.000 --> 00:02:15.333
so that if something happens I can immediately shut that off and

00:02:15.333 --> 00:02:18.000
then my computer's no longer on the internet.

00:02:18.000 --> 00:02:21.000
But this is going to allow TrickBot to go out,

00:02:21.000 --> 00:02:24.000
grab all the information that it needs to,

00:02:24.000 --> 00:02:26.000
grab all the files that it needs to.

00:02:26.000 --> 00:02:27.000
(Aaron) Got it.

00:02:27.000 --> 00:02:28.571
And you talked about being modularized and it takes some

00:02:28.571 --> 00:02:31.500
time to go and decide to download those modules and encrypt

00:02:31.500 --> 00:02:33.000
them and that kind of thing,

00:02:33.000 --> 00:02:36.999
so you needed to have time on the internet to be able to do that.

00:02:37.000 --> 00:02:38.999
And it allows us to monitor it as well, right?

00:02:39.000 --> 00:02:40.000
(Tyler) Right, right.

00:02:40.000 --> 00:02:43.600
(Aaron) And then network address translations happen internal to your machine,

00:02:43.600 --> 00:02:44.000
right?

00:02:44.000 --> 00:02:45.000
(Tyler) Right.

00:02:45.000 --> 00:02:48.000
(Aaron) So it's internal host to VM network address translation.

00:02:48.000 --> 00:02:49.000
(Tyler) Yes, yeah.

00:02:49.000 --> 00:02:51.750
And so the way that we would go through and capture the

00:02:51.750 --> 00:02:55.250
network traffic in this case is have some type of network

00:02:55.250 --> 00:02:59.000
sniffer running either on our VM here, our guest right here,

00:02:59.000 --> 00:03:01.000
or even in the host OS.

00:03:01.000 --> 00:03:04.666
Just to understand that if you're in NAT mode and you're in the host

00:03:04.666 --> 00:03:07.000
OS and you're capturing network traffic there,

00:03:07.000 --> 00:03:09.000
you're going to be seeing traffic not only from your guest,

00:03:09.000 --> 00:03:11.999
but also your host, so you're going to have to differentiate between the two,

00:03:12.000 --> 00:03:13.500
and they're both going to be looking like they're

00:03:13.500 --> 00:03:23.000
coming from the same IP address, so you definitely want to be careful there.
