WEBVTT

00:00:01.000 --> 00:00:02.545
(Aaron) We've detonated some malware and we've watched

00:00:02.545 --> 00:00:03.999
it do its thing for a little bit.

00:00:04.000 --> 00:00:06.000
It downloaded some modules, just like we talked about,

00:00:06.000 --> 00:00:08.900
and now we're going to kind of jump back into a previously infected,

00:00:08.900 --> 00:00:11.000
before we did this Play by Play,

00:00:11.000 --> 00:00:13.666
a previously infected box that's had some time on the

00:00:13.666 --> 00:00:15.555
network because we've seen it take 15 minutes,

00:00:15.555 --> 00:00:18.750
30 minutes, weeks to download everything and accomplish its missions,

00:00:18.750 --> 00:00:19.000
right?

00:00:19.000 --> 00:00:22.999
(Tyler) Yeah, so what I did was, the same malware example we had just looked at,

00:00:23.000 --> 00:00:24.999
I had previously infected my system,

00:00:25.000 --> 00:00:29.100
let it run for an hour or two just to give it a long time

00:00:29.100 --> 00:00:31.000
to kind of download whatever it wanted.

00:00:31.000 --> 00:00:32.500
And we're going to go in,

00:00:32.500 --> 00:00:36.571
and we're actually going to now look at the files that it

00:00:36.571 --> 00:00:40.000
downloaded and learn how we can actually decrypt them.

00:00:40.000 --> 00:00:44.000
Because remember that when TrickBot downloads the plugins to the system,

00:00:44.000 --> 00:00:45.999
it encrypts them per system.

00:00:46.000 --> 00:00:47.999
So unless we get some data from this system,

00:00:48.000 --> 00:00:49.999
we're not going to be able to decrypt it.

00:00:50.000 --> 00:00:50.222
(Aaron) Right,

00:00:50.222 --> 00:00:53.500
and here's where we'll able to get some indicators out of those

00:00:53.500 --> 00:00:54.999
configurations that we can use for detection.

00:00:55.000 --> 00:00:56.000
(Tyler) Right, exactly.

00:00:56.000 --> 00:00:56.571
(Aaron) Awesome.

00:00:56.571 --> 00:00:57.999
Well, let's jump into that.

00:00:58.000 --> 00:00:59.000
(Tyler) Sure.

00:00:59.000 --> 00:00:59.200
So,

00:00:59.200 --> 00:01:01.363
the first thing that we're going to do is I'm just going to

00:01:01.363 --> 00:01:02.000
jump into the directory where TrickBot's at.

00:01:02.000 --> 00:01:03.000
(Aaron) John's directory.

00:01:03.000 --> 00:01:06.999
(Tyler) Yeah, John's AppData/Roaming directory.

00:01:07.000 --> 00:01:10.000
Remember speedLAN looks familiar.

00:01:10.000 --> 00:01:12.000
(Aaron) But, why have LAN when you can have speedLAN?

00:01:12.000 --> 00:01:13.000
(Tyler) Exactly.

00:01:13.000 --> 00:01:15.000
And then I'm going to jump into the data directory.

00:01:15.000 --> 00:01:17.000
Remember, the data directory is where all the plugins are.

00:01:17.000 --> 00:01:20.000
And so we're seeing five different plugins here,

00:01:20.000 --> 00:01:24.000
as well as the directories that contain some of their configuration files.

00:01:24.000 --> 00:01:26.999
And all these files within here, all of the DLL files,

00:01:27.000 --> 00:01:29.999
and these are actually DLL files, they're just encrypted,

00:01:30.000 --> 00:01:32.999
as well as the files that we'll see in the configuration directories,

00:01:32.999 --> 00:01:33.999
they're all encrypted.

00:01:34.000 --> 00:01:34.571
(Aaron) So they're encrypted,

00:01:34.571 --> 00:01:37.400
which is why they're just showing up as just file as opposed

00:01:37.400 --> 00:01:39.000
to showing up as a recognized DLL file.

00:01:39.000 --> 00:01:40.000
(Tyler) Right.

00:01:40.000 --> 00:01:43.000
Now, even if you can't decrypt them,

00:01:43.000 --> 00:01:47.000
you can still get a lot of information as to what TrickBot was doing.

00:01:47.000 --> 00:01:50.000
Because each of these plugin names, they're always named the same.

00:01:50.000 --> 00:01:53.000
And they have been researched pretty well.

00:01:53.000 --> 00:01:55.999
And so you can just look at the names and tell what it was doing.

00:01:56.000 --> 00:01:58.999
So for example, this injectDll64,

00:01:59.000 --> 00:02:01.999
this is one of the modules that grabs banking activity.

00:02:02.000 --> 00:02:05.999
So its sole purpose is to kind of inject itself into browsers,

00:02:06.000 --> 00:02:08.000
and when you log into your banking website,

00:02:08.000 --> 00:02:09.000
to grab the credentials there, and you know,

00:02:09.000 --> 00:02:10.000
potentially some additional information.

