WEBVTT

00:00:01.931 --> 00:00:06.521 align:middle line:84%
OK, lab 4.3A, Hunting
for Android Malware--

00:00:06.521 --> 00:00:11.081 align:middle line:84%
you must do this
lab before 4.3B.

00:00:11.081 --> 00:00:13.181 align:middle line:84%
The reason-- you have
to find the Malware.

00:00:13.181 --> 00:00:16.301 align:middle line:84%
If you don't find the Malware,
you can't do lab 4.3B.

00:00:16.301 --> 00:00:19.241 align:middle line:84%
So make sure you take
your time with 4.3A.

00:00:19.241 --> 00:00:23.111 align:middle line:84%
If you have never worked a
Malware investigation before,

00:00:23.111 --> 00:00:26.381 align:middle line:84%
up until this point, you
have worked applications.

00:00:26.381 --> 00:00:28.421 align:middle line:84%
You know how to hunt
for applications.

00:00:28.421 --> 00:00:29.981 align:middle line:84%
You know your
Android cheat sheet

00:00:29.981 --> 00:00:31.773 align:middle line:84%
tells you what's running
in the background,

00:00:31.773 --> 00:00:33.401 align:middle line:84%
where to find
applications of interest.

00:00:33.401 --> 00:00:34.601 align:middle line:90%
Use that.

00:00:34.601 --> 00:00:37.331 align:middle line:90%
Hunt for the application.

00:00:37.331 --> 00:00:39.401 align:middle line:90%
The Malware is an application.

00:00:39.401 --> 00:00:42.501 align:middle line:84%
It's just doing really
rogue and nasty things.

00:00:42.501 --> 00:00:44.771 align:middle line:90%
Let's take a look at lab 4.3A.

00:00:44.771 --> 00:00:47.371 align:middle line:90%
So I'm in 4.3.

00:00:47.371 --> 00:00:49.351 align:middle line:84%
AXIOM has been
pre-processed for you.

00:00:49.351 --> 00:00:52.201 align:middle line:84%
AXIOM is really
helpful in this lab

00:00:52.201 --> 00:00:54.511 align:middle line:84%
because it hashes all
the files in a nice way

00:00:54.511 --> 00:00:56.101 align:middle line:90%
that you can sort by it.

00:00:56.101 --> 00:00:57.791 align:middle line:84%
Physical Analyzer
hashes as well,

00:00:57.791 --> 00:01:01.591 align:middle line:84%
but it's not as easy to
manipulate the file system

00:01:01.591 --> 00:01:06.571 align:middle line:84%
to get to where you need to be
for these specific hash values.

00:01:06.571 --> 00:01:11.111 align:middle line:84%
Hash values of the apps will
be very relevant in this lab.

00:01:11.111 --> 00:01:13.711 align:middle line:84%
So I'm going to load
this data in AXIOM.

00:01:13.711 --> 00:01:17.051 align:middle line:84%
I'm going to load it
in Physical Analyzer.

00:01:17.051 --> 00:01:19.391 align:middle line:84%
And we are going to
start this investigation.

00:01:19.391 --> 00:01:22.831 align:middle line:84%
Now, as far as tips
on where to start,

00:01:22.831 --> 00:01:25.481 align:middle line:84%
this is where you being
the artist comes into play.

00:01:25.481 --> 00:01:28.801 align:middle line:84%
I have so many students attack
this lab in different ways.

00:01:28.801 --> 00:01:30.451 align:middle line:84%
When I review it
with you, I'm going

00:01:30.451 --> 00:01:33.451 align:middle line:84%
to try to share with you
some of the unique mindsets

00:01:33.451 --> 00:01:38.001 align:middle line:84%
that students have shared with
me on, this is how I found it.

00:01:38.001 --> 00:01:39.771 align:middle line:90%
Think of it as an application.

00:01:39.771 --> 00:01:42.501 align:middle line:84%
It's an application that's
just doing bad things.

00:01:42.501 --> 00:01:46.761 align:middle line:84%
Now, the user, if
we look at this lab,

00:01:46.761 --> 00:01:50.821 align:middle line:84%
the user shares some
key hints with you.

