WEBVTT

00:00:00.000 --> 00:00:03.388 align:middle line:90%


00:00:03.388 --> 00:00:06.776 align:middle line:90%
[AUDIO LOGO]

00:00:06.776 --> 00:00:10.170 align:middle line:90%


00:00:10.170 --> 00:00:12.450 align:middle line:90%
Leaked password databases.

00:00:12.450 --> 00:00:14.820 align:middle line:84%
In this video, we're
going to be exploring

00:00:14.820 --> 00:00:20.040 align:middle line:84%
the process of utilizing free
publicly available leaked

00:00:20.040 --> 00:00:24.480 align:middle line:84%
password data databases
online to essentially try

00:00:24.480 --> 00:00:28.590 align:middle line:84%
and find or identify whether
the emails, the email addresses

00:00:28.590 --> 00:00:31.950 align:middle line:84%
we've identified in
the previous video

00:00:31.950 --> 00:00:36.270 align:middle line:84%
have essentially suffered
from a potential data

00:00:36.270 --> 00:00:40.470 align:middle line:84%
breach on a website that
the owner of the email

00:00:40.470 --> 00:00:42.210 align:middle line:90%
had registered on.

00:00:42.210 --> 00:00:44.130 align:middle line:84%
And the objective
here, as I mentioned

00:00:44.130 --> 00:00:48.360 align:middle line:84%
in the previous video, is
to essentially try and find

00:00:48.360 --> 00:00:51.930 align:middle line:84%
whether the owner of the
email address has, as I said,

00:00:51.930 --> 00:00:53.200 align:middle line:90%
experienced a data breach.

00:00:53.200 --> 00:00:56.430 align:middle line:84%
And if so, we'll actually
obtain that password that

00:00:56.430 --> 00:00:58.230 align:middle line:84%
was leaked during
the data breach,

00:00:58.230 --> 00:01:01.800 align:middle line:84%
and we can then try and
utilize that password

00:01:01.800 --> 00:01:03.875 align:middle line:84%
to perform a password
spray attack.

00:01:03.875 --> 00:01:06.000 align:middle line:84%
Now, we're not going to be
doing that in this video

00:01:06.000 --> 00:01:09.930 align:middle line:84%
because we're still in the
passive information gathering

00:01:09.930 --> 00:01:12.310 align:middle line:90%
phase of this course.

00:01:12.310 --> 00:01:13.770 align:middle line:90%
So let's get started again.

00:01:13.770 --> 00:01:15.682 align:middle line:84%
I'm just going to be
using my Kali Linux VM.

00:01:15.682 --> 00:01:18.015 align:middle line:84%
So I'm just going to switch
over really, really quickly.

00:01:18.015 --> 00:01:21.120 align:middle line:90%


00:01:21.120 --> 00:01:23.930 align:middle line:84%
All right, so I'm back
on my Kali Linux VM,

00:01:23.930 --> 00:01:26.060 align:middle line:84%
and the site that I'm
going to be utilizing

00:01:26.060 --> 00:01:28.700 align:middle line:84%
for this demonstration
is a very popular site

00:01:28.700 --> 00:01:33.410 align:middle line:84%
called haveibeenppwned.com, or
simply put, have I been pwned?

00:01:33.410 --> 00:01:35.720 align:middle line:84%
Now, have I been pwned
is a really cool site

00:01:35.720 --> 00:01:40.130 align:middle line:84%
because it essentially
aggregates whatever

00:01:40.130 --> 00:01:44.270 align:middle line:84%
data breach happens on
in the world on some

00:01:44.270 --> 00:01:48.330 align:middle line:84%
of the most popular websites
in the world like Facebook,

00:01:48.330 --> 00:01:52.340 align:middle line:84%
Google, really any website
that has a data breach.

00:01:52.340 --> 00:01:56.210 align:middle line:84%
These guys, more specifically
Troy Hunt, the individual

00:01:56.210 --> 00:01:58.490 align:middle line:84%
that set up this
website, aggregates

00:01:58.490 --> 00:02:03.560 align:middle line:84%
that database and allows
users, anyone in the world,

00:02:03.560 --> 00:02:07.130 align:middle line:84%
to essentially check and see
whether their email address

00:02:07.130 --> 00:02:12.440 align:middle line:84%
or phone number has been
leaked in a data breach, which

00:02:12.440 --> 00:02:13.370 align:middle line:90%
is very, very common.