00:02:10.000 --> 00:02:15.250
(Aaron) So that's modifying the web page on the client side with

00:02:15.250 --> 00:02:16.999
essentially a scraper for when you type in that information?

00:02:17.000 --> 00:02:18.000
(Tyler) Exactly.

00:02:18.000 --> 00:02:19.000
(Aaron) Got it.

00:02:19.000 --> 00:02:24.000
(Tyler) The networkDll64, this is the one that's usually downloaded initially.

00:02:24.000 --> 00:02:27.000
Its sole purpose is to go and grab system information.

00:02:27.000 --> 00:02:31.090
The interesting thing about all of these modules is that for the most part,

00:02:31.090 --> 00:02:32.000
the network traffic is encrypted.

00:02:32.000 --> 00:02:36.999
It's usually SSL or TLS encrypted over various ports.

00:02:37.000 --> 00:02:43.000
For some reason, this network DLL, the network traffic for it, is not encrypted.

00:02:43.000 --> 00:02:46.000
And so, when we do some network analysis later on,

00:02:46.000 --> 00:02:48.000
we will actually be able to see what it was sending.

00:02:48.000 --> 00:02:49.000
(Aaron) Oh, that's interesting.

00:02:49.000 --> 00:02:52.000
So is this, do you think it's not encrypted because that module is potentially,

00:02:52.000 --> 00:02:56.000
if we look at a software development team and we have a modularized program,

00:02:56.000 --> 00:02:58.999
like any other normal program,

00:02:59.000 --> 00:03:01.714
especially organized crime still is called organized crime for

00:03:01.714 --> 00:03:04.571
a reason because it's ran like a business,

00:03:04.571 --> 00:03:04.999
right?

00:03:05.000 --> 00:03:07.999
So, for effective software with each lifecycle,

00:03:08.000 --> 00:03:09.999
you're going to have teams that maybe work on the network module,

00:03:09.999 --> 00:03:13.000
but don't have the same cipher suite capability built into that.

00:03:13.000 --> 00:03:16.000
For that reason, maybe like, cross team communication?

00:03:16.000 --> 00:03:17.000
(Tyler) It's possible.

00:03:17.000 --> 00:03:19.000
It's definitely possible, or you know,

00:03:19.000 --> 00:03:20.818
this could just be like some really old one that

00:03:20.818 --> 00:03:24.111
somebody forgot to turn encryption on, or yeah,

00:03:24.111 --> 00:03:25.000
who knows?

00:03:25.000 --> 00:03:26.000
Yeah, who knows?

00:03:26.000 --> 00:03:29.000
But yeah, for some reason this one does not,

00:03:29.000 --> 00:03:31.333
at least for the most part does not send its

00:03:31.333 --> 00:03:33.000
information encrypted over the network.

00:03:33.000 --> 00:03:36.000
(Aaron) It's copy/pasted from Stack Overflow?

00:03:36.000 --> 00:03:37.999
(Tyler) Probably, probably.

00:03:38.000 --> 00:03:38.333
Psfin64,

00:03:38.333 --> 00:03:43.000
this is an interesting one because it's actually used for point-of-sale devices.

00:03:43.000 --> 00:03:45.000
So if it gets on, if TrickBot gets on a point-of-sale device,

00:03:45.000 --> 00:03:49.000
and a lot of point-of-sale devices run Windows,

00:03:49.000 --> 00:03:50.999
and if you're not sure what a point-of-sale device is,

00:03:51.000 --> 00:03:55.090
these are the cash registers that you slide your card in at Target or Walmart,

00:03:55.090 --> 00:03:57.000
or any other place in the world.

00:03:57.000 --> 00:03:57.285
You know,

00:03:57.285 --> 00:04:00.375
these things can get infected and this module is specifically made to

00:04:00.375 --> 00:04:03.000
grab credit card information from point-of-sale devices.

00:04:03.000 --> 00:04:04.000
(Aaron) Got it.

00:04:04.000 --> 00:04:04.999
And Target is a good example, right?

00:04:05.000 --> 00:04:06.000
(Tyler) Right.

00:04:06.000 --> 00:04:08.000
Because they did get hit pretty hard (Aaron) Yep.

00:04:08.000 --> 00:04:10.000
(Tyler) Pwgrab is exactly what it sounds like.

00:04:10.000 --> 00:04:15.000
Its purpose is to go across the system and grab any saved user credentials.

00:04:15.000 --> 00:04:15.272
So,

00:04:15.272 --> 00:04:18.285
you know when you're in your browser and it says do

00:04:18.285 --> 00:04:19.999
you want to save this password,

00:04:20.000 --> 00:04:23.000
or you go to your email and you save your email client

00:04:23.000 --> 00:04:24.999
and you save your user password there?

00:04:25.000 --> 00:04:28.000
That's stored somewhere on your computer,

00:04:28.000 --> 00:04:31.000
and there are ways to decode that data to get it back.

00:04:31.000 --> 00:04:34.714
This module just scans across the entire computer looking for