00:01:50.821 --> 00:01:53.901 align:middle line:84%
So when we go through
and we look at this,

00:01:53.901 --> 00:01:56.991 align:middle line:84%
the user of this device supplied
you the phone that they think

00:01:56.991 --> 00:01:58.671 align:middle line:90%
is infected with Malware.

00:01:58.671 --> 00:02:02.091 align:middle line:84%
She admitted she did have
USB debugging enabled,

00:02:02.091 --> 00:02:05.301 align:middle line:84%
and she has accessed .apk files
outside of the Google Play

00:02:05.301 --> 00:02:06.141 align:middle line:90%
Store.

00:02:06.141 --> 00:02:09.021 align:middle line:84%
So what this means is, if you
were looking at local App State

00:02:09.021 --> 00:02:11.271 align:middle line:84%
DB, it's not going to
help you, because what

00:02:11.271 --> 00:02:13.871 align:middle line:84%
if the Malware didn't
come from the Play Store?

00:02:13.871 --> 00:02:17.741 align:middle line:84%
She was able to provide you a
time frame of January 1, 2019

00:02:17.741 --> 00:02:20.681 align:middle line:84%
through January 5,
2019 when the device

00:02:20.681 --> 00:02:22.551 align:middle line:90%
may have become infected.

00:02:22.551 --> 00:02:26.261 align:middle line:84%
You have a full physical image
that was acquired with UFED.

00:02:26.261 --> 00:02:29.651 align:middle line:84%
You can use Autopsy,
AXIOM, Physical

00:02:29.651 --> 00:02:33.491 align:middle line:84%
Analyzer, whatever you choose
to work this investigation.

00:02:33.491 --> 00:02:39.781 align:middle line:84%
Now, the lab is going to step
you through the scenario.

00:02:39.781 --> 00:02:41.941 align:middle line:84%
If you don't want to
use the lab questions,

00:02:41.941 --> 00:02:45.631 align:middle line:84%
if you just want to play,
let me see what I can find,

00:02:45.631 --> 00:02:46.471 align:middle line:90%
don't read these.

00:02:46.471 --> 00:02:49.201 align:middle line:84%
Because this is going to
kind of hold your hand

00:02:49.201 --> 00:02:50.791 align:middle line:90%
along the investigation.

00:02:50.791 --> 00:02:53.191 align:middle line:84%
If you want to work this
like a real incident response

00:02:53.191 --> 00:02:55.861 align:middle line:90%
case, your goal--

00:02:55.861 --> 00:02:58.861 align:middle line:84%
can you find any
suspicious applications?

00:02:58.861 --> 00:03:02.001 align:middle line:84%
If so, did the
user install them?

00:03:02.001 --> 00:03:05.131 align:middle line:84%
If so, how did
the user get them?

00:03:05.131 --> 00:03:07.941 align:middle line:84%
So how did this Malware
land on the device,

00:03:07.941 --> 00:03:12.591 align:middle line:84%
and did the sender or attacker
try to hide it in any way

00:03:12.591 --> 00:03:14.811 align:middle line:90%
or obfuscate it in any way?

00:03:14.811 --> 00:03:17.781 align:middle line:90%
Good luck.

00:03:17.781 --> 00:03:22.061 align:middle line:84%
We are now going to
walk through lab 4.3A.

00:03:22.061 --> 00:03:23.789 align:middle line:84%
If you're not ready,
simply press pause,

00:03:23.789 --> 00:03:25.331 align:middle line:84%
and then continue
when you would like

00:03:25.331 --> 00:03:29.551 align:middle line:84%
to see my methods for
chasing down this Malware.

00:03:29.551 --> 00:03:31.791 align:middle line:84%
You can follow the
E-Workbook step by step.

00:03:31.791 --> 00:03:34.041 align:middle line:84%
What I want to do is
show you different ways

00:03:34.041 --> 00:03:38.491 align:middle line:84%
that students have
identified Malware.

00:03:38.491 --> 00:03:40.403 align:middle line:84%
I'm going to start
in Physical Analyzer.

00:03:40.403 --> 00:03:42.361 align:middle line:84%
And this approach I'm
about to show you I think