00:02:13.370 --> 00:02:18.020 align:middle line:84%
And one of the most important
things that you need to know

00:02:18.020 --> 00:02:22.490 align:middle line:84%
is most users don't really
know if their accounts

00:02:22.490 --> 00:02:26.150 align:middle line:84%
or their email has been leaked
or the email and password

00:02:26.150 --> 00:02:28.080 align:middle line:84%
has been leaked as
part of a data breach.

00:02:28.080 --> 00:02:30.920 align:middle line:84%
Now, why am I
referring you to this?

00:02:30.920 --> 00:02:33.740 align:middle line:84%
You might be saying, well,
do I check my own emails?

00:02:33.740 --> 00:02:35.250 align:middle line:90%
Well, you can do that.

00:02:35.250 --> 00:02:38.450 align:middle line:84%
In fact, I do recommend that you
do that because you might find

00:02:38.450 --> 00:02:42.560 align:middle line:84%
that your email and password has
been leaked as part of a data

00:02:42.560 --> 00:02:44.630 align:middle line:84%
breach on a site that
you had registered on,

00:02:44.630 --> 00:02:47.180 align:middle line:84%
and you may still be
using that password.

00:02:47.180 --> 00:02:50.690 align:middle line:84%
And the worst part about it
is that hackers have access

00:02:50.690 --> 00:02:52.460 align:middle line:90%
to this just like anyone else.

00:02:52.460 --> 00:02:55.340 align:middle line:84%
Now, in the context of
a penetration tester,

00:02:55.340 --> 00:02:58.970 align:middle line:84%
in the previous video, we took
a look at how to enumerate

00:02:58.970 --> 00:03:01.350 align:middle line:84%
or how to harvest
email addresses

00:03:01.350 --> 00:03:05.630 align:middle line:84%
using publicly available
resources or databases.

00:03:05.630 --> 00:03:07.860 align:middle line:84%
If we were targeting
an organization

00:03:07.860 --> 00:03:09.780 align:middle line:84%
and we found employee
email addresses,

00:03:09.780 --> 00:03:11.750 align:middle line:84%
we could essentially
put them in here.

00:03:11.750 --> 00:03:16.640 align:middle line:84%
And if they were leaked within
or as part of a data breach

00:03:16.640 --> 00:03:19.670 align:middle line:84%
and we were able to
obtain a password,

00:03:19.670 --> 00:03:22.820 align:middle line:84%
then we could use that password
and perform a password spray

00:03:22.820 --> 00:03:24.410 align:middle line:84%
attack and try and
log in to Google

00:03:24.410 --> 00:03:25.910 align:middle line:84%
with that same
email and password,

00:03:25.910 --> 00:03:30.470 align:middle line:84%
try and log into Facebook,
Instagram, you get the idea.

00:03:30.470 --> 00:03:31.740 align:middle line:90%
It's really, really dangerous.

00:03:31.740 --> 00:03:35.390 align:middle line:84%
So again, I can just put
in my own email here.

00:03:35.390 --> 00:03:39.012 align:middle line:84%
By the way, please don't
send me any emails.

00:03:39.012 --> 00:03:40.970 align:middle line:84%
I probably won't respond
to them on this email.

00:03:40.970 --> 00:03:43.220 align:middle line:84%
But you can see
that no pwnage has

00:03:43.220 --> 00:03:46.340 align:middle line:84%
been found, which means all the
sites that have registered on

00:03:46.340 --> 00:03:49.490 align:middle line:84%
with this email have not
experienced a data breach.

00:03:49.490 --> 00:03:52.880 align:middle line:84%
And as a result, my passwords
have not been leaked.

00:03:52.880 --> 00:03:56.720 align:middle line:84%
Now if we entered any
other email address,

00:03:56.720 --> 00:04:00.740 align:middle line:84%
maybe pippa@zonetransfer.me,
I doubt that has

00:04:00.740 --> 00:04:02.990 align:middle line:90%
been part of any data breach.

00:04:02.990 --> 00:04:06.383 align:middle line:84%
Let's just try and see
that, zonetransfer.me.

00:04:06.383 --> 00:04:09.630 align:middle line:90%


00:04:09.630 --> 00:04:10.180 align:middle line:90%
There we are.

00:04:10.180 --> 00:04:12.160 align:middle line:84%
So you can see that
works out just fine.

