WEBVTT

00:00:01.816 --> 00:00:03.026 align:middle line:90%
Now it's your turn.

00:00:03.026 --> 00:00:05.416 align:middle line:84%
You're going to dig into
this Malware sample.

00:00:05.416 --> 00:00:07.606 align:middle line:84%
You are going to
answer key questions.

00:00:07.606 --> 00:00:10.606 align:middle line:84%
And you are going to find out,
what was the person thinking

00:00:10.606 --> 00:00:11.536 align:middle line:90%
it was supposed to do?

00:00:11.536 --> 00:00:14.086 align:middle line:84%
What services are running
in the background?

00:00:14.086 --> 00:00:16.306 align:middle line:90%
How malicious is this software?

00:00:16.306 --> 00:00:19.366 align:middle line:84%
And could you
potentially figure out

00:00:19.366 --> 00:00:22.096 align:middle line:84%
if it's stealing information,
how it will name it?

00:00:22.096 --> 00:00:23.926 align:middle line:84%
Make sure, when you
go into your VM,

00:00:23.926 --> 00:00:28.576 align:middle line:84%
you realize there is
not a G Cases 4.3B.

00:00:28.576 --> 00:00:31.756 align:middle line:84%
If you did not
complete lab 4.3A,

00:00:31.756 --> 00:00:34.556 align:middle line:84%
you won't have the
piece of Malware.

00:00:34.556 --> 00:00:37.516 align:middle line:84%
So you're actually going to have
to load that Samsung extraction

00:00:37.516 --> 00:00:40.726 align:middle line:84%
and export
com.battery.extender.apk

00:00:40.726 --> 00:00:44.026 align:middle line:90%
to complete this lab.

00:00:44.026 --> 00:00:47.046 align:middle line:84%
We are now about
to review lab 4.3B.

00:00:47.046 --> 00:00:49.254 align:middle line:84%
If you're still working on
decompiling this Malware,

00:00:49.254 --> 00:00:51.546 align:middle line:84%
just press pause, and then
come back when you're ready.

00:00:51.546 --> 00:00:54.096 align:middle line:84%
The first question
is asking about what

00:00:54.096 --> 00:00:57.706 align:middle line:90%
is this app designed to do?

00:00:57.706 --> 00:00:59.836 align:middle line:84%
So what is it really
called, essentially?

00:00:59.836 --> 00:01:02.256 align:middle line:84%
So if we go to the
AndroidManifest,

00:01:02.256 --> 00:01:08.266 align:middle line:84%
and we look all
the way at the top,

00:01:08.266 --> 00:01:10.576 align:middle line:84%
we are going to see
that it was advertised

00:01:10.576 --> 00:01:12.346 align:middle line:90%
to be battery.extender.

00:01:12.346 --> 00:01:15.776 align:middle line:84%
However, when it's installed,
com.process.system.

00:01:15.776 --> 00:01:18.526 align:middle line:84%
And you may have found this
as well in the last lab

00:01:18.526 --> 00:01:23.386 align:middle line:84%
if you exported base.apk because
it was in the directory called

00:01:23.386 --> 00:01:25.016 align:middle line:90%
com.process.system.

00:01:25.016 --> 00:01:28.576 align:middle line:84%
And you can also see the
version for this Malware.

00:01:28.576 --> 00:01:32.176 align:middle line:84%
As far as permissions, there are
so many that are listed here--

00:01:32.176 --> 00:01:35.146 align:middle line:84%
when you start looking at some
of these, it's frightening.

00:01:35.146 --> 00:01:42.476 align:middle line:84%
Like, RECEIVE_SMS, access
your locations, SEND_SMS.

00:01:42.476 --> 00:01:45.596 align:middle line:84%
You can see CALL_PHONE,
has access to your camera,

00:01:45.596 --> 00:01:48.446 align:middle line:84%
RECORD_AUDIO, read your
contacts, write to contacts,

00:01:48.446 --> 00:01:49.436 align:middle line:90%
write to call log.

00:01:49.436 --> 00:01:50.426 align:middle line:90%
It's really bad.

00:01:50.426 --> 00:01:56.206 align:middle line:84%
So all of the permissions are
listed in AndroidManifest.xml.

00:01:56.206 --> 00:01:58.136 align:middle line:90%
Now let's keep digging.

00:01:58.136 --> 00:02:00.106 align:middle line:90%
This is one of my favorite ones.

00:02:00.106 --> 00:02:03.926 align:middle line:84%
Can you locate any
services that are running?

00:02:03.926 --> 00:02:07.194 align:middle line:84%
So if you are not frightened
by some of these apps yet,

00:02:07.194 --> 00:02:08.986 align:middle line:84%
you can even-- honestly,
you should do this

00:02:08.986 --> 00:02:10.778 align:middle line:84%
with some of the regular
apps that you use.

00:02:10.778 --> 00:02:17.316 align:middle line:84%
I'm going to type service,
and I'm going to click on--

00:02:17.316 --> 00:02:20.946 align:middle line:84%
all of these just so I get
the best or most information.

00:02:20.946 --> 00:02:25.026 align:middle line:84%
But look at here we see killer
mobile, AfterCallRecorder,

00:02:25.026 --> 00:02:28.566 align:middle line:84%
AudioRecorder, ChatCollector,
FacebookPhotoCollector,

00:02:28.566 --> 00:02:32.466 align:middle line:84%
GmailCollector, SQLiteAdapter,
which means it could go in

00:02:32.466 --> 00:02:34.356 align:middle line:90%
and edit databases.

00:02:34.356 --> 00:02:36.426 align:middle line:84%
This is one of those
perfect examples.

00:02:36.426 --> 00:02:40.096 align:middle line:84%
This Malware could have a
copy of some of these files.