00:03:42.361 --> 00:03:43.451 align:middle line:90%
is pretty interesting.

00:03:43.451 --> 00:03:45.281 align:middle line:84%
So if you go to
the applications,

00:03:45.281 --> 00:03:47.251 align:middle line:84%
whether you go
through Analyze Data,

00:03:47.251 --> 00:03:51.291 align:middle line:84%
or click on the Application
Insights, switch to Table View.

00:03:55.768 --> 00:03:57.351 align:middle line:84%
And then what we
want to do is just do

00:03:57.351 --> 00:03:59.401 align:middle line:90%
a little bit of filtering here.

00:03:59.401 --> 00:04:02.611 align:middle line:84%
So the first thing
I want to do is

00:04:02.611 --> 00:04:05.521 align:middle line:84%
choose the ones that are
not decoded by Cellebrite

00:04:05.521 --> 00:04:07.231 align:middle line:84%
because chances of
Malware being decoded

00:04:07.231 --> 00:04:09.001 align:middle line:90%
are probably slim to none.

00:04:09.001 --> 00:04:11.431 align:middle line:84%
And then I'm going
to also scroll over.

00:04:16.531 --> 00:04:23.281 align:middle line:84%
And I want to sort by
Permissions, so the ones that

00:04:23.281 --> 00:04:27.311 align:middle line:90%
have a lot of permissions.

00:04:27.311 --> 00:04:28.841 align:middle line:84%
And ultimately,
what I want to look

00:04:28.841 --> 00:04:36.381 align:middle line:84%
for are apps that may no
longer be in the App Store.

00:04:36.381 --> 00:04:39.531 align:middle line:84%
So I'm going to scroll over here
and see if we can see anything

00:04:39.531 --> 00:04:41.001 align:middle line:90%
where it alerts us to that.

00:04:41.001 --> 00:04:44.811 align:middle line:84%
So heavy permissions--
the ones that have a lot.

00:04:44.811 --> 00:04:47.721 align:middle line:84%
If you've see anything that
says app may not be from the App

00:04:47.721 --> 00:04:51.361 align:middle line:84%
Store or any of those types of
messages, those are helpful.

00:04:51.361 --> 00:04:57.351 align:middle line:84%
So as we start
looking through here,

00:04:57.351 --> 00:05:06.996 align:middle line:84%
we can see we have some Running
app, Root Spy, Antivirus.

00:05:06.996 --> 00:05:08.371 align:middle line:84%
I'm going to keep
scrolling down.

00:05:12.089 --> 00:05:13.381 align:middle line:90%
This is what we're looking for.

00:05:13.381 --> 00:05:17.371 align:middle line:84%
So I'm going to change
this category to this--

00:05:17.371 --> 00:05:19.126 align:middle line:90%
App May not be from Store.

00:05:22.881 --> 00:05:25.161 align:middle line:84%
Now, when we look
at this, right away,

00:05:25.161 --> 00:05:28.251 align:middle line:90%
we see that com.process.system.

00:05:28.251 --> 00:05:31.151 align:middle line:84%
Let's take a look at
information about this app.

00:05:31.151 --> 00:05:33.141 align:middle line:84%
So it tells us it was
in the foreground.

00:05:33.141 --> 00:05:34.731 align:middle line:90%
We see the version.

00:05:34.731 --> 00:05:36.791 align:middle line:84%
And we can see the
manifest file for it.

00:05:36.791 --> 00:05:38.201 align:middle line:84%
If you look at
this, it tells you

00:05:38.201 --> 00:05:42.551 align:middle line:84%
it has permissions to phone,
to tags, to social, to camera,

00:05:42.551 --> 00:05:46.236 align:middle line:84%
to storage, locations,
messages, microphone, network.

00:05:46.236 --> 00:05:47.861 align:middle line:84%
That looks like it's
interesting to us,

00:05:47.861 --> 00:05:50.311 align:middle line:90%
so I'm going to click on this.

00:05:50.311 --> 00:05:52.111 align:middle line:84%
And let it take me
to that directory.

00:05:55.161 --> 00:05:58.731 align:middle line:84%
And here is the actual
application for that.

