APT29 watering holes turn mobile patch lag into the attack surface
Sekoia attributes a watering-hole campaign serving iOS and Android exploit chains to APT29. Every flaw had been fixed before the campaign began; the exposure was devices that had not taken the fix.
Patched exploits, unpatched phones
A Russian intelligence campaign against mobile devices has been running on exploits that were already fixed. On 4 November Sekoia’s Threat Detection & Research team published its analysis of a watering-hole operation found in mid-October 2026. It assesses with moderate to high confidence that APT29, which it attributes to Russia’s SVR, or one of its subgroups conducted it [1]. The operation served three exploit chains to iPhone and Android visitors of compromised or cloned websites. Sekoia states that every vulnerability in those chains was patched before the campaign began, and that “a user running an up-to-date operating system is safe from these attacks.” [1] The finding for defenders is narrow and uncomfortable. The attack surface was patch lag, not novel capability.
What Sekoia found
Sekoia describes three delivery routes [1]. The first was JavaScript injected into legitimate sites, including a Ukrainian gas producer, a US chemical industry trade association, a far-right European political party, a far-right Czech movement and a Bulgarian military-related organisation. The second was lookalike domains that reverse-proxied real sites and appended script to every page. One mirrored the US America250 anniversary initiative. Another mirrored a London luxury hotel close to UK government buildings, which Sekoia suggests may have been aimed at diplomatic delegations and prominent guests [1]. The third was a supply-chain compromise of Plerdy, a Ukrainian web analytics tracker, between 27 August and 3 September 2026 [1].
The scale of the Plerdy exposure is not settled. Sekoia’s own report says “hundreds” of sites in its key takeaways and introduction, and “thousands” elsewhere [1]. Help Net Security reported that the tracker runs on thousands of mostly Ukrainian sites, including army, special forces and military equipment sites [2]. Infosecurity Magazine reported that thousands of sites load Plerdy but that Sekoia says hundreds were exposed [3]. The figures differ and the report does not reconcile them. Sekoia did not say how many devices were compromised [3].
Every route fed the same profiling script. Sekoia counted 61 collectors producing 394 data fields, appended to roughly 2.3 MB of minified library code. Only three fields could block delivery [1]. Visitors then received a platform-specific chain:
- iOS 16.7: two CVEs, including CVE-2024-27834, a WebKit pointer authentication bypass, used to steal cookies. Sekoia says the chain should work from iOS 16.0 to 17.4 [1].
- iOS 18.5: five CVEs from the DarkSword kit, taking messages, Keychain items, location, health data and photos [1].
- Android Chrome 139 to 145, excluding 143: CVE-2026-3910 in Chrome plus CVE-2025-27038 in the Adreno GPU driver, taking Chrome cookies, saved logins, history and Wi-Fi configuration [1].
None of the payloads persist [1]. Sekoia has withheld delivery and exfiltration hosts and detection rules from the public report and offers them to CERTs and law enforcement under TLP:AMBER. It is working with national CERTs, including CERT-UA, to identify victims [1][2].
Attribution and lineage
Sekoia’s attribution rests on technical overlap with a 2024 watering hole on Mongolian government sites, artefacts of a 2025 APT29 operation found on one compromised backend, infrastructure habits and victimology [1]. Google TAG assessed the 2024 Mongolian activity, which also stole cookies, as linked to APT29 with moderate confidence. It found the exploits matched ones previously used by the commercial surveillance vendors Intellexa and NSO Group [4]. The new campaign differs in one respect: it had no hardcoded target filter and took any cookies in the browser [1][3].
The iOS 18 chain has a documented history. GTIG reported in March 2026 that DarkSword, a six-vulnerability chain, had been used since at least November 2025 by several actors. UNC6748 targeted users in Saudi Arabia. Customers of the Turkish vendor PARS Defense targeted users in Turkey and, from January 2026, Malaysia. UNC6353, a suspected Russian espionage group, compromised Ukrainian sites [5]. Lookout assessed UNC6353 as well funded but technically less sophisticated, with possible links to exploit brokers [6]. The sources differ on the affected range: GTIG gives iOS 18.4 to 18.7, while Lookout and iVerify give 18.4 to 18.6.2 [5][6][7]. iVerify estimated about 221 million devices in the narrower band and stated that the figure is uncertain [7]. Sekoia’s analysis suggests APT29 obtained its exploits from a third party [3].
What it means
The cost of mobile exploitation has fallen. Sekoia’s conclusion, as reported by Help Net Security, is that packaged n-day kits lower the cost and skill required and that reuse by state groups will likely increase [2]. GTIG made the same point about proliferation across actors of differing geography and motivation [5]. A chain sold or leaked once does not stay with its first buyer.
The patch dates define the window. Apple fixed CVE-2024-27834 in May 2024 [9]. It fixed CVE-2025-43529 and CVE-2025-14174 in iOS 18.7.3 on 12 December 2025, noting possible exploitation against targeted individuals [8]. The Chrome flaw was fixed in Chrome 146 in March 2026, with Google aware of an exploit in the wild [10]. The Adreno flaw took longer. Qualcomm shipped fixes to manufacturers in May 2025 and warned of limited, targeted exploitation [11]. The Android bulletin carried it only at the 2025-08-05 patch level [12][13]. An Android phone’s exposure therefore depends on the manufacturer’s update cadence as much as on the user. Help Net Security reported that CISA added CVE-2024-27834 to its Known Exploited Vulnerabilities catalogue on 4 November, without attributing the exploitation [2].
Hospitality is a recurring vector for this service. Microsoft reported in July 2026, with an October update, that Storm-2945, which it assesses as a sub-cluster of Midnight Blizzard, manipulated hotel and conference captive-portal traffic to phish credentials and deliver malware, with indications of Android targeting [14]. The cloned hotel site in Sekoia’s report fits the same interest in travelling officials and delegations [1].
What to do
- Enforce minimum OS versions and patch levels for managed mobile devices, and block access to corporate resources below them. On Android, require the 2025-08-05 patch level or later and Chrome 146 or later [10][12].
- Identify devices that cannot run a current OS. iPhone 8 and iPhone X stop at iOS 16. Confirm they carry iOS 16.7.8 or later and plan to remove them from sensitive roles [9].
- For high-risk staff, assess Lockdown Mode. Apple describes it as “optional, extreme protection” and notes that a device in Lockdown Mode cannot enrol in MDM, so plan management around that [15]. GTIG recommends it where updating is not possible, and iVerify reports the DarkSword exploits would not work against it without further bypasses [5][7].
- Because the payloads take cookies and credentials and do not persist, treat suspected exposure as session compromise. Revoke sessions and tokens and rotate credentials rather than relying on device forensics alone [1].
- Inventory third-party scripts on your own sites. The Plerdy compromise turned an analytics tag into a delivery channel for every site that loaded it [1].
- Treat hotel, conference and guest Wi-Fi as untrusted. Use managed connectivity, passkeys and Conditional Access, and allow device code flow only where needed [14].
- CERTs and incident teams in affected sectors can request Sekoia’s TLP:AMBER indicators and samples [1].
Cyber operations outlook
A first-tier intelligence service no longer needs zero-days to reach phones. It needs a commodity chain, a trusted script and a population of devices a few months behind. GTIG’s record of DarkSword use against users in Malaysia shows the same tooling is already in circulation in the region [5]. For any organisation whose staff travel, negotiate or meet officials, mobile patch compliance belongs in the threat model. It should be measured and reported, not assumed.
Sources
Every R3KONX article cites its primary material. 15 sources, in order of first citation. Links open the original publication.
- Poisoned source: APT29 watering holes targets mobile devices with n-day exploits Sekoia · 2026-11-04
- Russian hackers target iOS and Android users with n-day exploits Help Net Security · 2026-11-04
- APT29 watering holes target unpatched iPhones and Android devices Infosecurity Magazine · 2026-11-04
- State-backed attackers and commercial surveillance vendors repeatedly use the same exploits Google Threat Analysis Group · 2024-08-29
- The Proliferation of DarkSword: iOS Exploit Chain Adopted by Multiple Threat Actors Google Threat Intelligence Group · 2026-03-18
- Attackers Wielding DarkSword Threaten iOS Users Lookout · 2026-03-18
- Inside DarkSword: A New iOS Exploit Kit Delivered Via Compromised Legitimate Websites iVerify · 2026-03-18
- About the security content of iOS 18.7.3 and iPadOS 18.7.3 Apple · 2025-12-12
- About the security content of iOS 16.7.8 and iPadOS 16.7.8 Apple · 2024-05-13
- Google Chrome security advisory (AV26-235) - Update 1 Canadian Centre for Cyber Security · 2026-03-13
- Qualcomm flags exploitation of Adreno GPU flaws, urges OEMs to patch urgently SecurityWeek · 2025-06-02
- Android Security Bulletin - August 2025 Android Open Source Project · 2025-08-04
- Android's August 2025 update patches exploited Qualcomm vulnerability SecurityWeek · 2025-08-05
- CaptiveCrunch: Midnight Blizzard targets travelers worldwide for malware delivery and credential theft Microsoft Threat Intelligence · 2026-07-31
- About Lockdown Mode Apple · 2026-09-18
Researched and written by the R3KONX Analysis Desk from the cited primary material. Attribution of the campaign to APT29 is Sekoia's assessment and rests on single-vendor research. CISA's 4 November Known Exploited Vulnerabilities notice could not be retrieved and is cited via Help Net Security; Qualcomm's June 2025 security bulletin could not be retrieved and is cited via SecurityWeek. Corrections: event@r3konx.asia.