00:02:40.096 --> 00:02:42.996 align:middle line:84%
So if the user deleted it, it
could potentially help you.

00:02:42.996 --> 00:02:46.326 align:middle line:84%
SkypeChatCollector,
ViberChatCollector.

00:02:46.326 --> 00:02:49.836 align:middle line:84%
It looks like it's going,
not only for your regular

00:02:49.836 --> 00:02:53.256 align:middle line:84%
permissions that you gave it
access to, but any third-party

00:02:53.256 --> 00:02:55.686 align:middle line:84%
apps that have access
to those permissions,

00:02:55.686 --> 00:02:59.616 align:middle line:84%
it's going and stealing
additional information--

00:02:59.616 --> 00:03:02.466 align:middle line:84%
not exactly a good
trait of something

00:03:02.466 --> 00:03:05.116 align:middle line:90%
you want on your mobile device.

00:03:05.116 --> 00:03:08.686 align:middle line:84%
If we go into the File
System over here--

00:03:12.056 --> 00:03:20.279 align:middle line:84%
so if we go into tmobile and
tracer, and we look at service,

00:03:20.279 --> 00:03:21.696 align:middle line:84%
this is another
way that you could

00:03:21.696 --> 00:03:23.586 align:middle line:90%
have found what it's stealing.

00:03:23.586 --> 00:03:28.206 align:middle line:84%
So if I just scroll up a little
bit and then zoom back in,

00:03:28.206 --> 00:03:30.006 align:middle line:84%
you can see specifically
each and every one

00:03:30.006 --> 00:03:31.956 align:middle line:90%
of these on what it's doing.

00:03:31.956 --> 00:03:34.746 align:middle line:84%
And you could look at the code
and see how it's doing it.

00:03:40.616 --> 00:03:44.696 align:middle line:84%
OK, for the next one, the
application checks for root.

00:03:44.696 --> 00:03:47.186 align:middle line:84%
I want you to think about why
an app would want to do this.

00:03:47.186 --> 00:03:48.686 align:middle line:84%
Because if you have
root access, you

00:03:48.686 --> 00:03:50.144 align:middle line:84%
really have the
keys to the kingdom

00:03:50.144 --> 00:03:52.296 align:middle line:84%
and could do many
things with that device.

00:03:52.296 --> 00:03:55.766 align:middle line:84%
So what we want to do
is we want to find where

00:03:55.766 --> 00:03:59.756 align:middle line:84%
the root is being checked
and how it actually

00:03:59.756 --> 00:04:01.356 align:middle line:90%
looks to the user.

00:04:01.356 --> 00:04:10.456 align:middle line:84%
So if we go out into
our services here,

00:04:10.456 --> 00:04:12.926 align:middle line:90%
you're going to find this root.

00:04:12.926 --> 00:04:15.416 align:middle line:84%
And what it's going to do is
show you the different methods

00:04:15.416 --> 00:04:17.276 align:middle line:90%
that it uses to check for root.

00:04:17.276 --> 00:04:20.066 align:middle line:84%
So the first one, it
checks for a systembin

00:04:20.066 --> 00:04:24.286 align:middle line:90%
to see if it's still superuser.

00:04:24.286 --> 00:04:26.326 align:middle line:84%
The next one, as we
keep going down-- just

00:04:26.326 --> 00:04:29.096 align:middle line:84%
keep clicking on the left, and
you'll see them on the right.

00:04:29.096 --> 00:04:31.246 align:middle line:84%
You can see here that
it looks for build tags,

00:04:31.246 --> 00:04:33.031 align:middle line:84%
and it runs something
called test-keys.

00:04:35.706 --> 00:04:42.116 align:middle line:84%
We could see here that it
checks for Superuser.apk

00:04:42.116 --> 00:04:45.026 align:middle line:84%
and then executes a SHELL
to see is, it Superuser?

00:04:45.026 --> 00:04:47.996 align:middle line:84%
So are you getting the
hashtag, pound symbol,

00:04:47.996 --> 00:04:50.706 align:middle line:84%
or are you getting
the dollar sign?

00:04:50.706 --> 00:04:53.806 align:middle line:84%
Most pieces of Malware
want to be root.

00:04:53.806 --> 00:04:55.746 align:middle line:84%
Now, if it's stealing
your information,

00:04:55.746 --> 00:04:57.486 align:middle line:84%
can you figure
out, if it records

00:04:57.486 --> 00:05:01.506 align:middle line:84%
a video, how it's
going to actually save

00:05:01.506 --> 00:05:02.866 align:middle line:90%
that on the device?

00:05:02.866 --> 00:05:13.036 align:middle line:84%
So if we go out to
activity, we can see here we

00:05:13.036 --> 00:05:16.986 align:middle line:84%
have VideoCapture and if
you look through the code

00:05:16.986 --> 00:05:21.766 align:middle line:84%
you should ultimately be able to
see how it's going to name it.

00:05:21.766 --> 00:05:24.396 align:middle line:84%
And we can see here it's going
to be formatted with the date

00:05:24.396 --> 00:05:27.076 align:middle line:84%
mp4, so this is what
we're looking for.

00:05:27.076 --> 00:05:30.876 align:middle line:84%
So then what you could do
is go into your extraction

00:05:30.876 --> 00:05:33.066 align:middle line:84%
and see, in those
specific locations

00:05:33.066 --> 00:05:36.046 align:middle line:84%
I told you about in section
2, if there's anything sitting

00:05:36.046 --> 00:05:38.046 align:middle line:84%
there waiting to be xfilled
to the server that's

00:05:38.046 --> 00:05:39.276 align:middle line:90%
stealing their information.
