WEBVTT

00:00:00.250 --> 00:00:03.250
So we know where the TrickBot is, right?

00:00:03.250 --> 00:00:05.250
We know what it did so far is it copy itself over,

00:00:05.250 --> 00:00:08.750
but remember, we saw it kind of die and then re-execute,

00:00:08.750 --> 00:00:09.250
right?

00:00:09.250 --> 00:00:10.250
So how is it doing that?

00:00:10.250 --> 00:00:12.250
We want to figure that out.

00:00:12.250 --> 00:00:15.250
And we did get a hint of that.

00:00:15.250 --> 00:00:17.250
Remember we see,

00:00:17.250 --> 00:00:22.250
in Regshot we see the files added of this new task called Speed lan library.

00:00:22.250 --> 00:00:26.250
So it looks like maybe it was creating a scheduled task for this.

00:00:26.250 --> 00:00:28.250
(Aaron) Right, is taskeng.exe,

00:00:28.250 --> 00:00:32.250
is that the executable associated with scheduled task execution?

00:00:32.250 --> 00:00:34.250
(Tyler) Yes, it is, actually.

00:00:34.250 --> 00:00:38.250
So that's actually a really good way, you know, you're right.

00:00:38.250 --> 00:00:42.125
I mean, the fact that taskeng was running and it was accessing this,

00:00:42.125 --> 00:00:45.536
our TrickBot module definitely also leads to the fact that

00:00:45.536 --> 00:00:47.250
we're dealing with a scheduled task.

00:00:47.250 --> 00:00:48.250
(Aaron) Got it.

00:00:48.250 --> 00:00:50.250
(Tyler) And in fact, if we would go up in our Regshot output,

00:00:50.250 --> 00:00:53.250
kind of in the middle here of the values added,

00:00:53.250 --> 00:00:57.250
you can see where these tasks were created called Speed lan library.

00:00:57.250 --> 00:00:58.250
I'm going to be thorough.

00:00:58.250 --> 00:01:02.250
I'm going to go in here and I'm going to launch the Task Manager.

00:01:02.250 --> 00:01:05.250
I'm going to go to the Task Scheduler.

00:01:05.250 --> 00:01:07.250
(Aaron) Yeah, make sure it's still there.

00:01:07.250 --> 00:01:11.250
(Tyler) Make sure it's still there and see really what the settings for it are.

00:01:11.250 --> 00:01:13.250
(Aaron) Yeah, what's the triggers and what's it trying to do.

00:01:13.250 --> 00:01:14.250
(Tyler) Exactly.

00:01:14.250 --> 00:01:19.250
So, I'm just going to go down here and click on Task Scheduler Library.

00:01:19.250 --> 00:01:21.250
It's a little bit slow.

00:01:21.250 --> 00:01:23.250
And here we have, here it is, Speed lan library.

00:01:23.250 --> 00:01:27.250
You can see they even put in a description of New speed lan library,

00:01:27.250 --> 00:01:30.250
so if I was some random administrator or user,

00:01:30.250 --> 00:01:31.250
I would just see, oh well, this looks legitimate.

00:01:31.250 --> 00:01:33.250
(Aaron) Yeah, it sounds totally legit, right.

00:01:33.250 --> 00:01:35.250
(Tyler) The triggers, it starts at system startup,

00:01:35.250 --> 00:01:37.250
so now we know how it's remaining persistent.

00:01:37.250 --> 00:01:41.250
When the system reboots, this is how TrickBot's going to start it back up.

00:01:41.250 --> 00:01:46.250
And then you can see that it actually will restart itself every 11 minutes.

00:01:46.250 --> 00:01:49.250
So if we do get on here and we're smart enough to figure out,

00:01:49.250 --> 00:01:50.250
oh, well, here's TrickBot.

00:01:50.250 --> 00:01:52.250
I'm just going to kill the process,

00:01:52.250 --> 00:01:54.250
11 minutes later it's going to start up again.

00:01:54.250 --> 00:01:55.250
(Aaron) Got it.

00:01:55.250 --> 00:01:57.250
Is this the only persistence that we've seen so far?