00:05:58.731 --> 00:06:00.461 align:middle line:84%
So that's how one
student found it.

00:06:00.461 --> 00:06:02.141 align:middle line:84%
But now, even if
you have this, you

00:06:02.141 --> 00:06:03.941 align:middle line:84%
have to figure out,
how do they get it?

00:06:03.941 --> 00:06:07.511 align:middle line:84%
So you could technically
export base.apk at this point

00:06:07.511 --> 00:06:08.721 align:middle line:90%
if you wanted to.

00:06:08.721 --> 00:06:11.441 align:middle line:84%
You could look at File
Info, and we don't have

00:06:11.441 --> 00:06:12.861 align:middle line:90%
any date/time stamps for it.

00:06:12.861 --> 00:06:16.714 align:middle line:84%
So this is where you could
look at the AndroidManifest.xml

00:06:16.714 --> 00:06:18.131 align:middle line:84%
and see if you
have any file info,

00:06:18.131 --> 00:06:21.201 align:middle line:84%
but we are not getting a lot
of information from this.

00:06:21.201 --> 00:06:24.521 align:middle line:84%
Let's see if I
click on base.apk.

00:06:24.521 --> 00:06:25.851 align:middle line:90%
Now I have a date.

00:06:25.851 --> 00:06:29.141 align:middle line:84%
So now this is
interesting, 1/4/2019.

00:06:29.141 --> 00:06:32.181 align:middle line:84%
What I recommend is that you
timeline around that time,

00:06:32.181 --> 00:06:34.518 align:middle line:84%
and then you would
find all the chats.

00:06:34.518 --> 00:06:36.351 align:middle line:84%
But let me walk you
through a different way.

00:06:36.351 --> 00:06:38.726 align:middle line:84%
So that is the way of going
straight to the applications.

00:06:38.726 --> 00:06:42.591 align:middle line:84%
I personally, have never
worked a Malware case that way.

00:06:42.591 --> 00:06:47.851 align:middle line:84%
What I would typically do
is go into the file system

00:06:47.851 --> 00:06:52.021 align:middle line:84%
and look for the locations that
I told you about in section 2.

00:06:52.021 --> 00:06:54.991 align:middle line:84%
So remember how I told you
cache is commonly empty.

00:06:54.991 --> 00:06:56.261 align:middle line:90%
This has three files in it.

00:06:56.261 --> 00:06:57.331 align:middle line:90%
Let's take a look.

00:06:57.331 --> 00:07:00.781 align:middle line:84%
So one of the first ones we
see is this Chainfire auto root

00:07:00.781 --> 00:07:03.601 align:middle line:84%
And we can see it's
from the 5th of 2014.

00:07:03.601 --> 00:07:06.271 align:middle line:84%
She did say she
used USB debugging.

00:07:06.271 --> 00:07:09.593 align:middle line:84%
But this is a good clue to you
that this device was rooted.

00:07:09.593 --> 00:07:11.551 align:middle line:84%
Now, does it have to be
rooted to have Malware?

00:07:11.551 --> 00:07:14.381 align:middle line:84%
Absolutely not, but it does
make it more susceptible.

00:07:14.381 --> 00:07:17.561 align:middle line:84%
So here we could see
that Chainfire root log.

00:07:17.561 --> 00:07:19.601 align:middle line:84%
The next thing I would
do after looking at cache

00:07:19.601 --> 00:07:21.131 align:middle line:90%
is look for downloads.

00:07:21.131 --> 00:07:24.431 align:middle line:84%
So if the user saves
something, where will it go?

00:07:27.931 --> 00:07:29.851 align:middle line:84%
And I look in
these NO NAME files

00:07:29.851 --> 00:07:30.961 align:middle line:90%
to see if I find anything.

00:07:30.961 --> 00:07:32.741 align:middle line:84%
Doesn't look like
it's of interest.

00:07:32.741 --> 00:07:35.911 align:middle line:84%
So now I want to
go into userdata

00:07:35.911 --> 00:07:38.671 align:middle line:84%
and see if I can find the
media directory or downloads.

00:07:43.771 --> 00:07:51.601 align:middle line:84%
So here's media, primary
user, downloads, seven files.