00:04:12.160 --> 00:04:15.330 align:middle line:84%
And again, all you need to do
is put in the employee's email

00:04:15.330 --> 00:04:15.930 align:middle line:90%
address here.

00:04:15.930 --> 00:04:18.899 align:middle line:84%
And most likely if they've
been using it for a long time,

00:04:18.899 --> 00:04:20.820 align:middle line:84%
they might have been
part of a data breach.

00:04:20.820 --> 00:04:23.820 align:middle line:84%
And, of course, that will
all tie into what sites

00:04:23.820 --> 00:04:25.110 align:middle line:90%
they registered on.

00:04:25.110 --> 00:04:28.770 align:middle line:84%
At the bottom here, you can see
it has a summary of the largest

00:04:28.770 --> 00:04:29.790 align:middle line:90%
breaches.

00:04:29.790 --> 00:04:32.280 align:middle line:84%
And, of course,
you can see we have

00:04:32.280 --> 00:04:34.350 align:middle line:90%
Facebook accounts, et cetera.

00:04:34.350 --> 00:04:35.730 align:middle line:90%
So you can click on that there.

00:04:35.730 --> 00:04:37.688 align:middle line:84%
And that'll give you more
information regarding

00:04:37.688 --> 00:04:38.680 align:middle line:90%
that particular breach.

00:04:38.680 --> 00:04:41.520 align:middle line:84%
So in April 2021,
a large data set

00:04:41.520 --> 00:04:44.040 align:middle line:84%
of over 500 million
Facebook users

00:04:44.040 --> 00:04:45.960 align:middle line:84%
was made freely
available for download,

00:04:45.960 --> 00:04:50.400 align:middle line:84%
encompassing approximately
20% of Facebook subscribers.

00:04:50.400 --> 00:04:56.220 align:middle line:84%
So the likelihood of an
individual having their email

00:04:56.220 --> 00:04:58.410 align:middle line:84%
and password leaked as
part of a data breach

00:04:58.410 --> 00:05:02.040 align:middle line:84%
is very, very common, unless
your email is really new.

00:05:02.040 --> 00:05:04.200 align:middle line:84%
Like for some of
my older emails,

00:05:04.200 --> 00:05:05.550 align:middle line:90%
they have been part of a breach.

00:05:05.550 --> 00:05:09.090 align:middle line:84%
And luckily for me, I do
regularly check the site just

00:05:09.090 --> 00:05:12.930 align:middle line:84%
to make sure that I'm not using
any of those passwords that

00:05:12.930 --> 00:05:14.220 align:middle line:90%
were part of the breach.

00:05:14.220 --> 00:05:17.340 align:middle line:84%
So I just wanted to share
this resource with you.

00:05:17.340 --> 00:05:19.870 align:middle line:84%
As I said, this will tie-in
to the previous video.

00:05:19.870 --> 00:05:23.430 align:middle line:84%
If you were able to identify
employee emails for the target

00:05:23.430 --> 00:05:26.370 align:middle line:84%
site that you are
targeting, then this

00:05:26.370 --> 00:05:29.675 align:middle line:90%
would be a great next step.

00:05:29.675 --> 00:05:31.800 align:middle line:84%
I would definitely recommend
taking a look at this.

00:05:31.800 --> 00:05:34.530 align:middle line:84%
Not a lot of penetration
testers do this.

00:05:34.530 --> 00:05:38.560 align:middle line:84%
But some of the
experienced ones do it.

00:05:38.560 --> 00:05:41.430 align:middle line:84%
So definitely, do
check this out.

00:05:41.430 --> 00:05:44.370 align:middle line:84%
Now have I been
pwned the only place

00:05:44.370 --> 00:05:45.580 align:middle line:90%
you can get this information?

00:05:45.580 --> 00:05:46.080 align:middle line:90%
No.

00:05:46.080 --> 00:05:48.330 align:middle line:84%
But again, the great
thing about this site

00:05:48.330 --> 00:05:50.280 align:middle line:90%
is you don't need to sign up.

00:05:50.280 --> 00:05:51.900 align:middle line:90%
They have an API.

00:05:51.900 --> 00:05:55.380 align:middle line:84%
And, of course, I would
recommend donating to this site

00:05:55.380 --> 00:05:58.680 align:middle line:84%
because they really are doing
the public a great service.

00:05:58.680 --> 00:06:02.010 align:middle line:84%
And as a penetration tester,
they're also doing us a service

