< Return to Video

Catching NSO Group's Pegasus spyware

  • 0:01 - 0:02
    [Translated by {Iikka}{Yli-Kuivila}
    (ITKST56 course assignment at JYU.FI)]
  • 0:04 - 0:10
    Herald: Good morning from C-Base, the
    space station beyond or under Berlin,
  • 0:13 - 0:19
    welcomes you to day 2 of the RC3
    streaming, we are starting in a few
  • 0:19 - 0:26
    seconds with the "Catching the NSO Group's
    Pegasus spyware". This is something that
  • 0:26 - 0:33
    has caught attention among the security
    and hacker communities over the world in
  • 0:33 - 0:38
    the last, I would guess, two years or so.
    There have been some spectacular cases of
  • 0:38 - 0:47
    murder, kidnappings, journalists being
    threatened, other things. The infamous
  • 0:47 - 0:53
    software doing this is called Pegasus,
    it's marketed by a company known by the
  • 0:53 - 1:02
    three-letter acronym NSO, whatever this
    stands for. And actually, Amnesty
  • 1:02 - 1:08
    International and its I.T. department, so
    to say, has invested quite some effort
  • 1:08 - 1:17
    into detecting whether a device has been
    infected by Pegasus or not. NSO marketed
  • 1:17 - 1:23
    this, among other things, as so-called
    "undetectable", well undetectable as in
  • 1:23 - 1:29
    software on a device, as we will see, and
    our speaker today, Donncha, Donncha O'Cearbhaill
  • 1:29 - 1:35
    from Ireland and from Amnesty
    International, will be presenting how they
  • 1:35 - 1:42
    developed detection tools for this nasty
    piece of spyware that has become so
  • 1:42 - 1:51
    popular among secret actors, state actors
    and others around the world. OK, enough
  • 1:51 - 1:56
    for the introduction, Donncha, the scene
    and the stream is yours. Good morning
  • 1:56 - 2:02
    Donncha: Good morning, and thank you for
    that introduction. So as the intro said,
  • 2:02 - 2:06
    today I'd like to talk to you about NSO
    group's Pegasus spyware, in particular I'd
  • 2:06 - 2:11
    like to explain a little bit about how we
    at Amnesty have investigated Pegasus over
  • 2:11 - 2:16
    the past few years and I'll also explain and
    demonstrate some of the tools we have
  • 2:16 - 2:22
    developed and published, that others also
    investigate and detect Pegasus spyware
  • 2:22 - 2:26
    potentially on their devices and the
    devices of other people in civil society.
  • 2:28 - 2:31
    So my name is Donncha O'Cearbhaill and I
    am a technologist based at the Amnesty
  • 2:31 - 2:36
    International Security Lab in Berlin with
    a small team who focuses on investigating
  • 2:36 - 2:43
    targeted digital threats such as spyware,
    phishing and other kinds of surveillance
  • 2:43 - 2:47
    that's directed against civil society and
    human rights defenders around the world.
  • 2:49 - 2:55
    So as the intro said, Pegasus has got a
    lot of attention in the past few months.
  • 2:57 - 3:01
    So you may have seen the Pegasus Project
    revelations that were published in July
  • 3:01 - 3:06
    during the summer. The Pegasus Project was
    a global investigation into abuses linked
  • 3:06 - 3:12
    to NSO group's Pegasus spyware. This
    investigation was based on a leaked
  • 3:13 - 3:19
    dataset of 50,000 potential Pegasus
    targets, which Amnesty International and
  • 3:19 - 3:23
    Forbidden Stories had access to, and so
    this global media investigation was
  • 3:23 - 3:27
    coordinated by Forbidden Stories, with the
    participation of about 80 journalists from
  • 3:27 - 3:32
    17 different media organisations around
    the world. During the Pegasus Project,
  • 3:32 - 3:37
    Amnesty International took the role of a
    technical partner, and the focus for
  • 3:37 - 3:42
    Amnesty International was to perform
    detailed innovative forensic analysis on
  • 3:42 - 3:47
    the devices of potential targets, and
    through this kind of forensic analysis and
  • 3:47 - 3:51
    this technical work we were able to
    identify traces of Pegasus, either
  • 3:51 - 3:59
    targeting or infecting online devices. So
    over a multi-month project Amnesty
  • 3:59 - 4:05
    Security Lab analyzed about 67 devices,
    and from these 67 devices of potential
  • 4:05 - 4:12
    targets at least 37 showed clear traces of
    Pegasus targeting or infection. So this is
  • 4:12 - 4:15
    really quite quite a high number of
    infected devices, and these devices
  • 4:15 - 4:22
    included journalists, activists,
    opposition political figures, all kinds of
  • 4:22 - 4:25
    people who were being unlawfully
    surveilled using Pegasus. Overall, of the
  • 4:25 - 4:32
    phones we have checked, which were iPhones
    and which hadn't been replaced, which took
  • 4:32 - 4:37
    data of the targeting, more than 80
    percent of the phones that were on this
  • 4:37 - 4:43
    list of potential targets showed traces of
    Pegasus. So in July these stories came out
  • 4:43 - 4:46
    and they highlighted cases of of civil
    society being targeted, such as
  • 4:46 - 4:51
    journalists in Hungary, activists in
    Morocco, activist Saudi Arabian
  • 4:51 - 4:57
    dissidents, also family members of Jamal
    Khashoggi, which the investigation showed
  • 4:57 - 5:01
    had been targeted with Pegasus spyware
    both before and after his his brutal
  • 5:01 - 5:06
    murder. So, yeah, you can. You can go and
    read many of these stories online. Today
  • 5:06 - 5:10
    I'd like to focus on and get to how we got
    there, how we developed these, these
  • 5:10 - 5:15
    tools, how we developed this methodology
    for finding Pegasus. And also to explain
  • 5:15 - 5:20
    about how you can also go and do this kind
    of searching for - for Pegasus and for
  • 5:20 - 5:27
    other mobile spyware. So let's take a step
    back for a second and ask, so what exactly
  • 5:27 - 5:32
    is Pegasus? Its name is well known, but
    what exactly is the software and how does
  • 5:32 - 5:37
    it work? OK, so first thing to remember is
    that actually, while Pegasus have been
  • 5:37 - 5:41
    gotten more well known in the last two
    years, it's not actually a new - a new
  • 5:41 - 5:45
    tool or a new product. So we know Pegasus
    has been around and then developed by NSO
  • 5:45 - 5:53
    Group since at least 2010. And on the left
    hand side here, the diagram, you can see a
  • 5:53 - 5:58
    Pegasus brochure from 2010 where it
    describes how Pegasus can be installed on
  • 5:58 - 6:03
    a BlackBerry devices. And we believe the
    original version of Pegasus was focused on
  • 6:03 - 6:07
    BlackBerry because back in 2010,
    smartphones were less prevalent than they
  • 6:07 - 6:11
    are now. BlackBerry is kind of a key
    target for some of the - the security
  • 6:11 - 6:17
    agencies who may want to buy this kind of
    spyware. So it developed over time here on
  • 6:17 - 6:23
    the right hand side, we can see some
    diagrams that were from a leaked Pegasus
  • 6:23 - 6:31
    brochure that was published in 2014. In
    the first diagram, here it talks about how
  • 6:31 - 6:37
    Pegasus is installed on a phone. In this
    example, it's showing how a Pegasus kind
  • 6:37 - 6:43
    of infection link can be sent over SMS to
    the target device. And then if opened how
  • 6:43 - 6:46
    the data can be collected and passed back
    to the - the operator of the Pegasus
  • 6:46 - 6:52
    software. That's just one example of -
    from their own diagrams. Here in the
  • 6:52 - 6:57
    circle below, you'll see a little bit of
    what Pegasus claims to be able to monitor.
  • 6:57 - 7:00
    And if you look at it, you can see it's
    basically everything on the device. So
  • 7:00 - 7:04
    it's talking about collecting email
    addresses, collecting SMS messages,
  • 7:04 - 7:09
    tracking location data, even reading the
    calendar, turning on the microphone of the
  • 7:09 - 7:14
    phone. And so bear in mind while this
    diagram is quite old, it's like six or
  • 7:14 - 7:18
    seven years old, you get an idea of what
    kind of data the Pegasus software will try
  • 7:18 - 7:23
    to collect from the phone. It's basically,
    it collected every kind of data on the
  • 7:23 - 7:26
    phone that might be of interest to
    somebody who is carrying out the
  • 7:26 - 7:32
    surveillance. One important thing to
    remember is that the Pegasus spyware is
  • 7:32 - 7:37
    able to get very kind of deep access to
    the phone, so it's fundamentally able to
  • 7:37 - 7:42
    access everything on the phone that the
    user is able to access and more. So even
  • 7:42 - 7:45
    if you're using a messaging app such as
    Signal or Telegram, which may be
  • 7:45 - 7:50
    encrypted, the Pegasus software is able to
    access that data and those messages before
  • 7:50 - 7:54
    they're encrypted on the device. So even
    once their spyware running on the phone
  • 7:54 - 7:58
    itself, none of these encrypted messaging
    apps will help because it has such low
  • 7:58 - 8:05
    level access to the device. So it's a
    little bit about what exactly Pegasus
  • 8:05 - 8:10
    tries to collect and what it - what it -
    what people can do with it using the
  • 8:10 - 8:17
    Pegasus software. So where exactly did the
    investigations into Pegasus start? So we
  • 8:17 - 8:24
    go back as far as 2016 was when Pegasus
    was first kind of identified in the wild,
  • 8:24 - 8:29
    being a being used to target an activist.
    So in this case, in 2016, Pegasus was
  • 8:29 - 8:35
    first found by Citizen Lab. Citizen lab
    is a group of researchers based in the
  • 8:35 - 8:40
    University of Toronto in Canada, who also
    works on investigating spyware targeting
  • 8:40 - 8:47
    civil society. So in this case, a UAE
    based human rights defender named Ahmed
  • 8:47 - 8:52
    Mansoor began to receive suspicious
    messages over SMS. So you can see some
  • 8:52 - 8:56
    screenshots of the messages on the right.
    So Ahmed Mansoor was cautious about these
  • 8:56 - 9:00
    because in the past he had previously been
    targeted with other kinds of spyware
  • 9:00 - 9:04
    tools, including - including Finfisher.
    So when he began to receive these
  • 9:04 - 9:08
    messages, he - he was cautious about them
    and he shared them with Citizen Lab, who
  • 9:08 - 9:13
    then began to investigate them. So what
    Citizen Lab realized is that these looked
  • 9:13 - 9:17
    to be an attack message, and they opened
    these attack links on their own testing
  • 9:17 - 9:22
    phone. When they did this they're able to
    capture the exploit that was being
  • 9:22 - 9:28
    delivered over these links and also
    able to capture a copy of the Pegasus
  • 9:28 - 9:33
    payload. So what happens when these links
    are opened is that the link is opened in a
  • 9:33 - 9:38
    web browser such as Safari. When the link
    is opened, the Pegasus server would return
  • 9:38 - 9:44
    to some JavaScript, some code that would
    exploit an unknown flaw in the Safari web
  • 9:44 - 9:48
    browser and by kind of manipulating the
    Safari web browser and exploit this
  • 9:48 - 9:53
    unknown flaw - they could then get their
    own code to start running inside this web
  • 9:53 - 9:58
    browser. And eventually, with the help of
    some additional flaws, they could then get
  • 9:58 - 10:03
    more privileged access on the iPhone and
    eventually install the full Pegasus
  • 10:03 - 10:11
    payload. So, yes, Citizen Lab first found
    it in 2016, it was it was a very important
  • 10:11 - 10:17
    discovery and it showed just how how
    serious some of the threats facing civil
  • 10:17 - 10:20
    society were. That there were people
    willing to use these kinds of very
  • 10:20 - 10:24
    expensive exploits to start targeting
    human rights defenders who are just doing
  • 10:24 - 10:28
    their human rights work. Unfortunately,
    after this, Ahmed Mansoor continued to get
  • 10:28 - 10:33
    harassed, and he was sentenced to prison,
    and he's currently still in prison from
  • 10:33 - 10:42
    since 2017. So for about four years now.
    So when did we at Amnesty start
  • 10:42 - 10:44
    investigating this. So our team has been
    investigating these kinds of threats for a
  • 10:44 - 10:49
    while, but really we started focusing on
    NSO and investigating NSO in 2018 after an
  • 10:49 - 10:55
    Amnesty colleague of ours started to
    receive some suspicious messages. So this
  • 10:55 - 10:59
    - this colleague received in May 2018
    received this message you can see here on
  • 10:59 - 11:04
    the left. The message is written in
    Arabic. But it this it claims that there
  • 11:04 - 11:09
    is going to be a protest happening shortly
    outside the Saudi Arabian Embassy. And
  • 11:09 - 11:13
    they asked the Amnesty staff member, to to
    support the protest and then to click on
  • 11:13 - 11:19
    this link for for more information. So
    fortunately, our Amnesty colleague, when
  • 11:19 - 11:22
    they received this message, they got quite
    suspicious. They were like, this is just
  • 11:22 - 11:25
    weird, I don't know this person. And so
    they shared a screenshot of this message
  • 11:25 - 11:30
    with us at the Amnesty Security Lab, and
    we began to investigate. So quite quickly
  • 11:30 - 11:35
    when we started looking at this domain
    name and the server, and we agreed it
  • 11:35 - 11:39
    looked kind of suspicious. And we also
    managed to identify some additional
  • 11:39 - 11:45
    domains and servers that were related to
    this original akhbar-arabia domain. And
  • 11:45 - 11:49
    quite quickly, it started to appear to us
    that this was indeed something suspicious,
  • 11:49 - 11:52
    and maybe it was some kind of an attack
    message. So at the time, we didn't know it
  • 11:52 - 11:59
    was necessarily NSO Group. By looking at
    the original and initial servers here. We
  • 11:59 - 12:03
    managed to create kind of a fingerprint,
    so some way of identifying the particular
  • 12:03 - 12:08
    configuration of the domain name and the
    server sent inside of this message. With
  • 12:08 - 12:12
    the aid of this fingerprint, we then began
    to do what's called an internet scan. So
  • 12:12 - 12:17
    we connect it to every single server on
    the Internet, send a particular request
  • 12:17 - 12:20
    and then find any other server on the
    Internet that matched this particular
  • 12:20 - 12:25
    fingerprint, this particular configuration
    from this server. So by doing this
  • 12:25 - 12:30
    internet scanning, what we found was 600
    different domains all across the Internet
  • 12:32 - 12:35
    that matched this fingerprint and that
    appeared to be related to the same kinds
  • 12:35 - 12:41
    of attacks. So what was really was really
    key is that we found that these these
  • 12:41 - 12:45
    domains were actually related to Pegasus
    because NSO Group had made one kind of key
  • 12:45 - 12:49
    mistake or key flow when they were setting
    up this infrastructure. So what happened
  • 12:49 - 12:58
    is that as described earlier Citizen Lab
    had previously identified servers being
  • 12:58 - 13:03
    used by NSO Group in 2016 after the
    expose in 2016 NSO shut down all of
  • 13:03 - 13:07
    these domains and infrastructure. And then
    began to set up new kind of infrastructure
  • 13:07 - 13:11
    that would not be related to NSO or not
    linkable to NSO. Fortunately they made a
  • 13:11 - 13:15
    mistake because they had reused one domain
    name from the previous set of
  • 13:15 - 13:20
    infrastructure and also being used in this
    new infrastructure. So by finding this one
  • 13:20 - 13:25
    domain out of 600 that had previously been
    in - in use by NSO, we're able to show
  • 13:25 - 13:29
    that these 600 domains were also related
    to Pegasus. And so we're able to show that
  • 13:29 - 13:34
    this message that was sent to our Amnesty
    International colleague was indeed related
  • 13:34 - 13:40
    to Pegasus and was an attempt to to
    compromise their device. So we published
  • 13:40 - 13:46
    these findings in August 2018, and at that
    time we also identified that another set
  • 13:46 - 13:51
    Saudi-Arabian activists had similarly been
    targeted, with a Pegasus exploit message
  • 13:51 - 13:56
    over WhatsApp. Following this, Amnesty
    International also supported a legal
  • 13:56 - 14:02
    action in Israel, which asked the Israeli
    Ministry of Defense to revoke NSO's export
  • 14:02 - 14:07
    licenses. To prevent this Pegasus software
    being sold to countries that would abuse
  • 14:07 - 14:12
    it to target Amnesty and also target other
    human rights activists. Unfortunately
  • 14:12 - 14:18
    later the Israeli court rejected the legal
    complaint and said that the Israeli
  • 14:18 - 14:23
    Ministry of Defense had adequate
    safeguards in place to prevent NSO's
  • 14:23 - 14:30
    exports being sold to countries who would
    abuse it. Here in the bottom on the left,
  • 14:30 - 14:36
    you can see that. You can see a chart
    which shows the number of Pegasus servers
  • 14:36 - 14:41
    online at the time. I mean, see here that
    when we published this report NSO acted
  • 14:41 - 14:47
    quite quickly to shut down all 500 or 600
    servers that were being used to deliver
  • 14:47 - 14:51
    Pegasus. So this just shows that, you
    know, NSO is kind of reading these
  • 14:51 - 14:55
    researches and paying attention to it. It
    is trying to avoid getting their
  • 14:55 - 14:59
    infrastructure and servers discovered by
    by researchers who are investigating these
  • 15:00 - 15:16
    kinds of abuses. So this is back in in
    2018, so after discovering this attack
  • 15:16 - 15:22
    against an Amnesty staff member we at
    Amnesty continued trying to investigate
  • 15:22 - 15:28
    Pegasus to try to find more cases of
    abuse. We next found Pegasus targeting
  • 15:28 - 15:35
    happening in Morocco in 2019. So you can
    see here on the right. This time, we found
  • 15:35 - 15:41
    that a Moroccan human rights defender
    named Maati Monjib was being targeted
  • 15:41 - 15:47
    repeatedly with Pegasus. When we checked
    his phone, we found that he had some
  • 15:47 - 15:52
    suspicious messages there, saying that the
    messages claimed that there is some, some
  • 15:52 - 15:58
    scandal or some news story, and they're
    asking the target to click on these links
  • 15:58 - 16:02
    to find out more information. So when we
    looked at these these links, we knew
  • 16:02 - 16:07
    immediately that they were Pegasus links,
    because we had previously identified these
  • 16:07 - 16:12
    domains as one of the 600 domains, that
    were being used in 2018. So for example,
  • 16:12 - 16:17
    you can see that in the second message on
    the right, we see the domain
  • 16:17 - 16:22
    videosdownload.co. We knew it was Pegasus
    because we'd previously identified and
  • 16:22 - 16:30
    published this domain in 2018. So this
    time we knew Maati was being targeted with
  • 16:30 - 16:35
    Pegasus, but we realized we needed to do
    some more investigation to see if his
  • 16:35 - 16:39
    phone was indeed compromised that we could
    collect more information from his device.
  • 16:40 - 16:43
    So when we did this, we actually found
    something quite interesting on Maati's
  • 16:43 - 16:48
    phone because we found what we believed
    was evidence of a new type of a targeting
  • 16:48 - 16:54
    on his phone. Instead of relying on the
    target being tricked into clicking on a
  • 16:54 - 16:59
    link which is maybe not reliable, or maybe
    the target can - can see something is
  • 16:59 - 17:04
    suspicious. We instead saw them using an
    what's called a network injection attack.
  • 17:04 - 17:08
    So how are network injection attack works
    is like this: So network injection
  • 17:08 - 17:15
    involves having some kind of equipment or
    software running on the what access to the
  • 17:15 - 17:19
    internet connection of the mobile device.
    So this can either be at the mobile phone
  • 17:19 - 17:23
    network or potentially having some - some
    software or hardware running on the same
  • 17:23 - 17:28
    Wi-Fi network as the target. And what it
    does is when the target is browsing the
  • 17:28 - 17:34
    web on their phone, eventually, the target
    browses and clicks on link that goes to a
  • 17:34 - 17:39
    regular http website. So without https. So
    when this regular http request is made,
  • 17:40 - 17:43
    the software that's running on the
    upstream network can see this http
  • 17:43 - 17:48
    request. And when the http request
    happens, it can instead, instead of
  • 17:48 - 17:52
    returning the correct response to correct
    content, instead it returns a http
  • 17:52 - 17:57
    redirect. And the http redirect will then
    send the browser of the phone to a
  • 17:57 - 18:02
    malicious exploit site, which can then
    hack the phone. So in the case of Maati,
  • 18:02 - 18:06
    we found that he had tried to go and check
    his email and typed in Yahoo.fr on his
  • 18:06 - 18:11
    browser when he typed in Yahoo.fr - the
    software running on the on the upstream
  • 18:11 - 18:16
    network saw this cleartext connection and
    then redirected his phone to this exploit
  • 18:16 - 18:20
    link we see above. So you see the domain
    is quite suspicious:
  • 18:20 - 18:25
    "get1tn0w.free247downloads.com". And
    again, it has some random characters at
  • 18:25 - 18:29
    the end, which looks like a kind of an
    exploit link. So at the time, we suspected
  • 18:29 - 18:34
    that this was was Pegasus, and it was a
    new way of delivering Pegasus without
  • 18:34 - 18:37
    tricking the user into clicking on a link.
    But we weren't certain that it was
  • 18:37 - 18:44
    Pegasus, potentially it was some other
    kind of spyware. Fortunately for us NSO
  • 18:44 - 18:51
    helped to confirm that this really was
    Pegasus, because before we published this
  • 18:51 - 18:56
    report, Amnesty wrote to NSO Group sharing
    our findings and interestingly one day
  • 18:56 - 19:00
    after we shared the findings with NSO this
    spyware server got shut down and went
  • 19:00 - 19:06
    offline. And this is already a week before
    the report was made publicly available. So
  • 19:06 - 19:09
    that kind of confirmed to us that NSO
    really was controlling this infrastructure
  • 19:09 - 19:13
    and were able to get it shutdown even when
    we'd only privately shared this
  • 19:13 - 19:19
    information with with NSO. A bit later, we
    found some more information about how this
  • 19:19 - 19:24
    attack may have been done - NSO at a trade
    fair was demonstrating some new type of
  • 19:24 - 19:28
    hardware they had developed, which you can
    see here on the photo on the right. And we
  • 19:28 - 19:34
    believe this this photo is of some kind of
    IMSI catcher or fake base station, which
  • 19:34 - 19:40
    can run a fake mobile phone network. And
    then target's phone: so Maati could
  • 19:40 - 19:44
    connect to this fake mobile phone base
    station. And from that position, it could
  • 19:44 - 19:49
    be possible for NSO to redirect the phone
    to a malicious - a malicious exploit link.
  • 19:49 - 19:54
    So we're not sure what happened in this
    case if this was the device that was used.
  • 19:54 - 19:58
    But we believe the NSO is demonstrating
    or testing these kinds of what are called
  • 19:58 - 20:06
    tactical infection methods. So this was
    where our findings were in Morocco - we
  • 20:06 - 20:11
    started to realize that actually relying
    on checking for SMS messages, checking for
  • 20:11 - 20:17
    links or relying on people coming to us
    with something suspicious wasn't going to
  • 20:17 - 20:22
    work anymore because we began to see what
    were called zero-click attacks. And so all
  • 20:22 - 20:26
    a Zero-click attack is is any way of
    infecting a device that doesn't rely on
  • 20:26 - 20:31
    some interaction from the user. Doesn't
    rely on the user clicking on a link. So we
  • 20:31 - 20:34
    can see here are some examples of other
    zero-click attacks that have been
  • 20:34 - 20:37
    discovered over the past couple of years.
    I guess one of the first ones here was in
  • 20:37 - 20:44
    2019, where NSO Group developed an exploit
    for a for WhatsApp, and it was then used
  • 20:44 - 20:51
    by their customers to target at least 1400
    different people around the world. All of
  • 20:51 - 20:58
    this - how it worked is that the - the
    target was simply to receive a call over
  • 20:58 - 21:02
    WhatsApp, even a missed call and the
    exploit would be able to compromise their
  • 21:02 - 21:06
    phone without the use of clicking
    anything. As I described earlier, we saw
  • 21:06 - 21:10
    these kinds of network injection attacks
    happen, and then later in 2020, Citizen
  • 21:10 - 21:18
    Lab also found an iMessage zero-day being
    used to again compromise iPhone users
  • 21:18 - 21:24
    without any interaction in 2020. So from
    our own investigations, we have found that
  • 21:24 - 21:31
    NSO has been using various zero-click
    exploits since at least summer 2017 until
  • 21:31 - 21:35
    July of this year. So we know it's not
    something that's quite new for NSO
  • 21:35 - 21:39
    but at least it's something we've
    started only recently discovering in the
  • 21:39 - 21:42
    past few years. And we've seen, NSO
    putting a lot of focus into developing
  • 21:42 - 21:53
    these kinds of complicated but very
    powerful zero-click exploits. So now that
  • 21:53 - 21:57
    we know that NSO and their customers are
    using these kind of zero-click attacks, we
  • 21:57 - 22:02
    realized we needed to do something kind of
    more advanced to try and find these cases
  • 22:02 - 22:07
    of cases of - of surveillance. The big
    problem with mobile devices is a lack of
  • 22:07 - 22:11
    visibility, whereas on desktop or laptop
    computers, we have antivirus available or
  • 22:11 - 22:14
    we have EDR systems available. There
    really is nothing similar that was
  • 22:14 - 22:18
    available for mobile devices. So these
    kinds of attacks, especially zero-click
  • 22:18 - 22:26
    attacks, are often going undetected. We
    got to investigate this. We realized that
  • 22:26 - 22:30
    it was difficult to perform forensics on
    mobile devices. It's actually not
  • 22:30 - 22:34
    impossible. We were somewhat surprised to
    realize that iPhones actually allow a
  • 22:34 - 22:39
    significant amount of relevant data to be
    extracted from the phones themselves in
  • 22:39 - 22:44
    the form of an iPhone backup. And so it's
    actually quite - quite possible to start
  • 22:44 - 22:49
    doing a forensic analysis on iPhones.
    Unfortunately, Android devices we found
  • 22:49 - 22:53
    were much more limited because of
    restrictions on the Android operating
  • 22:53 - 22:58
    system. It isn't possible to extract much
    data in an Android backup, and so all
  • 22:58 - 23:02
    we've really been able to do on Android is
    to simply check the SMS messages and maybe
  • 23:02 - 23:07
    the browser history for some traces of -
    of targeting. But again, it's just it's
  • 23:07 - 23:12
    much less data is available on Androids
    compared to iPhones. The other big problem
  • 23:12 - 23:16
    we realized is that there's there's a lack
    of any kinds of public tools for
  • 23:16 - 23:19
    consensual mobile forensics. All of the
    forensic tools that are out there are
  • 23:19 - 23:25
    designed for - for people to extract data
    from phones that they don't want or their
  • 23:25 - 23:29
    phones have been seized or phones that are
    somehow otherwise obtained. There's no
  • 23:29 - 23:35
    there's no tools available to really check
    your own phone for signs of spyware. So
  • 23:35 - 23:41
    this is where the Mobile Verification
    Toolkit comes into play. So - MVT - it is
  • 23:41 - 23:44
    a public tool developed by Amnesty
    International and designed to simplify the
  • 23:44 - 23:49
    process of analyzing mobile devices for
    traces of spyware. And here it's available
  • 23:49 - 23:53
    on GitHub, you can go check it out. And
    just to highlight all of the
  • 23:53 - 23:58
    cases of Pegasus targeting I've described
    previously in all the cases and traces
  • 23:58 - 24:02
    that are present for the rest of the
    presentation, all of these have been found
  • 24:02 - 24:09
    using MVT. So MVT really works to - to
    detect advanced spyware, including spyware
  • 24:09 - 24:15
    using zero-click, zero-day exploits and
    really sophisticated stuff such as
  • 24:15 - 24:19
    Pegasus. So while all of these different
    spyware vendors try to say: "Our thing is
  • 24:19 - 24:23
    undetectable": It is definitely advanced,
    they definitely spent a lot of money in
  • 24:23 - 24:27
    developing this stuff, but it's not magic.
    And if you're careful and diligent about
  • 24:27 - 24:30
    checking the traces, there's always
    mistakes that are made. There's always
  • 24:30 - 24:35
    ways of identifying potential suspicious
    behavior on these devices. And MVT it is
  • 24:35 - 24:45
    written in Python, it's a very easy to
    install, and if you have PIP, you can just
  • 24:45 - 24:50
    go a "pip3 install mvt" . And here's how
    it's how it's used. Again, it's very
  • 24:50 - 24:55
    straightforward. To check an iPhone, you
    simply make a backup of the iPhone and you
  • 24:55 - 25:00
    run this one command so it'll be "mvt-ios
    check-backup" and then you provide the
  • 25:00 - 25:05
    backup folder. In the command here we also
    see what's called a stix-file. So a .stix
  • 25:05 - 25:10
    file is simply a file containing
    indicators. This maybe like domain names
  • 25:10 - 25:15
    or IP addresses, or process names that are
    known to be linked to a spyware tool. And
  • 25:15 - 25:20
    so the MVT is a generic tool. It can be
    used with Pegasus indicators, but it also
  • 25:20 - 25:26
    can be used with indicators for other
    spyware tools and could be used to detect
  • 25:26 - 25:32
    other spyware. So MVT is a modular
    framework, it has modules for parsing
  • 25:32 - 25:37
    different kinds of databases such as SMS
    messages or browser history or other kinds
  • 25:37 - 25:41
    of files on the device. I'm going to go
    through and explain a few of the modules
  • 25:41 - 25:46
    that are available in MVT and show how
    this can be used to - to find traces of
  • 25:46 - 25:54
    Pegasus or other similar spyware tools. So
    one module that is quite useful is the SMS
  • 25:54 - 25:59
    module, which is quite straightforward, it
    simply reads the SMS database in iPhone
  • 25:59 - 26:04
    backup to extract all of the links from
    the SMS messages and check if any of those
  • 26:04 - 26:11
    SMS messages contain links to known
    malicious domains. So in this case, we're
  • 26:11 - 26:15
    checking a backup that is targeted with
    Pegasus, and we see that - we see that
  • 26:15 - 26:19
    there's multiple domains that are found
    and are tied to Pegasus. We see this
  • 26:19 - 26:25
    revolution-news.co, stopsms.biz and
    from what we know of NSO we've seen these
  • 26:25 - 26:33
    kinds of exploit SMS used primarily
    between 2016 and 2018. We've also seen
  • 26:33 - 26:38
    Pegasus links as far back as 2014, and as
    recently as 2020. So this has been quite
  • 26:38 - 26:43
    common and I - if these zero-click attacks
    are not available, I think we'll still see
  • 26:43 - 26:51
    these kinds of exploit links being sent in
    SMS. So another data source that's quite
  • 26:51 - 26:57
    useful and quite helpful for finding
    traces of targeting is the Safari browser
  • 26:57 - 27:04
    history. So what we've seen is we've seen
    some as we identify traces of exploit
  • 27:04 - 27:09
    being recorded in Safari browser history,
    especially after a network injection
  • 27:09 - 27:14
    attack. So in this case, while there's no
    link in SMS when a network injection
  • 27:14 - 27:19
    attack happens the exploit server domain
    will be recorded in the browser history.
  • 27:19 - 27:23
    And so by checking the browser history, we
    may be able to find evidence that this
  • 27:23 - 27:31
    attack happened. So on the right here you
    can see a screenshot and this screenshot
  • 27:31 - 27:38
    was actually taken by Moroccan journalist
    Omar Radi when he was being targeted with
  • 27:38 - 27:44
    one of these network injection attacks in
    Morocco. So when he was browsing the web
  • 27:44 - 27:47
    he clicked the link and then instantly
    redirected into this web page. And when
  • 27:47 - 27:50
    this screenshot was taken, it was actually
    running the JavaScript trying to exploit
  • 27:50 - 27:55
    his phone. So unfortunately, following the
    publication of this research Omar Radi was
  • 27:55 - 28:00
    repeatedly harassed by the Moroccan
    authorities and then he was eventually
  • 28:00 - 28:05
    jailed after an unfair trial, and he's
    currently - currently in jail.
  • 28:07 - 28:13
    So another file quite useful in our
    investigations is something called the ID
  • 28:13 - 28:18
    status cache file. So the ID status cache
    file is a file on iPhones, and it can
  • 28:18 - 28:24
    track traces of any iCloud accounts
    which interacted with the device. This can
  • 28:24 - 28:27
    be interacting with the device over a
    bunch of different Apple services,
  • 28:27 - 28:32
    including iMessage, AirDrop, Apple Photos.
    And so what is really useful about this
  • 28:32 - 28:39
    file, because it showed us which malicious
    accounts, which kind of Pegasus related
  • 28:39 - 28:46
    accounts had been targeting a particular
    device. So what we know about Pegasus - we
  • 28:46 - 28:52
    believe that these malicious accounts are
    - have been set up and have been used by
  • 28:52 - 28:58
    one individual Pegasus customer. So you
    can see here in the first row, we see this
  • 28:58 - 29:04
    email address linakeller and we saw this -
    this account being used to deliver a
  • 29:04 - 29:08
    iMessage zero-day to quite a number of
    different activists. So we've seen it
  • 29:08 - 29:16
    used to deliver exploits to two different
    Moroccan activists and a couple of French
  • 29:16 - 29:21
    political figures. So by - by looking at
    which individuals have been targeted by
  • 29:21 - 29:25
    the same, the same account, by the same
    customer we were able to kind of get a
  • 29:25 - 29:28
    better idea of who that customer might be
    and have some idea about the attribution
  • 29:28 - 29:34
    for that attack. The same in these other -
    in these other cases, for example we see
  • 29:34 - 29:39
    the jessicadavies1345 email. This was
    found on the phone of two different
  • 29:39 - 29:44
    Hungarian journalists. Same for the
    emmadavies' address and again for this
  • 29:44 - 29:49
    final address here: williams enny. We
    found this on the phone of two different
  • 29:51 - 29:58
    Hungarian individuals, hungarian
    activists. So this is really useful for us
  • 29:58 - 30:01
    in our investigation because it really
    helped us get a better idea of who might
  • 30:01 - 30:10
    be behind some of the attacks that we were
    seeing. So the previous logs
  • 30:10 - 30:16
    I showed about SMS, data and browser
    history. These show kind of traces of
  • 30:16 - 30:19
    targeting. They showed some of these had
    been sent a malicious link, but they don't
  • 30:19 - 30:24
    necessarily prove that a phone has been
    successfully compromised. So what I will
  • 30:24 - 30:29
    show now is some of the logs we can use to
    show that a device was indeed compromised.
  • 30:29 - 30:33
    One of these files that was very useful
    for us in our investigations was the so-
  • 30:33 - 30:40
    called data usage file. So the data usage
    file in an iPhone is a file that records
  • 30:40 - 30:44
    information about how much mobile data
    traffic each process on the phone has
  • 30:44 - 30:49
    used. So this may be used to, like help
    the iPhone keep track of, you know, which
  • 30:49 - 30:53
    apps on your phone are using the most of
    your mobile data. But what is really
  • 30:53 - 30:57
    helpful for this is that it actually
    recorded the names of some of the Pegasus
  • 30:57 - 31:01
    processes and how much data each of these
    pegasus processes were using. So for all
  • 31:01 - 31:08
    we know about NSO's Pegasus, we believe
    that when Pegasus is installed on a phone,
  • 31:08 - 31:14
    it will kind of pick a random name that it
    uses to kind of hide itself in running on
  • 31:14 - 31:18
    the system. Throughout our investigation
    we found about 50 different process names
  • 31:18 - 31:22
    that the Pegasus process was using to try
    and hide itself. And once we identified
  • 31:22 - 31:26
    these process names, then we could go and
    look for these Pegasus known Pegasus
  • 31:26 - 31:32
    process names on devices of potential
    targets. What's happened, this database
  • 31:32 - 31:36
    also shows a timestamp of when this
    process name was first kind of started on
  • 31:36 - 31:40
    the device, when it was last seen on the
    device. And also it gives you some kind of
  • 31:40 - 31:45
    information about how much data this
    process transferred. In some cases, this
  • 31:45 - 31:48
    has been gigabytes of data which shows
    that really the Pegasus spyware was
  • 31:48 - 31:53
    extracting a lot of data from the device.
    And again, this is all automated in MVT
  • 31:53 - 31:59
    so if you check a phone using MVT with the
    Pegasus indicators, it'll show quite
  • 31:59 - 32:05
    clearly if any of these processes have
    been found on the device. Another feature
  • 32:05 - 32:11
    that's been very helpful for us and in our
    analysis is the timeline feature of MVT.
  • 32:11 - 32:17
    So how the Timeline feature works is it
    takes all of the different indicators and
  • 32:17 - 32:21
    modules on the phone, so it checks the -
    the SMS messages, it check the - the file
  • 32:21 - 32:27
    system and every - every event, like every
    SMS message, every web browser lookup will
  • 32:27 - 32:33
    all be recorded in a single file with the
    date that it happened. So by looking at
  • 32:33 - 32:39
    this timeline, we can often see what
    different events happened around the same
  • 32:39 - 32:43
    time as each other, and this can give us
    some idea - some idea about how attacks
  • 32:43 - 32:48
    were actually delivered on this device. So
    I want to give you just one example of -
  • 32:48 - 32:52
    of how this timeline can be used. Just so
    you know how to use this timeline in your
  • 32:52 - 33:00
    own investigations. So this is actually a
    demonstration of the phone of a Rwandan
  • 33:00 - 33:06
    activist who was targeted in June 2021
    using the forcedentry, iMessage zero-day.
  • 33:06 - 33:14
    So we can see here on the timeline that on
    8:00 p.m. 8:45, we see the phone began to
  • 33:14 - 33:18
    receive some push notifications over
    iMessage. So it seems it receives like 46
  • 33:18 - 33:25
    push notifications. And then what we saw
    was that SMS attachments began to be
  • 33:25 - 33:30
    written to the phone. So in the final line
    here, we see that a file is written -
  • 33:30 - 33:34
    written to the SMS attachments directory.
    And if you look at the end of the line, we
  • 33:34 - 33:39
    see that the - the file being written to
    disk actually had a .GIF attachment. So at
  • 33:39 - 33:44
    the time we thought this was something to
    do with the exploit somehow. NSO was
  • 33:44 - 33:50
    delivering their exploit in that GIF file.
    If we look a little bit later in the
  • 33:50 - 33:56
    timeline, we see that about 10 minutes
    later, on the same day, a Pegasus process
  • 33:56 - 34:02
    starts running on the phone. This otpgrefd
    process. Shortly afterwards, some
  • 34:02 - 34:07
    additional files are written on disk and
    some more Pegasus processes start. So by
  • 34:07 - 34:12
    looking at this timeline together, we can
    see quite clearly that the phone began to
  • 34:12 - 34:16
    receive iMessage messages. These GIF
    attachments start to be written on the
  • 34:16 - 34:21
    disk and then about 10 minutes later, the
    phone was compromised with the Pegasus. So
  • 34:21 - 34:23
    remember here like - there was no
    interaction from the user - they didn't
  • 34:23 - 34:26
    click on any link. As far as we are aware
    they I didn't even notice anything
  • 34:26 - 34:29
    happening on the device. This simply
    silently these messages were being
  • 34:29 - 34:35
    delivered and after 10 or 20 minutes,
    Pegasus began to gain access to the
  • 34:35 - 34:40
    device. So we've shared some of these
    findings with Apple, and then later in
  • 34:40 - 34:47
    September 2021, Apple - Citizen Lab
    identified a copy of this exploit on
  • 34:47 - 34:50
    another - phone of an another activist and
    they shared it with Apple and Apple
  • 34:50 - 35:01
    patched this vulnerability in September
    2021. So that's a little bit of how MVT
  • 35:01 - 35:07
    works and how some of this methodology
    works to identify Pegasus on a
  • 35:07 - 35:13
    device. So since we published our forensic
    methodology and our tools, many other
  • 35:13 - 35:19
    groups and organisations have been using
    these tools and methodology to check other
  • 35:19 - 35:24
    devices for signs of Pegasus and found
    quite a number of new cases. Here on the
  • 35:24 - 35:29
    top right you're going to see an example
    of another NGO "Frontline Defenders", who
  • 35:29 - 35:33
    identified six Palestinian human rights
    defenders who had their devices hacked
  • 35:33 - 35:39
    using Pegasus. And other case we see
    that the Belgian military intelligence
  • 35:39 - 35:44
    services use a similar methodology to
    check the phones of journalists in
  • 35:44 - 35:49
    Belgium, and they found that a journalist,
    Belgian journalist, Peter Verlinden, had
  • 35:49 - 35:54
    his iPhone hacked who they suspected by
    Rwanda. Again, we see another case where
  • 35:54 - 35:59
    French intelligence services confirmed
    that a number of French journalists had
  • 35:59 - 36:06
    their phones hacked using using Pegasus
    again using a similar methodology. So what
  • 36:06 - 36:11
    I'd like to highlight is MVT can really be
    useful in identifying traces of Pegasus, but also
  • 36:11 - 36:18
    MVT is designed as a kind of generic
    mobile forensic tool. So when used with
  • 36:18 - 36:21
    Pegasus indicators it will find Pegasus,
    but it also can be used to go and
  • 36:21 - 36:25
    proactively search for new kinds of
    spyware. So I really recommend that if
  • 36:25 - 36:29
    you're suspicious that phones may be
    targeted with this kind of spyware, you
  • 36:29 - 36:34
    can use MVT to extract some data and then
    dig into it. If the person is a member of
  • 36:34 - 36:38
    civil society or an activist then Amnesty
    and other organisations will be happy to
  • 36:38 - 36:44
    help support these investigations. And
    also, MVT is an open source tool. It's
  • 36:44 - 36:49
    based on different modules, and so we're
    always open to ideas for - for new modules
  • 36:49 - 36:54
    and new detection ideas to help make this
    tool better and better able to detect new
  • 36:54 - 37:04
    kinds of threats. One thing to remember
    about MVT it is - it's designed to detect
  • 37:04 - 37:07
    some kind of spyware. Unfortunately, the
    people who develop these spyware, they're
  • 37:07 - 37:10
    - they're smart people and they read these
    reports and they watch these kind of
  • 37:10 - 37:15
    presentations. And every time we publish
    information about how to detect these
  • 37:15 - 37:20
    kinds of spyware targeting civil society,
    the different spyware vendors and actors
  • 37:20 - 37:25
    will try to improve their tools to avoid
    them being detected. They'll try to kind
  • 37:25 - 37:30
    of upgrade their infrastructure to hide it
    again or to the better obscure their
  • 37:30 - 37:35
    activities. So just to give an example,
    here's some of the development of NSO's
  • 37:35 - 37:39
    own infrastructure over time. We see that
    after we published - Amnesty published the
  • 37:39 - 37:45
    report in 2018 NSO infrastructure was shut
    down and then later over the next two
  • 37:45 - 37:50
    years, it began to run more
    infrastructure, which was again shut down
  • 37:50 - 37:58
    after discovery in - in 2021. So it's a
    constant arms race. And so while - while
  • 37:58 - 38:01
    this - these tools are useful to detect
    Pegasus now, it's not always going to be
  • 38:01 - 38:05
    just automatic, and it's important to do
    further research to try and identify new
  • 38:05 - 38:12
    traces of new kinds of attacks. So what is
    the future for mobile spyware? So one
  • 38:12 - 38:17
    thing I'd like to reiterate is that while
    we focus a lot on NSO Group and Pegasus in
  • 38:17 - 38:20
    this research and in this
    talk and also there's been a lot of focus
  • 38:20 - 38:24
    on NSO Group. It's not the only mobile
    spyware out there, and there's definitely
  • 38:24 - 38:29
    many other players who are trying to get
    into the space and trying to also develop
  • 38:29 - 38:35
    similar kinds of spyware tools, which are
    then sold to - to different customers.
  • 38:35 - 38:42
    We've seen that from this investigation.
    We found at least 180 journalists who are
  • 38:42 - 38:45
    potential targets of Pegasus and many
    other human rights activists and
  • 38:45 - 38:50
    opposition politicians who have been
    targeted with these tools over the last number
  • 38:50 - 38:56
    of years. So far, these threat actors and
    these - these state agencies are able to
  • 38:56 - 39:01
    target activists and civil society with
    impunity due to a lack of visibility and
  • 39:01 - 39:05
    telemetry on mobile platforms. They've
    just been getting away with it because
  • 39:05 - 39:09
    they haven't been detected. So tools such
    as MVT can help expose some of these
  • 39:09 - 39:13
    threats, but they need to be used more
    widely and need to be used with more civil
  • 39:13 - 39:19
    society to really understand the full
    scope of these kinds of threats. And it's
  • 39:19 - 39:24
    also important that industry, the tech
    industry and the security industry work
  • 39:24 - 39:27
    closely with civil society to help detect
    and expose these threats because
  • 39:27 - 39:32
    unfortunately, the people most at risk
    from these kinds of really serious attacks
  • 39:32 - 39:36
    are some of the people who are the least
    equipped, both financially and technically
  • 39:36 - 39:43
    to defend against them. So to conclude,
    I think we're going to continue to see
  • 39:43 - 39:49
    attackers focusing on mobile. Mobile is
    where all the data is. No other place
  • 39:49 - 39:52
    gives you as much insight into somebody's
    life and all their most innermost
  • 39:52 - 39:56
    thoughts. Even just having a microphone in
    everybody's pocket in someone's pocket is
  • 39:56 - 40:02
    such a powerful position to be in that we
    think companies and states will continue
  • 40:02 - 40:07
    trying to develop these kinds of tools. We
    know - I think that zero-click exploits
  • 40:07 - 40:12
    are going to be highly, highly desirable.
    So while Apple and others have done a
  • 40:12 - 40:16
    great job in making attacks against
    iMessages more difficult, it's almost
  • 40:16 - 40:20
    certain that these kinds of cyber
    surveillance companies will continue
  • 40:20 - 40:24
    trying to develop zero-click exploits. If
    not for iMessage then maybe for other chat
  • 40:24 - 40:30
    platforms. I don't know like Signal or
    Telegram or WhatsApp, they're going to try
  • 40:30 - 40:37
    and attack other applications that
    activists are using. Unfortunately it's
  • 40:37 - 40:42
    not possible for activists and civil
    society to protect themselves from these
  • 40:42 - 40:47
    kinds of zero-day attacks from a technical
    sense. So we definitely need more active
  • 40:47 - 40:52
    collaboration between civil society and
    key platform vendors to help identify and
  • 40:52 - 40:56
    defend against these threats. And also, we
    urgently need better regulation to prevent
  • 40:56 - 41:01
    these kinds of really sophisticated
    spyware tools being sold to states and
  • 41:01 - 41:07
    agencies which have a long history of
    abusing them to target civil society and
  • 41:07 - 41:13
    opposition. So thank you all for
    listening, and I'm happy to answer some
  • 41:13 - 41:18
    questions now. If you have some questions
    or if you're concerned about, you are a
  • 41:18 - 41:21
    member of civil society or an activist
    or are concerned about surveillance please
  • 41:21 - 41:25
    feel free to contact us at share@amnesty.tech
    Thank you.
  • 41:25 - 41:31
    Herald: Thank you Donncha. Thank you from
    C-Base. We have already taken some
  • 41:31 - 41:37
    overtime this early hacker morning. There
    have been popping up some small questions
  • 41:37 - 41:43
    on our internal here from our tiny
    audience at C-Base. We don't have that
  • 41:43 - 41:48
    much time left. Just can you give us an
    indication: What is the pace of this
  • 41:48 - 41:54
    ongoing war? Do you feel that NSO group is
    actively fighting MVT and your tool
  • 41:54 - 41:58
    development or did - didn't you get this
    honor yet?
  • 41:58 - 42:05
    D: Definitely. We've seen, even in the
    past year, we saw NSO starting to be more
  • 42:05 - 42:11
    careful about cleaning up their forensic
    traces, and since 2020, they've begun to
  • 42:11 - 42:15
    already clean some of the traces that
    we've been using. And it's clear they've
  • 42:15 - 42:18
    realized that people are investigating
    that there is a risk of people discovering
  • 42:18 - 42:21
    this stuff, and I feel like after the
    revelations of this summer, they're going
  • 42:21 - 42:26
    to have a much more proactively trying to
    to clean up some of these traces. But as I
  • 42:26 - 42:31
    said, NSO is one company out there,
    there's also many other companies trying
  • 42:31 - 42:35
    to compete in the same space. So even if
    NSO gets better than, you know, other
  • 42:35 - 42:39
    companies are still out there and can
    still be caught using MVT and
  • 42:39 - 42:44
    fundamentally, even if they - they clean
    up some traces for any kind of failed
  • 42:44 - 42:48
    attacks, these traces are still going to
    be left around because it won't be
  • 42:48 - 42:51
    possible to for the spyware to clean up
    their traces.
  • 42:51 - 42:57
    H: Uhm-Hmm. So one could still after an
    attack eventually, eventually on an old
  • 42:57 - 43:03
    device years later discover that there had
    been some spyware activity, which may be
  • 43:03 - 43:10
    in the long run interesting information
    about dark campaigns and things. So NSO is
  • 43:10 - 43:15
    not the only actor, there will be more. Do
    you feel that there are just copycats in
  • 43:15 - 43:21
    the market or do you think there will be
    completely new threats in the future?
  • 43:21 - 43:25
    D: So I guess there's always there's lots
    of smart people who work for these
  • 43:25 - 43:30
    companies who are trying to develop these
    tools. Just last - earlier this month,
  • 43:30 - 43:34
    Citizen Lab published a report about
    another cyber surveillance vendor called
  • 43:34 - 43:41
    Cytrox based in North Macedonia, and they
    were selling similar spyware, which is
  • 43:41 - 43:45
    using kind of one-click attacks using
    links to help compromise iPhones and
  • 43:45 - 43:50
    Android phones. So that's one company
    that's competing in this space. There's
  • 43:50 - 43:55
    other companies doing doing similar kinds
    of targeting, but we believe, you know,
  • 43:55 - 43:59
    NSO was definitely the biggest company in
    this space, and they had a lot of money to
  • 43:59 - 44:05
    invest in, especially in these kind of
    zero-click attacks. So for now, we don't
  • 44:05 - 44:08
    know if they're a company that's as big or
    sophisticated as NSO, but I think many
  • 44:08 - 44:12
    others will be trying to take their place
    if NSO becomes less popular.
  • 44:12 - 44:19
    H: I see. I see. OK, thank you very much.
    We have to go over to the - RC3 morning
  • 44:19 - 44:27
    show in a few seconds. Thank you very much
    for this interesting talk this morning.
  • 44:27 - 44:34
    Again, share@amnesty.tech is the address
    to go to. And this is probably one of the
  • 44:34 - 44:39
    talks you want to watch again on
    media.ccc.de in a few days when it has
  • 44:39 - 44:46
    been published. So greetings to Ireland.
    Thank you very much and we will meet and
  • 44:46 - 44:51
    see again in real, I hope. Thank you.
    D: Thank you very much. Have a good day.
  • 44:55 - 45:03
    Everything is licensed under CC by 4.0.
    And it is all for the community, to download
  • 45:03 - 45:04
    Subtitles created by c3subtitles.de
    in the year 2022. Join, and help us!
  • 45:04 - 45:04
    [Translated by {Iikka}{Yli-Kuivila} (ITKST56 course assignment at JYU.FI)]
Title:
Catching NSO Group's Pegasus spyware
Description:

more » « less
Video Language:
English
Duration:
45:04

English subtitles

Revisions