00:07:51.601 --> 00:07:54.971 align:middle line:90%
Let's check this out.

00:07:54.971 --> 00:07:57.041 align:middle line:90%
Now, this is interesting.

00:07:57.041 --> 00:07:59.351 align:middle line:84%
When you download apps
from the App Store,

00:07:59.351 --> 00:08:01.901 align:middle line:84%
they do not get
downloaded right here.

00:08:01.901 --> 00:08:03.081 align:middle line:90%
This is unusual.

00:08:03.081 --> 00:08:06.551 align:middle line:84%
So the fact that we have
this battery.extender.apk,

00:08:06.551 --> 00:08:10.901 align:middle line:84%
whatsapp-1-1, and whatsapp-1,
that's of interest to us.

00:08:10.901 --> 00:08:13.451 align:middle line:84%
Now what I'm going to do
is I would export all three

00:08:13.451 --> 00:08:15.851 align:middle line:84%
of these at this point
because they are abnormal.

00:08:15.851 --> 00:08:17.771 align:middle line:84%
And you need them for
part two of the lab.

00:08:17.771 --> 00:08:22.391 align:middle line:84%
So I'm going to go
into Cases, Lab4.3,

00:08:22.391 --> 00:08:25.701 align:middle line:84%
and I'm just exporting
every single one of these,

00:08:25.701 --> 00:08:26.271 align:middle line:90%
just in case.

00:08:26.271 --> 00:08:28.104 align:middle line:84%
If you don't need them,
you can delete them.

00:08:32.683 --> 00:08:34.891 align:middle line:84%
What we can also do is look
at the timeline of these.

00:08:34.891 --> 00:08:36.961 align:middle line:90%
So we see 1/3--

00:08:36.961 --> 00:08:41.431 align:middle line:84%
it looks like 1/3/2019,
1/3/2019, 1/3/2019.

00:08:41.431 --> 00:08:43.981 align:middle line:84%
But then we have
this Coursepage.html.

00:08:43.981 --> 00:08:47.354 align:middle line:84%
If you click on that, we can
see some information here.

00:08:47.354 --> 00:08:49.021 align:middle line:84%
So I was hoping you'd
stumble upon this.

00:08:49.021 --> 00:08:50.938 align:middle line:84%
You can read this, "Sign
up by clicking here."

00:08:50.938 --> 00:08:54.301 align:middle line:84%
If you hover, you will see
that's actually to a Dropbox,

00:08:54.301 --> 00:08:57.211 align:middle line:90%
to com.battery.extender.apk.

00:08:57.211 --> 00:09:00.451 align:middle line:84%
The person clicked on,
"Sign up by clicking here,"

00:09:00.451 --> 00:09:02.461 align:middle line:84%
and battery.extender.apk
was downloaded.

00:09:02.461 --> 00:09:03.691 align:middle line:90%
So that's interesting.

00:09:03.691 --> 00:09:06.971 align:middle line:84%
This one here is some spam
for you to take this course.

00:09:06.971 --> 00:09:08.221 align:middle line:90%
So that's legitimate.

00:09:08.221 --> 00:09:11.281 align:middle line:84%
Now, what we want to do is
look at the date/time stamp

00:09:11.281 --> 00:09:12.871 align:middle line:90%
of this file.

00:09:12.871 --> 00:09:16.681 align:middle line:90%
So 1/3/2019 around 19:54 UTC.

00:09:16.681 --> 00:09:19.801 align:middle line:90%
Let's go into Timeline.

00:09:19.801 --> 00:09:33.681 align:middle line:90%
Let's change this to 1/3/2019.

00:09:33.681 --> 00:09:37.336 align:middle line:84%
I'm going to do 1 day and see
if that's enough to start.

00:09:37.336 --> 00:09:38.711 align:middle line:84%
I'm also going to
get rid of some

00:09:38.711 --> 00:09:39.911 align:middle line:84%
of the things that
are just noise,

00:09:39.911 --> 00:09:40.994 align:middle line:90%
that aren't going to help.

00:09:40.994 --> 00:09:43.921 align:middle line:84%
Like, cookies probably
aren't going to help.

