The Million Dollar Dissident: NSO Group’s iPhone Zero-Days used against a UAE Human Rights Defender

August 26, 2016

By Bill Marczak and John Scott-Railton, Senior Researchers at the Citizen Lab, with the assistance of the research team at Lookout Security

This report describes how a government targeted an internationally recognized human rights defender, Ahmed Mansoor, with the Trident, a chain of zero-day exploits designed to infect his iPhone with sophisticated commercial spyware.

1. Executive Summary

Ahmed Mansoor is an internationally recognized human rights defender, based in the United Arab Emirates (UAE), and recipient of the Martin Ennals Award (sometimes referred to as a “Nobel Prize for human rights”).  On August 10 and 11, 2016, Mansoor received SMS text messages on his iPhone promising “new secrets” about detainees tortured in UAE jails if he clicked on an included link. Instead of clicking, Mansoor sent the messages to Citizen Lab researchers.  We recognized the links as belonging to an exploit infrastructure connected to NSO Group, an Israel-based “cyber war” company that sells Pegasus, a government-exclusive “lawful intercept” spyware product.  NSO Group is reportedly owned by an American venture capital firm, Francisco Partners Management.

The ensuing investigation, a collaboration between researchers from Citizen Lab and from Lookout Security, determined that the links led to a chain of zero-day exploits (“zero-days”) that would have remotely jailbroken Mansoor’s stock iPhone 6 and installed sophisticated spyware.  We are calling this exploit chain Trident.  Once infected, Mansoor’s phone would have become a digital spy in his pocket, capable of employing his iPhone’s camera and microphone to snoop on activity in the vicinity of the device, recording his WhatsApp and Viber calls, logging messages sent in mobile chat apps, and tracking his movements.  

We are not aware of any previous instance of an iPhone remote jailbreak used in the wild as part of a targeted attack campaign, making this a rare find.

The Trident Exploit Chain:
  • CVE-2016-4657: Visiting a maliciously crafted website may lead to arbitrary code execution
  • CVE-2016-4655: An application may be able to disclose kernel memory
  • CVE-2016-4656: An application may be able to execute arbitrary code with kernel privileges

Once we confirmed the presence of what appeared to be iOS zero-days, Citizen Lab and Lookout quickly initiated a responsible disclosure process by notifying Apple and sharing our findings. Apple responded promptly, and notified us that they would be addressing the vulnerabilities. We are releasing this report to coincide with the availability of the iOS 9.3.5 patch, which blocks the Trident exploit chain by closing the vulnerabilities that NSO Group appears to have exploited and sold to remotely compromise iPhones.

Recent Citizen Lab research has shown that many state-sponsored spyware campaigns against civil society groups and human rights defenders use “just enough” technical sophistication, coupled with carefully planned deception. This case demonstrates that not all threats follow this pattern.  The iPhone has a well-deserved reputation for security.  As the iPhone platform is tightly controlled by Apple, technically sophisticated exploits are often required to enable the remote installation and operation of iPhone monitoring tools. These exploits are rare and expensive. Firms that specialize in acquiring zero-days often pay handsomely for iPhone exploits.  One such firm, Zerodium, acquired an exploit chain similar to the Trident for one million dollars in November 2015.

The high cost of iPhone zero-days, the apparent use of NSO Group’s government-exclusive Pegasus product, and prior known targeting of Mansoor by the UAE government provide indicators that point to the UAE government as the likely operator behind the targeting.

Remarkably, this case marks the third commercial “lawful intercept” spyware suite employed in attempts to compromise Mansoor.  In 2011, he was targeted with FinFisher’s FinSpy spyware, and in 2012 he was targeted with Hacking Team’s Remote Control System.  Both Hacking Team and FinFisher have been the object of several years of revelations highlighting the misuse of spyware to compromise civil society groups, journalists, and human rights workers.

Figure 1: Ahmed Mansoor, the “Million Dollar Dissident.”

