WEBVTT

00:00:00.140 --> 00:00:02.000
Malware these days is actually quite complex.

00:00:02.000 --> 00:00:03.200
It's doing a bunch of checks.

00:00:03.200 --> 00:00:05.730
It's doing a bunch of things to make sure it doesn't wanna get caught.

00:00:06.080 --> 00:00:07.010
That kind of thing, right?

00:00:07.020 --> 00:00:11.960
Yes, a lot of malware today has anti‑analysis checks,

00:00:11.960 --> 00:00:14.120
so it's going to be looking for the tools that you're running.

00:00:14.250 --> 00:00:18.720
It has anti‑VM checks to make sure that it's not running in a virtual machine.

00:00:18.840 --> 00:00:20.540
We're seeing less and less of that,

00:00:20.540 --> 00:00:23.560
especially in newer malware just because virtual machines are just so

00:00:23.560 --> 00:00:27.710
prevalent in an enterprise. I can't think of any major organization

00:00:27.710 --> 00:00:29.900
that doesn't have virtualization in there.

00:00:30.120 --> 00:00:31.880
And so the malware authors have kind of realized,

00:00:31.880 --> 00:00:32.360
Well,

00:00:32.800 --> 00:00:36.270
maybe I don't necessarily want to not run on a system that's

00:00:36.270 --> 00:00:39.900
virtualized because that could be a system within an

00:00:39.980 --> 00:00:42.340
organization that I do want to compromise.

00:00:42.470 --> 00:00:45.989
So instead they're looking at, Is this computer running a debugger? Is

00:00:45.989 --> 00:00:49.890
it trying to debug me? Is it running any of the common analysis tools

00:00:49.890 --> 00:00:52.050
like process monitor or process explorer?

00:00:52.320 --> 00:00:55.320
Some of those tools we'll talk about later on. And there are

00:00:55.320 --> 00:00:58.170
ways that you can get around these checks. Some of them are a

00:00:58.170 --> 00:00:59.550
bit more complicated than others.

00:00:59.620 --> 00:01:02.960
But we'll talk about ways that we can either modify our virtual

00:01:02.960 --> 00:01:05.680
machine to get around the anti‑VM checks if they exist,

00:01:05.880 --> 00:01:09.150
and then ways that we can kind of modify our tools themselves to

00:01:09.150 --> 00:01:11.130
kind of get around some of these simple checks.

00:01:11.140 --> 00:01:13.050
You're never going to be able to get around everything.

00:01:13.220 --> 00:01:14.940
There's always going to be something that catches you.

00:01:14.940 --> 00:01:18.560
And so you always have the option to fall back to using an

00:01:18.570 --> 00:01:21.570
actual piece of hardware with the OS installed on it without

00:01:21.570 --> 00:01:23.260
any virtualization if you need to.

00:01:23.350 --> 00:01:26.480
But at least we'll talk about the ways that you can protect yourself and

00:01:26.480 --> 00:01:30.190
make some changes to kind of hide from these checks, and so you can try to

00:01:30.200 --> 00:01:32.550
bypass them without having to go that route.