00:09:43.921 --> 00:09:46.021 align:middle line:84%
Download email
images won't help.

00:09:46.021 --> 00:09:47.071 align:middle line:90%
Search items will.

00:09:47.071 --> 00:09:48.151 align:middle line:90%
Web history will.

00:09:48.151 --> 00:09:50.041 align:middle line:90%
OK, that looks good.

00:09:50.041 --> 00:09:51.414 align:middle line:90%
You can always add more.

00:09:51.414 --> 00:09:52.831 align:middle line:84%
But we want to see
if we can find,

00:09:52.831 --> 00:09:54.851 align:middle line:90%
how did the person get this?

00:09:54.851 --> 00:09:59.491 align:middle line:84%
So as we start looking,
we see there's email.

00:09:59.491 --> 00:10:01.291 align:middle line:90%
And look at this, magic--

00:10:01.291 --> 00:10:02.851 align:middle line:90%
Coursepage.

00:10:02.851 --> 00:10:07.911 align:middle line:84%
So we could see that
mraceventura1980

00:10:07.911 --> 00:10:12.111 align:middle line:84%
sent an email that says,
hey, there on 1/3/2019.

00:10:12.111 --> 00:10:16.071 align:middle line:84%
We could see that it
has two links in it.

00:10:16.071 --> 00:10:20.121 align:middle line:84%
It's from Liz Lemon
to Ace Ventura.

00:10:20.121 --> 00:10:22.106 align:middle line:90%
As we scroll down, Coursepage.

00:10:22.106 --> 00:10:23.481 align:middle line:84%
And she says, it's
been too long.

00:10:23.481 --> 00:10:25.801 align:middle line:84%
Thought this might be
something you would like.

00:10:25.801 --> 00:10:29.901 align:middle line:84%
So how she hid this,
she attached it,

00:10:29.901 --> 00:10:33.921 align:middle line:84%
she put an embedded
link that led him to get

00:10:33.921 --> 00:10:35.481 align:middle line:90%
that com.battery.extender.

00:10:35.481 --> 00:10:40.131 align:middle line:84%
So you can see that
portion of this.

00:10:40.131 --> 00:10:44.161 align:middle line:84%
So now he keeps going,
checking email and hang out.

00:10:44.161 --> 00:10:48.531 align:middle line:84%
So then there's this one from
Lloyd Christmas to Ace Ventura.

00:10:48.531 --> 00:10:50.421 align:middle line:84%
We can see it says,
here's a little something

00:10:50.421 --> 00:10:51.921 align:middle line:90%
so we can keep in touch.

00:10:51.921 --> 00:10:52.806 align:middle line:90%
And it has a URL.

00:10:56.051 --> 00:10:58.211 align:middle line:84%
And we could see it's
that new WhatsApp.

00:10:58.211 --> 00:11:02.121 align:middle line:84%
So this one was hidden
within Google Drive.

00:11:02.121 --> 00:11:07.021 align:middle line:84%
And if you look,
there's the URL,

00:11:07.021 --> 00:11:09.511 align:middle line:90%
and it downloads new WhatsApp.

00:11:09.511 --> 00:11:11.821 align:middle line:84%
So through Hangouts
was that chat.

00:11:11.821 --> 00:11:14.851 align:middle line:84%
Now, what would make your
life easier when we're looking

00:11:14.851 --> 00:11:16.621 align:middle line:90%
at these .apks.

00:11:16.621 --> 00:11:21.481 align:middle line:84%
This is where I don't like
how Cellebrite doesn't have

00:11:21.481 --> 00:11:23.321 align:middle line:90%
the hash values right in there.

00:11:23.321 --> 00:11:29.226 align:middle line:84%
So if we go into Magnet
into AXIOM, and we look at--

00:11:33.829 --> 00:11:35.621 align:middle line:84%
I think that's how it
spelled, newwhatsapp.

00:11:44.121 --> 00:11:50.991 align:middle line:90%
And if we go into--

00:11:50.991 --> 00:11:53.241 align:middle line:84%
I actually want to search
this in file system.