00:06:02.010 --> 00:06:06.180 align:middle line:84%
because they allow us to
identify whether employees have

00:06:06.180 --> 00:06:08.280 align:middle line:84%
been laxed with their
password security

00:06:08.280 --> 00:06:13.200 align:middle line:84%
or are not in compliance with
the company's password security

00:06:13.200 --> 00:06:14.140 align:middle line:90%
policy.

00:06:14.140 --> 00:06:18.420 align:middle line:84%
And as we already know,
it's a standard tendency

00:06:18.420 --> 00:06:22.740 align:middle line:84%
for individuals, just normal
people to reuse passwords.

00:06:22.740 --> 00:06:26.430 align:middle line:84%
And that's really not
a fault of their own.

00:06:26.430 --> 00:06:29.260 align:middle line:84%
Once they have a password,
they tend to reuse it.

00:06:29.260 --> 00:06:31.440 align:middle line:84%
And if they have
reused a password that

00:06:31.440 --> 00:06:35.190 align:middle line:84%
was part of a data breach on
all of the sites that they use,

00:06:35.190 --> 00:06:38.370 align:middle line:84%
then all of those sites
are in essence compromised

00:06:38.370 --> 00:06:42.090 align:middle line:84%
because all it takes is
for one hacker or attacker

00:06:42.090 --> 00:06:44.520 align:middle line:90%
to target you, get your email.

00:06:44.520 --> 00:06:47.640 align:middle line:84%
They go to haveibeenpwned.com,
get that password,

00:06:47.640 --> 00:06:51.960 align:middle line:84%
and then try and log into all
of the sites you typically

00:06:51.960 --> 00:06:53.170 align:middle line:90%
have registered on.

00:06:53.170 --> 00:06:56.700 align:middle line:84%
So do take a look at
have I been pwned?

00:06:56.700 --> 00:06:58.770 align:middle line:84%
As I said, I can't really
showcase anything here

00:06:58.770 --> 00:07:01.050 align:middle line:84%
because that would
be a breach of ethics

00:07:01.050 --> 00:07:03.870 align:middle line:84%
because if there was a
password that was leaked here,

00:07:03.870 --> 00:07:07.150 align:middle line:84%
then that would not
be a good thing.

00:07:07.150 --> 00:07:10.200 align:middle line:84%
So this was more of an
informational video, where

00:07:10.200 --> 00:07:12.060 align:middle line:84%
I wanted to showcase
this really, really

00:07:12.060 --> 00:07:12.893 align:middle line:90%
important resource.

00:07:12.893 --> 00:07:14.310 align:middle line:84%
With that being
said, that's going

00:07:14.310 --> 00:07:16.830 align:middle line:84%
to conclude the
practical demonstration

00:07:16.830 --> 00:07:19.430 align:middle line:90%
side of this video.

00:07:19.430 --> 00:07:23.860 align:middle line:84%
All right, so that concludes
the passive information

00:07:23.860 --> 00:07:26.500 align:middle line:84%
gathering phase or
section of this course.

00:07:26.500 --> 00:07:28.480 align:middle line:84%
In the next section,
we're going to move on

00:07:28.480 --> 00:07:30.580 align:middle line:90%
to active information gathering.

00:07:30.580 --> 00:07:33.910 align:middle line:84%
So we'll take a look at how to
perform a DNS zone transfer,

00:07:33.910 --> 00:07:37.000 align:middle line:84%
how to perform port
scanning with Nmap.

00:07:37.000 --> 00:07:38.950 align:middle line:84%
And yeah, we're
essentially just going

00:07:38.950 --> 00:07:41.890 align:middle line:84%
to take a look at how to utilize
the information that we've

00:07:41.890 --> 00:07:47.500 align:middle line:84%
obtained to essentially learn
more about the target or target

00:07:47.500 --> 00:07:48.280 align:middle line:90%
system.

00:07:48.280 --> 00:07:52.000 align:middle line:84%
And that, of course, will
entail all techniques and tools

00:07:52.000 --> 00:07:55.060 align:middle line:84%
that actively engage
or communicate

00:07:55.060 --> 00:07:56.570 align:middle line:90%
with the target system.

00:07:56.570 --> 00:07:59.500 align:middle line:84%
So I'll see you
in the next video.

00:07:59.500 --> 00:08:00.000 align:middle line:90%