WEBVTT

00:00:00.040 --> 00:00:01.692
So it covers copying files in and out, but we've also,

00:00:01.692 --> 00:00:05.590
we've built this OS, we've made it look real, we've made

00:00:05.590 --> 00:00:06.820
the hardware look real right.

00:00:06.950 --> 00:00:09.330
We now need to have some tools on it that help us analyze

00:00:09.340 --> 00:00:12.035
what the malware's going to. And there are a ton of great

00:00:12.035 --> 00:00:13.760
malware analysis tools out there.

00:00:13.860 --> 00:00:17.950
But there's a set of tools that I think most people use like

00:00:18.030 --> 00:00:21.290
Microsoft's Sysinternals Process Monitor, Process Explorer.

00:00:21.340 --> 00:00:24.100
We talked about FakeNet, that's a commonly used tool.

00:00:24.190 --> 00:00:29.340
And like we said in one of the earlier modules, malware authors,

00:00:29.350 --> 00:00:32.910
they're moving away from anti‑VM detection, from VM detection to

00:00:32.920 --> 00:00:34.920
the detection of the analysis tools.

00:00:34.920 --> 00:00:35.260
Okay.

00:00:35.270 --> 00:00:40.180
And so we want to do a couple things to kind of make it more difficult for the

00:00:40.180 --> 00:00:44.250
malware authors to detect our analysis tools themselves.

00:00:44.390 --> 00:00:44.680
Yeah,

00:00:44.690 --> 00:00:47.289
so it can identify if it's on a weird hardware, it can identify if

00:00:47.710 --> 00:00:51.110
it's on a weird OS. It could also identify if we're running, if

00:00:51.110 --> 00:00:54.187
processes are running that are common tools that are being used. So

00:00:54.187 --> 00:00:58.270
how do you hide those processes? So, honestly, the easiest way to do

00:00:58.270 --> 00:01:00.180
this is just rename your tool.

00:01:00.190 --> 00:01:01.950
So like Process Monitor.

00:01:02.430 --> 00:01:07.370
It's file name is procmon.exe. So if a malware was doing a very simple check,

00:01:07.370 --> 00:01:09.780
they were just kind of enumerating through the right process list,

00:01:10.000 --> 00:01:13.570
they would look for things like propmon.exe. Just rename it to

00:01:13.570 --> 00:01:18.380
something like notepad.exe. It's going to work just as fine. It's

00:01:18.380 --> 00:01:23.500
still going to work the way that you expect it to. But then it's

00:01:23.500 --> 00:01:25.550
going to bypass that very simple check.

00:01:26.650 --> 00:01:29.180
Now Process Monitor, for example, does some other things.

00:01:29.180 --> 00:01:33.320
It loves a driver in order to kind of see the data it's looking for or

00:01:33.320 --> 00:01:37.540
that you want to see. You really can't control that. And so there are

00:01:37.540 --> 00:01:40.630
times where you may need to move away from tools that you're familiar

00:01:40.630 --> 00:01:42.430
with or that are more commonly used,

00:01:42.440 --> 00:01:45.250
and use something that's less common that the malware

00:01:45.250 --> 00:01:46.610
probably isn't going to be detecting.

00:01:46.620 --> 00:01:48.060
So, for example,

00:01:48.250 --> 00:01:52.320
for Process Monitor, Process Monitor is a tool that kind of monitors

00:01:52.320 --> 00:01:56.620
what's going on in your operating system in real time. Right. There

00:01:56.620 --> 00:01:58.280
are other tools that do the same thing.

00:01:58.280 --> 00:02:02.650
There's a great tool called WinAPIOverride that does the exact same thing.

00:02:03.320 --> 00:02:05.860
In fact, it kind of gives you a bit more capabilities.

00:02:05.870 --> 00:02:10.110
But malware is less likely to look for WinAPIOverride than it is for procmon.

00:02:10.110 --> 00:02:13.510
So if you get on the system and you're running these tools, and the malware

00:02:13.510 --> 00:02:16.340
just kind of immediately kills itself or isn't acting the way that it should,

00:02:16.510 --> 00:02:20.620
try using an alternative tool to see if then it runs, if it's not detecting

00:02:21.000 --> 00:02:22.050
that. That's a really good point.

00:02:22.110 --> 00:02:24.310
So we can change the names, or we can actually just use a different tool.

00:02:24.320 --> 00:02:26.930
That's a lot of benefits of the community, right?

00:02:26.930 --> 00:02:29.550
There's always like another variant or another tool that we can

00:02:29.550 --> 00:02:33.010
use to accomplish some of the same things. Right, and there are

00:02:33.020 --> 00:02:35.560
definitely other techniques that you can use. You can even start

00:02:35.560 --> 00:02:37.300
using malware against itself.

00:02:37.300 --> 00:02:41.850
Download a rootkit onto your system that you can control and hide your tools

00:02:41.850 --> 00:02:46.400
with the rootkit. You're kind of using the attacker's techniques and tools

00:02:46.410 --> 00:02:48.970
against themselves, but it's still a valid way to go.

00:02:49.570 --> 00:02:50.200
What I would say,

00:02:50.200 --> 00:02:53.170
though, if you're going to do that, kind of analyze that rootkit beforehand,

00:02:53.170 --> 00:02:57.950
make sure it doesn't have any back doors or anything in it, if for nothing else,

00:02:58.090 --> 00:03:01.310
just so you know that that traffic is from the rootkit that

00:03:01.320 --> 00:03:03.550
you're using and not from the malware.

00:03:03.690 --> 00:03:07.340
Yeah, I've actually never heard that, but it's incredibly brilliant.

00:03:07.520 --> 00:03:11.480
That's the way to do it because that's what rootkits do, they hide. Yeah,

00:03:11.480 --> 00:03:14.010
we're just going to use the attacker's tools against themselves.