00:11:53.241 --> 00:11:55.221 align:middle line:90%
So a good reminder here--

00:11:55.221 --> 00:12:05.441 align:middle line:84%
we go into File System, we
stay at the top partition,

00:12:05.441 --> 00:12:14.641 align:middle line:84%
All Subfolders, and I'm
searching for newwhatsapp.

00:12:14.641 --> 00:12:15.541 align:middle line:90%
And I have no hits.

00:12:15.541 --> 00:12:19.011 align:middle line:84%
So then what I'm going to
do is click on this one.

00:12:19.011 --> 00:12:20.511 align:middle line:84%
Oh, goody, it does
not want to work.

00:12:28.099 --> 00:12:29.141 align:middle line:90%
So maybe it won't assist.

00:12:29.141 --> 00:12:33.223 align:middle line:90%
Let me go back into Artifacts.

00:12:33.223 --> 00:12:34.681 align:middle line:84%
I just want to get
the hash values.

00:12:34.681 --> 00:12:35.761 align:middle line:90%
Come on, AXIOM.

00:12:38.381 --> 00:12:39.386 align:middle line:90%
If we go into--

00:12:51.564 --> 00:12:53.481 align:middle line:84%
it's actually not going
to make it easy on me.

00:12:53.481 --> 00:12:56.161 align:middle line:84%
So I'm going to go back in to
Cellebrite here in a second.

00:12:56.161 --> 00:12:57.651 align:middle line:90%
Let's see, Android Downloads--

00:13:00.428 --> 00:13:01.761 align:middle line:90%
all right, this is what we need.

00:13:04.701 --> 00:13:06.941 align:middle line:84%
So when we're looking
at WhatsApp, what I want

00:13:06.941 --> 00:13:08.891 align:middle line:84%
is for it to show
us the hash value,

00:13:08.891 --> 00:13:12.901 align:middle line:84%
and it doesn't seem like it's
even doing that right now.

00:13:12.901 --> 00:13:13.651 align:middle line:90%
Not of assistance.

00:13:13.651 --> 00:13:14.413 align:middle line:90%
OK, I'm switching.

00:13:14.413 --> 00:13:16.121 align:middle line:84%
This is where you'll
see my frustrations,

00:13:16.121 --> 00:13:17.911 align:middle line:84%
and I go back and
forth in the tools.

00:13:17.911 --> 00:13:20.711 align:middle line:84%
We need to know the hash
values of these files.

00:13:20.711 --> 00:13:24.511 align:middle line:84%
So we can say, if they are the
same, if they're different--

00:13:24.511 --> 00:13:30.461 align:middle line:84%
because whatsapp-1
one and whatsapp-1.1,

00:13:30.461 --> 00:13:32.241 align:middle line:84%
why is it named
something different?

00:13:32.241 --> 00:13:34.631 align:middle line:84%
So what I'm going to do
is I'm going to go back

00:13:34.631 --> 00:13:38.251 align:middle line:90%
into the File System.

00:13:38.251 --> 00:13:43.406 align:middle line:84%
I'm going to search
for WhatsApp.

00:13:50.721 --> 00:13:52.611 align:middle line:84%
And you could even
specify more than that.

00:13:52.611 --> 00:13:54.673 align:middle line:84%
I could search for
com.whatsapp-1.

00:13:59.981 --> 00:14:01.931 align:middle line:84%
And that definitely
took it down to 16.

00:14:01.931 --> 00:14:05.911 align:middle line:90%
That's better to deal with.

00:14:05.911 --> 00:14:08.001 align:middle line:84%
And what we want to do
is find the hash value.

00:14:08.001 --> 00:14:09.521 align:middle line:90%
So this is what we want.

00:14:09.521 --> 00:14:11.881 align:middle line:90%
So here we could see it's 4db.

00:14:11.881 --> 00:14:18.931 align:middle line:84%
So we could see that's
the one for 1.1.

00:14:18.931 --> 00:14:21.991 align:middle line:84%
And if you look for the other
one, they're exactly the same.

00:14:21.991 --> 00:14:24.741 align:middle line:84%
So technically, you
only have to export one.

00:14:24.741 --> 00:14:25.924 align:middle line:90%
This was put there twice.