00:01:57.250 --> 00:01:59.250
(Tyler) So far, yeah, this is the only persistence.

00:01:59.250 --> 00:02:00.150
And we can,

00:02:00.150 --> 00:02:05.250
here we verified that what it's doing is it's launching our TrickBot executable.

00:02:05.250 --> 00:02:10.250
And in fact, in looking at this, we're not seeing any other persistence.

00:02:10.250 --> 00:02:11.250
(Aaron) Not at all.

00:02:11.250 --> 00:02:13.250
(Tyler) But we can verify that.

00:02:13.250 --> 00:02:15.250
We're going to run one more tool.

00:02:15.250 --> 00:02:19.250
I'm just going to close Process Monitor.

00:02:19.250 --> 00:02:20.250
(Aaron) Before you close Process Explorer,

00:02:20.250 --> 00:02:23.250
I was curious if we can, because the svchost at the bottom,

00:02:23.250 --> 00:02:25.000
that's the malicious one that's hollowed out,

00:02:25.000 --> 00:02:25.250
right?

00:02:25.250 --> 00:02:26.250
(Tyler) Yes, yes.

00:02:26.250 --> 00:02:29.250
(Aaron) Can we hit that and look at its TCP activity?

00:02:29.250 --> 00:02:30.250
Is that an option?

00:02:30.250 --> 00:02:31.250
(Tyler) Oh yeah, absolutely.

00:02:31.250 --> 00:02:35.250
So I'm just going to click up here on TCP.

00:02:35.250 --> 00:02:37.250
One thing that I always recommend is turn off resolve addresses

00:02:37.250 --> 00:02:38.250
because it's going to make it a little faster,

00:02:38.250 --> 00:02:42.250
and if the attacker is watching that, they're not going to do anything.

00:02:42.250 --> 00:02:45.250
But you can see, oh, there it went, really fast.

00:02:45.250 --> 00:02:48.250
It's sending out something.

00:02:48.250 --> 00:02:52.250
And you can see here, notice the port that it's sending it to is port 447.

00:02:52.250 --> 00:02:53.250
We're going to see that later.

00:02:53.250 --> 00:02:54.250
(Aaron) Okay, great.

00:02:54.250 --> 00:02:55.250
(Tyler) But yeah,

00:02:55.250 --> 00:02:56.917
and so it's definitely going out and it's definitely

00:02:56.917 --> 00:02:58.250
trying to connect to the network.

00:02:58.250 --> 00:03:02.250
Right now it looks like it's not able to because the state is SYN_SENT.

00:03:02.250 --> 00:03:03.250
It's not making a complete connection.

00:03:03.250 --> 00:03:05.250
(Aaron) Right, it's not able to reset, yeah.

00:03:05.250 --> 00:03:07.250
(Tyler) Right, it's not able to do that three-way handshake.

00:03:07.250 --> 00:03:09.250
What that means is that this version of TrickBot,

00:03:09.250 --> 00:03:11.250
its command control channels have probably been shut down or moved.

00:03:11.250 --> 00:03:12.250
(Aaron) I see, okay.

00:03:12.250 --> 00:03:14.250
But that's okay because you know what,

00:03:14.250 --> 00:03:17.125
I infected my system before and we have a bunch of network

00:03:17.125 --> 00:03:18.250
traffic that we're going to look at.

00:03:18.250 --> 00:03:19.250
(Aaron) Awesome.

00:03:19.250 --> 00:03:22.250
(Tyler) But yeah, let's jump back to persistence really fast.

00:03:22.250 --> 00:03:24.250
There's one more tool we're going to run.

00:03:24.250 --> 00:03:27.250
And we talked about this tool in our previous Play by Play,

00:03:27.250 --> 00:03:31.250
but this tool is called Autoruns.

00:03:31.250 --> 00:03:33.250
Let me get to it.

00:03:33.250 --> 00:03:34.250
(Aaron) Good old sysinternals.

00:03:34.250 --> 00:03:38.250
(Tyler) Yeah, sysinternals, Mark Russinovich makes some pretty amazing tools.