The attack on Mansoor is further evidence that “lawful intercept” spyware has significant abuse potential, and that some governments cannot resist the temptation to use such tools against political opponents, journalists, and human rights defenders. Our findings also highlight the continuing lack of effective human rights policies and due diligence at spyware companies, and the continuing lack of incentives to address abuses of “lawful intercept” spyware.

Our report proceeds as follows:

  • Section 2 provides an overview of the attack against Ahmed Mansoor.
  • Section 3 details NSO Group’s tradecraft, gleaned from what appears to be a copy of NSO Group documentation leaked in the Hacking Team emails.
  • Section 4 summarizes our technical analysis of the attack against Mansoor (in collaboration with Lookout).
  • Section 5 describes how we found what appears to be the NSO Group’s mobile attack infrastructure while working on our previous Stealth Falcon report.
  • Section 6 links the spyware used in the attack on Mansoor to NSO Group.
  • Section 7 outlines evidence of other individuals targeted with the infrastructure that we linked to NSO Group, including Mexican journalist Rafael Cabrera.
  • Section 8 explains how the attack on Mansoor fits into the context of ongoing attacks on UAE dissidents.
  • Section 9 concludes the report.


2. Ahmed Mansoor Targeted With iPhone Zero-Day

Ahmed Mansoor is an internationally recognized human rights defender, blogger, and member of Human Rights Watch’s advisory committee.  Mansoor, who is based in the UAE, was jailed for eight months in 2011 along with four other activists for supporting a pro-democracy petition.  After he was released, Mansoor’s passport was confiscated, his car was stolen, and $140,000 disappeared from his bank account.  Mansoor is banned from traveling overseas, and his work continues to attract significant harassment and punishment

On the morning of August 10, 2016, Mansoor received an SMS text message that appeared suspicious. The next day he received a second, similar text. The messages promised “new secrets” about detainees tortured in UAE prisons, and contained a hyperlink to an unfamiliar website. The messages arrived on Mansoor’s stock iPhone 6 running iOS 9.3.3.

Mansoor quickly forwarded the messages to Citizen Lab researchers for investigation.  He has good reason to be concerned about unsolicited messages: every year since 2011, Mansoor has been targeted with spyware attacks, including with FinFisher spyware in 2011 and Hacking Team spyware in 2012 (see Section 8: Ahmed Mansoor and Previous UAE Attacks).

image00 image13
Figure 3: SMS text messages received by Mansoor (English: “New secrets about torture of Emiratis in state prisons”).  The sender’s phone numbers are spoofed.

When Mansoor’s messages reached us, we recognized the links: the domain name belongs to a network of domains that we believe to be part of an exploit infrastructure provided by the spyware company NSO Group (see Section 6: Linking NSO Group Products to the Attack on Mansoor).  We had first come across the NSO Group infrastructure during the course of our earlier research into Stealth Falcon, a UAE-based threat actor (see Section 5: Tracking a Mobile Attack Infrastructure).  

When we first found the infrastructure and connected it to NSO Group, we hypothesized that operators of the NSO Group spyware would target a user by sending them an infection link containing one of the exploit infrastructure domain names.  Though we had previously found several public occurrences of links involving these domains on Twitter (see Section 7: Evidence of Other Targets), none of the links we found seemed to be active (i.e., none produced an infection when we tested them).  In other exploit infrastructures with which we are familiar (e.g., Hacking Team’s exploit infrastructure), we had noted that operators prefer to deactivate such links after a single click, or after a short period of time, perhaps in order to prevent the disclosure of the exploit to security researchers.