00:04:34.714 --> 00:04:37.000
all that data because it knows where it's at.

00:04:37.000 --> 00:04:39.000
And so it's going to grab that out and it's going to

00:04:39.000 --> 00:04:40.000
send that back to the attackers.

00:04:40.000 --> 00:04:44.777
(Aaron) So whether that's a Chrome back-end datastore or a Mozilla,

00:04:44.777 --> 00:04:48.000
or whatever it is, do you know if it has,

00:04:48.000 --> 00:04:52.000
because there's capabilities as well for cracking older versions of KeyStore?

00:04:52.000 --> 00:04:55.000
And that's been something that I've seen with other malware.

00:04:55.000 --> 00:04:56.999
Does it have a KeyStore capability?

00:04:57.000 --> 00:04:59.000
(Tyler) It wouldn't surprise me if it did.

00:04:59.000 --> 00:04:59.999
I don't know for sure.

00:05:00.000 --> 00:05:01.000
(Aaron) Okay.

00:05:01.000 --> 00:05:01.250
(Tyler) But,

00:05:01.250 --> 00:05:04.000
you can see that this module is much larger than all the other modules.

00:05:04.000 --> 00:05:07.000
It's 1.2 MB or so.

00:05:07.000 --> 00:05:10.999
It would not surprise me if it had this capability to do that.

00:05:11.000 --> 00:05:14.000
If you think about it, when an attacker gets on a system,

00:05:14.000 --> 00:05:15.363
if I have safe credentials,

00:05:15.363 --> 00:05:19.000
then it makes sense for them to go and find it everywhere that they can

00:05:19.000 --> 00:05:21.000
because then they don't have to wait for me to log in,

00:05:21.000 --> 00:05:22.999
they can just grab it directly.

00:05:23.000 --> 00:05:27.000
(Aaron) Is this also the module that's going to dump LSASS?

00:05:27.000 --> 00:05:30.000
(Tyler) No, this one won't dump LSASS and do Mimikatz type capabilities.

00:05:30.000 --> 00:05:30.666
There's another module,

00:05:30.666 --> 00:05:32.999
it doesn't look like that plugin was downloaded in this case.

00:05:33.000 --> 00:05:35.999
But yeah, there's another module that will do that.

00:05:36.000 --> 00:05:37.000
(Aaron) Okay.

00:05:37.000 --> 00:05:39.777
(Tyler) This module is also interesting because even on Windows 10

00:05:39.777 --> 00:05:43.500
where the modules are downloaded directly into memory,

00:05:43.500 --> 00:05:48.000
when this runs it leaves in the data directory here,

00:05:48.000 --> 00:05:54.000
it will leave a file called grabber_temp.INTEG .RAW,

00:05:54.000 --> 00:05:57.125
and all that is is like some temporary file leftover from when it's

00:05:57.125 --> 00:05:59.999
grabbing credentials out of everywhere around your computer.

00:06:00.000 --> 00:06:02.999
So that's another indicator that you can look for.

00:06:03.000 --> 00:06:05.333
If you see this this file on your system,

00:06:05.333 --> 00:06:09.333
then chances are you've had TrickBot and it's grabbed any

00:06:09.333 --> 00:06:10.999
safe credentials that were on the system.

00:06:11.000 --> 00:06:13.000
(Aaron) Right, so you not only know that you are infected,

00:06:13.000 --> 00:06:18.000
you also know that any KeyStore that's been available has been compromised.

00:06:18.000 --> 00:06:19.000
(Tyler) Right.

00:06:19.000 --> 00:06:21.000
This last module, systeminfo64,

00:06:21.000 --> 00:06:25.000
this is another module that just goes through and grabs some system information,

00:06:25.000 --> 00:06:28.428
but a lot of researchers have actually seen this module used

00:06:28.428 --> 00:06:32.666
specifically to determine if the resources of this computer meet the

00:06:32.666 --> 00:06:34.999
requirements for deploying the Ryuk ransomware.

00:06:35.000 --> 00:06:38.285
So, this is a good indication, if you see systeminfo64,

00:06:38.285 --> 00:06:39.999
chances are, eventually,

00:06:40.000 --> 00:06:44.999
this version of TrickBot will be deploying Ryuk ransomware on your system.

00:06:45.000 --> 00:06:45.333
(Aaron) So,

00:06:45.333 --> 00:06:47.428
it's probably just pumping information back to a Reddit

00:06:47.428 --> 00:06:48.999
server somewhere that's saying yes or no?

00:06:49.000 --> 00:06:50.999
(Tyler) Yeah, yeah, pretty much.

00:06:51.000 --> 00:06:54.000
Or at least recording that information so that when the attacker decides,

00:06:54.000 --> 00:06:57.428
hey, I'm going to deploy Ryuk, then it knows,

00:06:57.428 --> 00:06:57.714
oh well,

00:06:57.714 --> 00:07:00.000
you know these 10 servers are the ones that I want to deploy on

00:07:00.000 --> 00:07:09.000
because it's going to hurt the company the most.