00:14:25.924 --> 00:14:28.341 align:middle line:84%
Remember when we said that,
if you click on something that

00:14:28.341 --> 00:14:30.201 align:middle line:84%
could potentially be
Malware or sideloaded,

00:14:30.201 --> 00:14:31.521 align:middle line:90%
it will double-download.

00:14:31.521 --> 00:14:33.981 align:middle line:90%
It's the exact same file.

00:14:33.981 --> 00:14:37.611 align:middle line:84%
Now, if you look at this .apk,
this is actually not Malware

00:14:37.611 --> 00:14:38.111 align:middle line:90%
at all.

00:14:38.111 --> 00:14:39.941 align:middle line:90%
It has led to just distract you.

00:14:39.941 --> 00:14:41.441 align:middle line:90%
It is something that's abnormal.

00:14:41.441 --> 00:14:45.431 align:middle line:84%
The real piece of Malware is
that com.battery.extender,

00:14:45.431 --> 00:14:47.441 align:middle line:84%
when it installs
itself and installs

00:14:47.441 --> 00:14:50.471 align:middle line:84%
as that com.process.system,
which is the Tracer Killer

00:14:50.471 --> 00:14:52.921 align:middle line:90%
Mobile Spyware.

00:14:52.921 --> 00:14:55.591 align:middle line:84%
Now, one of the most unique ways
I've seen someone find this,

00:14:55.591 --> 00:14:57.541 align:middle line:90%
and it kind of blew my mind--

00:14:57.541 --> 00:15:00.361 align:middle line:84%
and this is only
because Chrome was used.

00:15:00.361 --> 00:15:05.501 align:middle line:84%
If you go into
Physical Analyzer,

00:15:05.501 --> 00:15:12.871 align:middle line:84%
and we go into Downloads
under Web History for Chrome,

00:15:12.871 --> 00:15:15.121 align:middle line:84%
look at this little
tidbit over here.

00:15:15.121 --> 00:15:16.741 align:middle line:84%
It tells you
immediately, the URL

00:15:16.741 --> 00:15:23.071 align:middle line:84%
was Dropbox, where the Malware
was downloaded to, when

00:15:23.071 --> 00:15:26.281 align:middle line:84%
it was downloaded, how big
it was, that it completed,

00:15:26.281 --> 00:15:28.651 align:middle line:84%
that it came from
Chrome History.

00:15:28.651 --> 00:15:30.541 align:middle line:90%
And it tells you the downloads.

00:15:30.541 --> 00:15:35.481 align:middle line:84%
It tells you the URL,
the entire chain.

00:15:35.481 --> 00:15:42.376 align:middle line:84%
If we keep scrolling, it tells
us the referrer was Dropbox.

00:15:46.631 --> 00:15:49.901 align:middle line:84%
And it gives us the hash value
and says battery.extender.apk.

00:15:49.901 --> 00:15:53.954 align:middle line:84%
It gives us everything we really
needed except who sent it.

00:15:53.954 --> 00:15:55.871 align:middle line:84%
So then you could just
timeline on these dates

00:15:55.871 --> 00:15:57.691 align:middle line:90%
and walk your way out of it.

00:15:57.691 --> 00:15:59.441 align:middle line:84%
But what I need to
make sure that everyone

00:15:59.441 --> 00:16:01.331 align:middle line:84%
does at this point
is, you either

00:16:01.331 --> 00:16:08.531 align:middle line:84%
download battery.extender.apk,
or you download and save

00:16:08.531 --> 00:16:10.921 align:middle line:84%
the base.apk for
com.process.system.

00:16:10.921 --> 00:16:11.921 align:middle line:90%
So you have two choices.

00:16:11.921 --> 00:16:13.391 align:middle line:84%
I think the easiest
way to get it

00:16:13.391 --> 00:16:16.961 align:middle line:84%
is, if you go into Media
Downloads and just Right-Click

00:16:16.961 --> 00:16:19.481 align:middle line:84%
and do Save As, you
need this for part B

00:16:19.481 --> 00:16:22.001 align:middle line:84%
because I'm going to teach
you now how to decompile it.