We accessed the link Mansoor provided us on our own stock factory-reset iPhone 5 (Mansoor had an iPhone 6) with iOS 9.3.3 (the same version as Mansoor).  When we clicked the link, we saw that it was indeed active, and watched as unknown software was remotely implanted on our phone.  This suggested that the link contained a zero-day iPhone remote jailbreak: a chain of heretofore unknown exploits used to remotely circumvent iPhone security measures.  To verify our observations, we shared our findings with Lookout Security.  Both research teams determined that Mansoor was targeted with a zero-day iPhone remote jailbreak. The chain of exploits, which we are calling the Trident, included the following (see Section 4: The Trident iOS Exploit Chain and Payload for more details):

  • CVE-2016-4657: An exploit for WebKit, which allows execution of the initial shellcode
  • CVE-2016-4655: A Kernel Address Space Layout Randomization (KASLR) bypass exploit to find the base address of the kernel
  • CVE-2016-4656: 32 and 64 bit iOS kernel exploits that allow execution of code in the kernel, used to jailbreak the phone and allow software installation

The implant installed by the Trident exploit chain would have turned Mansoor’s iPhone into a digital spy in his pocket. The spyware, which appears to be NSO’s Pegasus spyware solution, was capable of employing his iPhone’s camera and microphone to eavesdrop on activity in the vicinity of the device, recording his WhatsApp and Viber calls, logging messages sent in mobile chat apps, and tracking his movements.


3. NSO Group and the Pegasus Solution