00:03:38.250 --> 00:03:39.250
(Aaron) Absolutely.

00:03:39.250 --> 00:03:42.250
Is there a reason you're using the 64-bit as opposed to the x86?

00:03:42.250 --> 00:03:43.250
(Tyler) Because I'm on a 64-bit system.

00:03:43.250 --> 00:03:47.250
I don't think that there would be any difference, but why take the chance?

00:03:47.250 --> 00:03:48.250
Immediately when it starts up,

00:03:48.250 --> 00:03:51.250
it's going to start going through and doing things.

00:03:51.250 --> 00:03:53.250
And you can see down here that, hey,

00:03:53.250 --> 00:03:58.250
it found this Not verified interesting thing here that's our malware.

00:03:58.250 --> 00:04:01.250
In fact, if we wanted to, let me cancel this.

00:04:01.250 --> 00:04:02.250
I'm going to change the options a little bit.

00:04:02.250 --> 00:04:04.250
I'm going to tell it to also check against VirusTotal.

00:04:04.250 --> 00:04:06.250
So it's going to be uploading the hashes.

00:04:06.250 --> 00:04:08.250
(Aaron) Yeah, and another benefit of having it connected to the internet.

00:04:08.250 --> 00:04:09.250
(Tyler) Right, exactly.

00:04:09.250 --> 00:04:12.250
And so this is going to take a little bit.

00:04:12.250 --> 00:04:14.250
So it's going to go through and check all the hashes,

00:04:14.250 --> 00:04:15.750
and then it'll tell us how many places on

00:04:15.750 --> 00:04:18.250
VirusTotal have actually detected this.

00:04:18.250 --> 00:04:21.250
And eventually our malicious process down here, oh, right away.

00:04:21.250 --> 00:04:27.250
41 out of 70 systems are antiviruses on VirusTotal detected this, yeah.

00:04:27.250 --> 00:04:29.250
(Aaron) That's a successful detection of TrickBot there?

00:04:29.250 --> 00:04:33.250
(Tyler) Yeah, and if we would sit here long enough and let it go long enough,

00:04:33.250 --> 00:04:35.250
we would see that, at least with Autoruns,

00:04:35.250 --> 00:04:38.250
it wasn't detecting any other persistence mechanism.

00:04:38.250 --> 00:04:39.250
This is the only one.

00:04:39.250 --> 00:04:40.250
(Aaron) Right.

00:04:40.250 --> 00:04:41.250
I wanted to take a second,

00:04:41.250 --> 00:04:45.796
and I think we skipped over how easily this malware

00:04:45.796 --> 00:04:49.250
ran on our VM that we had set up, right?

00:04:49.250 --> 00:04:52.250
And so in the malware analysis lab setting up Play by Play,

00:04:52.250 --> 00:04:53.450
we talked about all the different things we can do to

00:04:53.450 --> 00:04:57.250
make it look like a real boy so it'll, the malware will actually execute.

00:04:57.250 --> 00:04:59.250
And it seemed to execute no problem.

00:04:59.250 --> 00:05:02.250
And including using Process Explorer.

00:05:02.250 --> 00:05:04.107
So it wasn't looking for Process Explorer because we didn't change the name,

00:05:04.107 --> 00:05:04.250
right?

00:05:04.250 --> 00:05:05.250
(Tyler) Right.

00:05:05.250 --> 00:05:08.250
Or if it does, it doesn't care.

00:05:08.250 --> 00:05:13.250
So yeah, TrickBot is one of these where it has a lot of protections in place.

00:05:13.250 --> 00:05:15.393
That could be the reason why it just doesn't care about

00:05:15.393 --> 00:05:16.250
Process Monitor or anything like that.

00:05:16.250 --> 00:05:17.250
(Aaron) Oh, it's advanced enough.

00:05:17.250 --> 00:05:20.250
It's like, go ahead and monitor my process.

00:05:20.250 --> 00:05:22.250
That's fine.

00:05:22.250 --> 00:05:25.250
(Tyler) Right, exactly.
