Apple has reported zero successful spyware infections among iPhone users who activated Lockdown Mode, the company’s most aggressive defense against state-sponsored hacking. The claim carries weight at a time when commercial spyware vendors are selling surveillance tools to governments worldwide, and Apple itself has warned users across 91 countries that they may be targets. A closer look at the available evidence, including one high-profile case involving an Egyptian politician, suggests Lockdown Mode is delivering on its promise, but the feature’s strict trade-offs raise questions about whether it can protect the people who need it most.
What Lockdown Mode Actually Does
Apple introduced Lockdown Mode in late 2022 as an optional shield for users facing sophisticated digital threats. When activated, it strips away features that spyware typically exploits. Message attachments beyond basic images are blocked. Web browsing is restricted by disabling certain JavaScript compilation techniques. Wired connections to computers are refused unless the device is unlocked. FaceTime calls from unknown contacts are silenced. The result is a phone that works, but with significant limitations on everyday convenience.
That design philosophy is intentional. By shrinking the number of entry points available to attackers, Apple reduces the “attack surface” that spyware vendors rely on. Most commercial spyware, including tools like Predator and Pegasus, exploits complex features such as rich media rendering or web engine vulnerabilities to gain a foothold on a device. Lockdown Mode removes or restricts many of those features outright, making infection far harder even when attackers possess zero-day exploits.
The trade-off is real. Users in Lockdown Mode lose access to shared photo albums, certain font rendering, and some website functionality. For most people, these restrictions would be annoying. For journalists, activists, and political dissidents who face targeted surveillance, the calculation is different: a less convenient phone is better than a compromised one.
The Egyptian Case That Tested Apple’s Claim
The strongest public evidence supporting Apple’s assertion comes from a joint investigation by Citizen Lab at the University of Toronto and Google’s Threat Analysis Group. Researchers found that an Egyptian opposition figure, Ahmed Eltantawy, was targeted with Predator spyware. Predator, developed by the Cytrox consortium, is one of several commercial surveillance tools sold to government clients for use against specific individuals.
The attack against Eltantawy involved attempts to redirect his web traffic to a malicious server that would deliver the Predator payload. According to the same investigation, the effort likely failed because his iPhone was running in Lockdown Mode at the time. The mode’s restrictions on web engine behavior appear to have blocked the infection chain before it could execute, preventing the spyware from taking hold on his device.
This case matters because it is not a lab simulation. It represents a real-world attack by a well-resourced adversary against a specific political target, and Lockdown Mode held. Citizen Lab and Google TAG documented the technical details, providing outside verification that Apple’s defensive tool worked as intended in at least this instance.
It also illustrates how narrow the margin for safety can be. Eltantawy was reportedly under pressure and surveillance long before the attempted Predator infection. Had he not enabled Lockdown Mode when he did, the same infrastructure and exploit chain might have succeeded. The outcome depended not only on Apple’s engineering but also on a high-risk user making the right security choice at the right time.
Apple’s Broader Spyware Warnings
Apple’s confidence in Lockdown Mode sits alongside an increasingly urgent pattern of threat notifications. The company alerted users in 91 countries, including India, that they may have been targeted by what Apple called “mercenary spyware attacks.” Those alerts, sent directly to affected users, marked a shift in Apple’s language. The company previously described these incidents as “state-sponsored” attacks but moved to the term “mercenary” to reflect the commercial nature of the spyware industry.
The language change is not cosmetic. Calling the threat “mercenary” rather than “state-sponsored” more accurately describes the business model: private companies develop the spyware, and governments purchase and deploy it. That distinction matters for accountability. It names the commercial vendors as active participants rather than framing governments as the sole actors.
Apple did not publicly identify which spyware tools or vendors were involved in the 91-country warning. The company has historically been cautious about naming specific adversaries in its user notifications, instead directing recipients to enable Lockdown Mode and update their software immediately. That guidance underscores how central the feature has become to Apple’s strategy for defending users at the highest risk.
Why “Zero Breaches” Deserves Scrutiny
Apple’s claim that no Lockdown Mode user has been successfully hacked is significant, but it comes with important caveats that deserve honest examination. First, the company has not disclosed how many people have activated Lockdown Mode. Without that denominator, the claim is hard to evaluate statistically. If only a small number of users have enabled the feature, the absence of breaches could reflect limited exposure rather than impenetrable security.
Second, Apple’s statement relies on its own detection capabilities. If a spyware vendor developed an exploit that bypassed both Lockdown Mode and Apple’s monitoring systems, the company might not know about it. Security researchers have repeatedly demonstrated that even well-defended systems can harbor undetected compromises for months or years. The lack of observed breaches is encouraging, but it is not the same as a guarantee that no breaches exist.
Third, the commercial spyware industry adapts quickly. Predator and Pegasus represent the known threats, but new tools and techniques emerge regularly. A feature that blocks today’s attack chains may not stop tomorrow’s. Apple has updated Lockdown Mode with each iOS release, expanding its protections, but the arms race between defenders and attackers is continuous and asymmetric. Spyware developers need to find only one viable path in; defenders must close them all.
None of this means Apple’s claim is false. The Eltantawy case provides independent corroboration that Lockdown Mode stopped at least one sophisticated attack, and Apple has a business incentive not to overstate the feature’s success in a way that could be easily disproven. But treating the claim as proof of total invulnerability would be a mistake. Security is measured in degrees, not absolutes, and any tool that promises perfect protection should be met with skepticism.
The Adoption Gap Remains the Biggest Risk
The most pressing problem with Lockdown Mode is not whether it works. The evidence suggests it does. The problem is that the people who need it most may not know it exists or may not activate it in time.
Lockdown Mode is buried in iOS settings under Privacy and Security and requires a device restart to enable. Apple does not push it to users proactively unless they receive a threat notification. For a journalist in a country with aggressive surveillance practices, discovering Lockdown Mode after an infection is already underway would be too late. The feature is preventive, not curative; it blocks exploit chains but cannot retroactively remove spyware that has already been installed.
There is also a usability barrier. Turning on Lockdown Mode means accepting that some messages will not come through as expected, some websites will break, and some workflows will stop working. For people whose professional lives depend on fast communication and seamless collaboration, those costs are substantial. Many high-risk users already juggle multiple devices, secure messaging apps, and operational security practices. Adding another layer of friction can feel like a step too far.
That tension highlights a broader challenge for tech companies building tools for at-risk communities. The most secure configuration is rarely the most usable one. If Lockdown Mode is so restrictive that only a small fraction of potential targets can tolerate it, its protective value will be limited no matter how effective it is in theory.
What Effective Protection Would Look Like
Apple’s experience with Lockdown Mode points toward several ways the industry could better protect users facing mercenary spyware. First, awareness needs to move beyond one-off threat notifications. High-risk groups such as human rights defenders, opposition politicians, and investigative reporters would benefit from clear, localized guidance on when to consider Lockdown Mode and what trade-offs it entails.
Second, the line between “normal” and “high-risk” modes could be softened. If some of Lockdown Mode’s protections—such as stricter handling of message attachments or tighter controls on web content—were made available as granular options, more users might adopt them without committing to the full set of restrictions. That would expand the protective umbrella without forcing an all-or-nothing choice.
Finally, transparency will matter as the spyware landscape evolves. When Apple reports that no Lockdown Mode users have been successfully hacked, independent research like the Eltantawy investigation helps validate that message. Continued collaboration with external labs, and more detailed public accounting when attacks are detected, would help users and policymakers understand how well these defenses are holding up over time.
For now, Lockdown Mode appears to be doing what it was designed to do: dramatically raising the cost of infecting an iPhone with commercial spyware. The unanswered question is whether the people most in need of that protection will be able, and willing, to live with the compromises it demands.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