The attack on Mansoor appears to have used Pegasus, a remote monitoring solution sold by NSO Group Technologies Ltd (see Section 6: Linking NSO Group Products to the Attack on Mansoor).  NSO Group, based in Herzelia, Israel (CR# 514395409), develops and sells mobile phone surveillance software to governments around the world.  The company describes itself as a “leader” in “mobile and cellular Cyber Warfare,” and has been operating for more than six years since its founding in 2010.

NSO Group appears to be owned by a private equity firm with headquarters in San Francisco: Francisco Partners Management LLC, which reportedly acquired it in 2014 after approval from the Israeli Defense Ministry.  However, as of November 2015, Francisco Partners was reportedly exploring selling NSO Group, with a stated valuation of up to $1 billion. Interestingly, Francisco Partners previously invested in Blue Coat, a company selling network filtering and monitoring solutions, whose technology has been used by repressive regimes according to previous Citizen Lab research.

Figure 4: Image from an NSO Group brochure posted on SIBAT (The International Defense Cooperation Directorate of the Israel Ministry of Defense).

NSO Group has largely avoided the kind of high profile media attention that companies like Hacking Team and FinFisher have sometimes courted. The company maintains no website, there is little concrete information about NSO Group’s Pegasus product available online, and we know of no prior technical analysis of NSO Group’s products or infrastructure.

Some previous media reports have linked NSO Group and Pegasus to a scandal involving potential illegal eavesdropping in Panama, and possible sales to Mexico.  Other reports have suggested that NSO Group’s activities have aroused concern within the United States intelligence community.

Two of NSO Group’s three co-founders, Shalev Hulio and Omri Lavie, are also co-founders of mobile security company Kaymera, which promises a “Multi Layered Cyber Defense Approach” to clients.  On Kaymera’s website, the company reprints a Bloomberg article pointing out that they “play both sides of the cyber wars.”  The article also quotes NSO Group’s CEO, who suggests that they entered the defense business when potential clients saw the capabilities of NSO Group’s tools.

Figure 5: Kaymera’s website promises comprehensive mobile security


3.1. Pegasus Documents in Hacking Team Leak

Much of the publicly available information about Pegasus seems to be rumor, conjecture, or unverifiable claims made to media about capabilities. However, when we examined the Hacking Team emails leaked online after a 2015 breach, we found several instances of Hacking Team clients or resellers sharing what appeared to be NSO Group’s product documentation and sales pitches.

For instance, in December 2014, a reseller of surveillance technologies to the Mexican government forwarded a PDF document containing detailed technical specifications of NSO Group’s Pegasus system to Hacking Team.  According to the document’s metadata, it appears to have been created in December 2013 by Guy Molho, who is listed on LinkedIn as the Director of Product Management at NSO Group.


3.2. Device Infection

According to the purported 2013 NSO Group Pegasus documentation found in the Hacking Team materials, NSO Group offers two remote installation vectors for spyware onto a target’s device: a zero-click vector, and a one-click vector.  The one-click vector involves sending the target a normal SMS text message with a link to a malicious website.  The malicious website contains an exploit for the web browser on the target’s device, and any other required exploits to implant the spyware. In the attack against Mansoor, the Trident exploit chain was used.

To use NSO Group’s zero-click vector, an operator instead sends the same link via a special type of SMS message, like a WAP Push Service Loading (SL) message.  A WAP Push SL message causes a phone to automatically open a link in a web browser instance, eliminating the need for a user to click on the link to become infected. Many newer models of phones have started ignoring or restricting WAP Push messages.  Mobile network providers may also decide to block these messages.

Figure 6: Diagram from purported NSO Group Pegasus documentation showing the sequence through which the spyware (“Agent”) is installed on a target’s mobile device.  Source: Hacking Team Emails.

The documentation refers to a malicious website employed in installation of the spyware (“Agent”) as an Anonymizer, which communicates with a Pegasus Installation Server located on the operator’s premises.  When a target visits a malicious link from their device, the Anonymizer forwards the request to the Pegasus Installation Server, which examines the target device’s User-Agent header to determine if Pegasus has an exploit chain, such as the Trident, that supports the device.

If the device is supported, the Pegasus Installation Server returns the appropriate exploit to the target device through the Anonymizer and attempts an infection.  If infection fails for any reason, the target’s web browser will redirect to a legitimate website specified by the Pegasus operator, in order to avoid arousing the target’s suspicion.

In the operation targeting Mansoor, the one-click vector was used, with anonymizer (see Section 4: The Trident iOS Exploit Chain and Payload for more details).


3.3. Data Collection

According to the purported NSO Group documentation, once successfully implanted on a phone using an exploit chain like the Trident, Pegasus can actively record or passively gather a variety of different data about the device.  By giving full access to the phone’s files, messages, microphone and video camera, the operator is able to turn the device into a silent digital spy in the target’s pocket.

Figure 7: Diagram from purported NSO Group Pegasus documentation showing the range of information gathered from a device infected with Pegasus.  Source: Hacking Team Emails.

In the spyware used in targeting Mansoor, we confirmed many elements of this functionality, and observed indications that the collection of the following types of data was supported, among others (see Section 4.2: The Payload for more details):

  • Calls made by phone, WhatsApp and Viber,
  • SMS messages, as well as messages and other data from popular apps like Gmail, WhatsApp, Skype, Facebook, KakaoTalk, Telegram, and others,
  • A wide range of personal data, such as calendar data and contact lists, as well as passwords, including Wi-Fi passwords.


3.4. Exfiltration

According to the purported NSO Group documentation, an infected device transmits collected information back to a Pegasus Data Server at the operator’s premises, via the PATN (Pegasus Anonymizing Transmission Network).  The PATN appears to be a proxy chain system similar to Hacking Team’s anonymizers and FinFisher’s relays. The chain is intended to obfuscate the identity of the government client associated with a particular operation.  Once the collected information arrives on the Pegasus Data Server, an operator may visualize the information on a Pegasus Working Station.

Figure 8: A purported screenshot of NSO Group’s Pegasus Working Station software, which visualizes location data collected from infected devices (as of March 2012).  Source: Hacking Team Emails.

The implant in the attack targeting Mansoor communicated with two PATN nodes: and  The first of these,, appears to be a lookalike domain for the legitimate, a Gulf-based satellite television channel (see Section 5.2 for more details on lookalike domains observed in apparent NSO Group infrastructure).


3.5. Prioritizing Stealth

One interesting design decision of NSO Group’s Pegasus system, according to the purported NSO Group documentation, is that it emphasizes stealth above almost all else.  As the documentation states:

In general, we understand that it is more important that the source will not be exposed and the target will suspect nothing than keeping the agent alive and working.

Certain Pegasus features are only enabled when the device is idle and the screen is off, such as “environmental sound recording” (hot mic) and “photo taking.”  The documentation also states that the spyware implements a “self-destruct mechanism,” which may be activated automatically “in cases where a great probability of exposing the agent exists.”  However, the documentation claims that sometimes Pegasus removal can result in an infected device rebooting immediately after removal.


4. The Trident iOS Exploit Chain and Payload

In this section, we describe our technical analysis of the attack on Mansoor, including the Trident iOS Exploit chain and payload. Given the accelerated timeframe of this case, we are publishing the results of a preliminary analysis.

Recall that the investigation that led to the discovery of the Trident exploit chain began when UAE human rights activist Ahmed Mansoor forwarded to Citizen Lab two suspicious links that he received via SMS on his iPhone (Section 2).  Suspecting the links to be iPhone spyware associated with NSO Group (Section 6), we accessed them from our own stock factory-reset iPhone 5 running iOS 9.3.3.  Mansoor’s device is an iPhone 6, running iOS 9.3.3; we did not have an iPhone 6 available for testing.  Although the latest iOS version when Mansoor received the links was 9.3.4, this version had been released only one week beforehand.

We accessed the links by opening Safari on our iPhone, and manually transcribing the links from the screenshots that Mansoor sent.  After about ten seconds of navigating to the URL, which displayed a blank page, the Safari window closed, and we observed no further visual activity on the iPhone’s screen.  Meanwhile, we saw that the phone was served what appeared to be a Safari exploit, followed by intermediate files (final111), and a final payload (test111.tar). The first two payloads form the Trident exploit chain, and test111.tar is the payload.

Figure 9: Requests from our phone to as we clicked on the malicious link.  The first request is our click on the link.  The requests for ntf_bed.html, ntf_brc.html, and test111.tar are conducted by a stage2 binary (in final111).  All previous requests are conducted by Safari.

Suspecting what we had observed to be the work of a zero-day iPhone remote jailbreak, we shared the exploit and payloads with colleagues at Lookout Security, initiated a responsible disclosure process with Apple, and sent Apple the exploit and payloads.


4.1. The Trident Exploit Chain

This section provides a high-level overview of the Trident exploit chain used in the attack against Mansoor.  For further details, see Lookout’s report.

When a user opens the links sent to Mansoor on an iPhone, a stage1 containing obfuscated JavaScript is downloaded. The JavaScript downloads (via XMLHttpRequest) stage2 binaries for either 32-bit (iPhone 5 and earlier) or 64-bit (iPhone 5s and later), depending on the type of device.  The stage1 employs a previously undocumented memory corruption vulnerability in WebKit to execute this code within the context of the Safari browser (CVE-2016-4657).

The stage2 exploits a function that returns a kernel memory address, from which the base address of the kernel can be mapped (CVE-2016-4655).  The stage2 then employs a memory corruption vulnerability in the kernel (CVE-2016-4656).  This last vulnerability is employed to disable code signing enforcement, allowing the running of unsigned binaries.  The stage2 downloads and installs the stage3, which is the spyware payload.


4.2. The Payload

This section provides a high-level overview of the functionality of the spyware payload.  For more details, see Lookout’s report.

4.2.1. Persistence

The Trident is re-run locally on the phone at each boot, using the JavaScriptCore binary.  To facilitate persistence, the spyware disables Apple’s automatic updates, and detects and removes other jailbreaks.

4.2.2. Recording

The attack payload includes a renamed copy of Cydia Substrate, a third-party app developer framework, which it uses to help facilitate recording of messages and phone calls from targeted apps.  To record WhatsApp and Viber calls, the spyware injects WhatsApp and Viber using the Cydia Substrate, hooks various call status methods, and sends system-wide notifications when call events occur; the spyware listens for these notifications and starts or stops recording as appropriate.  It appears that the payload can spy on apps including: iMessage, Gmail, Viber, Facebook, WhatsApp, Telegram, Skype, Line, KakaoTalk, WeChat, Surespot,, Mail.Ru, Tango, VK, and Odnoklassniki.

The spyware also exfiltrates calendar and contact data, as well as passwords saved in the phone’s keychain, including Wi-Fi passwords and networks.

4.2.3. Exfiltration

The attack payload beacons back to command and control (C2) servers delivered in stage2 of the Trident, via HTTPS.  One of the binaries in the stage2 of the link sent to Mansoor contained the following string:


The Base64 string decodes to:

Your Google verification code is:5678429

This appears designed to look like a text message from Google containing a two-factor authentication code, though legitimate Google messages of this type do not contain a link, and contain one fewer digit in the verification code.  Base64-decoding the “i” parameter of the URL yields:,

These are the C2 servers for the spyware sent to Mansoor: and

A similar obfuscation appears to be used for exchange of information over SMS between an infected phone and the C2 Server.  In case the spyware’s C2 servers are disabled or unreachable, an operator may deliver updated C2 servers to an infection using this type of SMS, similar to FinFisher’s “emergency configuration update” functionality.


5. Tracking a Mobile Attack Infrastructure

This section explains how we first identified what appeared to be a mobile attack infrastructure while tracking Stealth Falcon.  We then outline some basic observations about the infrastructure, including themes in the domain names used by the attackers.  We link the infrastructure we found to NSO Group in Section 6.


5.1. Stealth Falcon Leads Us to a Mobile Attack Infrastructure

A year or so before Ahmed Mansoor received his suspicious SMS messages, we were tracking Stealth Falcon, a threat actor targeting individuals critical of the UAE government at home and abroad, several of whom were later arrested. For full details on Stealth Falcon, read our May 2016 report.

In the course of our investigation, we traced Stealth Falcon’s spyware to dozens of different command and control (C2) domains. One server that matched our C2 fingerprint for Stealth Falcon’s custom spyware,, was connected to the email address, according to data in its DNS SOA record.  The same email address appeared in WHOIS records for the following three domains:

These domains did not match our Stealth Falcon fingerprint. As we examined the domains, however, we found that the index page on these domains contained an iframe pointing to the website (Asrar Arabiya, or “Arabian Secrets” in English), which appears to be a benign website that takes a critical view of the Arab World’s “dictatorships.”  The index page also contained a nearly invisible iframe pointing to an odd looking site,

<iframe src="" width="1" height="1" border="0"></iframe>
<iframe src="" style="width:100%; height:1200px; position:absolute; 
top:-5px; left:-5px;" border="0"></iframe>

Figure 10: HTML content of the index page on the three fake “Asrar Arabiya” domains.

We suspect that the three domains we identified were attempting to mislead users into believing they were visiting the legitimate website.  Since we had linked the operation to Stealth Falcon, we suspected that the additional domain,, might be an attack domain.  We visited the URL in the iframe,, and were redirected to

<html><head><meta http-equiv='refresh' content='0;url=' /><meta http-equiv='refresh' content='
1;url=' /><title></title></head><body></body></html>

Figure 11: HTML content of  The page tells the web browser to redirect the visitor to Google.

We devised a number of fingerprints for various behaviors of, checked Shodan and Censys, and conducted our own scanning with zmap to identify related servers.  We found 237 live IP addresses, and extracted their domain names from the SSL certificates returned by the each server.  The SSL certificates we found included *,, and, the three domains in the spyware attack sent to Mansoor.

We linked these IPs and domain names to what appears to be NSO Group exploit infrastructure.


5.2. Coding the Domain Names

We coded the domain names we found, and identified several common themes, perhaps indicating the type of bait content that targets would receive.  Interestingly, the most common theme among the domains we identified was “News Media,” perhaps indicating the use of fake news articles to trick targets into clicking on spyware links.  An example of one such attack in action is the targeting of Mexican journalist Rafael Cabrera (Section 7.1).

We also noted the prevalence of themes we had seen in other spearphishing attacks, e.g., online accounts, document sharing, shipment tracking, corporate account portals. Another common theme was ISPs, perhaps because a target may trust an SMS appearing to come from an ISP or Telco they subscribe to.

Figure 12: Most commonly recurring domain name themes.

Alarmingly, some of the names suggested a willingness on the part of the operators to impersonate governments and international organizations. For example, we found two domain names that appear intended to masquerade as an official site of the International Committee of the Red Cross (ICRC): and

We also identified the domain which may be a lookalike for, a website belonging to Teleperformance, a company that has managed UK visa application processing in many countries.

Figure 13: Screenshot from an article published by the UK Government on how to apply for a visa.

Visa applicants are required to visit the legitimate website as part of the online visa application process. We found similar evidence of government-themed sites hinting at Mexico and Kenya.

The following table provides further examples of themes found in the domain names.

Type Example Impersonating
News Media
Las Ultimas Noticias
Shipment Tracking FedEx
ISP / Telco
Vodacom (Mozambique)
Iusacell (Mexico)
Sabafon (Yemen)
Popular Online Platforms
Account Info. (Generic)
Government Portals
The Emirates Foundation
Visa Application Processing Portal for the UK (
Humanitarian organizations
International Committee of the Red Cross
Airlines, Generic
Turkish Airlines
The Pokemon Company

Figure 14: Examples of domain names and themes

We also examined the domain names for evidence of links to any specific country and found a range of countries.  Our criteria was whether the domain name contained the name of a telecom provider, ISP, local website, government service, geographic location, a country’s TLD, or the name of a country.

The UAE and Mexico dominate this list, although other countries are also worth noting, including: Turkey, Israel, Thailand, Qatar, Kenya, Uzbekistan, Mozambique, Morocco, Yemen, Hungary, Saudi Arabia, Nigeria, and Bahrain.

Figure 15: Country theme based on domain name.

Citizen Lab is refraining from publishing a full list of domain names at this time given the possibility that some domains may have been used in legitimate law enforcement operations.


6. Linking NSO Group Products to the Attack on Mansoor

In this section, we explain why we believe the attack on Ahmed Mansoor incorporated the use of NSO Group’s Pegasus product.  We explain how we connected the domain name in the link that Ahmed Mansoor received,, to a network of domain names that we had mapped out while working on the May 2016 Stealth Falcon report (Section 5). We also highlight links to the UAE.


6.1. Spyware Points to NSO Group’s Pegasus Solution

The final payload that we identified, test111.tar, contained several files, including libaudio.dylib, which appeared to be the base library for call recording, libimo.dylib, which appeared to be the library for recording chat messages from apps, and two libraries for WhatsApp and Viber call recording: libvbcalls.dylib, and libwacalls.dylib.  In each file, we found several hundred strings containing the text “_kPegasusProtocol,” the name of NSO Group’s solution.


Figure 16: “Pegasus” strings in the payload.


6.2. Historical Scanning Data Connects Mansoor Attack to NSO Group-linked Infrastructure

The links sent to Mansoor used the domain The network of 237 live IP addresses we mapped (Section 5) included, to which resolves, and which returns an SSL certificate for * The 237 IPs also included ( and (, which were the two C2 servers in the spyware used in targeting Mansoor.

However, the 237 IPs and related domain names that we mapped did not provide insight into the identity of the threat actor. The IP addresses all appeared to be associated with cloud VPS providers, which gave no clue as to the identities of the operators, and the WHOIS information was mostly private. We did note that several domain names had WHOIS registrants based in Israel (e.g.,,

We examined historical scanning data to see whether we could attribute the 237 IPs to a threat actor.  We noted that at least 19 of these IPs had previously returned a different distinctive Google redirect in response to a “GET /”.

\xef\xbb\xbf<HTML><HEAD><META HTTP-EQUIV="refresh" CONTENT=

Figure 17: Response to an HTTP GET exhibited by 19 IPs in historical scanning data (note that the first three bytes represent the unicode byte order mark — BOM).

These 19 IPs included an IP address that (later) resolved to, one of the C2 servers for the spyware sent to Mansoor.

We then searched the same historical data for other IP addresses that matched this same fingerprint.  Overall, between October 2013 and September 2014, we identified 83 IPs that matched the fingerprint.  We found several IPs of particular interest.  The IP address matched our fingerprint from October 2013 until April 2014.

HTTP/1.1 200 OK
Content-Type: text/html
Last-Modified: Tue, 04 Jun 2013 15:28:04 GMT
Accept-Ranges: bytes
ETag: "09a91b3861ce1:0"
Server: Microsoft-IIS/7.5
Date: Mon, 28 Oct 2013 21:23:12 GMT
Connection: close
Content-Length: 127
\xef\xbb\xbf<HTML><HEAD><META HTTP-EQUIV="refresh" CONTENT="0;URL=">

The domain name pointed to this IP address at the same time (from April 2013 to April 2016), according to DomainTools.  The registrant information for this domain is:

Registrant Street:         Medinat Hayehudim 85
Registrant City:           hertzliya
Registrant State/Province: central
Registrant Postal Code:    46766
Registrant Country:        IL
Registrant Phone:          972542228649
Registrant Email:

We also found two other IP addresses of interest that matched the fingerprint: and matched the fingerprint in March 2014.  The former was pointed to by from 2014-09-24 to 2015-05-06 (PassiveTotal), the latter was pointed to by from 2015-09-01 until present (DomainTools).  Both domains are registered to NSO Group.

Given these findings, we strongly suspected the network of domain names we uncovered was part of an exploit infrastructure for NSO Group’s mobile spyware.


6.3. Additional UAE Infrastructure

Recall that our first window into this infrastructure came from our Stealth Falcon research, when we identified the domain, fingerprinted it, and traced it to 237 live IP addresses that shared the same characteristics (Section 5.1).

Using PassiveTotal, we were able to further trace to seven other domains, indicating Stealth Falcon targeting that appeared to use NSO Group’s Pegasus solution in Qatar (, UAE (, which may be a fake mobile phone company based in the Emirate of Ajman), and Bahrain (  Based on our previously published research, we believe there is strong circumstantial evidence to support the conclusion that the operator of Stealth Falcon is connected to an entity within the UAE Government.

We also identified five .ae TLDs that all shared the same registrant name (“Gerald Binord”), which may have been used to target people in the UAE.  We further identified another group of domains including (“Daman Health” is a UAE-based health insurer) and, which also included a domain, suggesting an operator that is targeting both UAE and Turkey targets.


7. Evidence of Other Targets

In two cases, Mexico and Kenya, we found evidence of other targets who may have been targeted with NSO Group’s Pegasus, based on messages they sent or received containing links that involve domain names we traced to what appears to be a mobile attack infrastructure associated with NSO Group’s Pegasus (see Section 5: Tracking a Mobile Attack Infrastructure).


7.1. Mexico: Politically Motivated Targeting?

In the case of Mexico, one target appears to be the journalist Rafael Cabrera, who recently reported on the Casa Blanca controversy, a reported conflict of interest involving the President and First Lady of Mexico.  On August 30, 2015 the journalist Cabrera tweeted that he had received suspicious messages purporting to come from Mexican television station UNO TV.  His tweet included screencaptures of the messages, which said that Mexico’s Presidency was considering defamation claims and imprisonment of reporters related to the Casa Blanca report that Cabrera had worked on.

Terms of Use | Copyright © 2002 - 2016 CONSTITUENTWORKS SM  CORPORATION. All rights reserved. | Privacy Statement