Sekoia researchers have linked a large-scale watering-hole campaign to Russia-aligned APT29 with moderate-to-high confidence. It used patched n-day exploits against iPhones and Android phones that visited compromised or cloned websites, including those of a Ukrainian gas producer and a U.S. chemical industry trade association.
What happened: the APT29 watering-hole campaign at a glance
Sekoia’s Threat Detection & Research team detected the campaign in mid-October 2026 and attributes it, with moderate-to-high confidence, to APT29, also tracked as Midnight Blizzard, Cozy Bear and The Dukes. Security press coverage of the report ran on November 4, 2026. The campaign used compromised legitimate sites, cloned lookalike domains and a poisoned third-party analytics script to reach iOS and Android visitors, according to BleepingComputer and GBHackers.
Confirmed by Sekoia’s research, as reported:
- Compromised legitimate sites included a Ukrainian gas producer, a U.S. chemical industry trade association and a Bulgarian military-related organization. Visitors also hit a compromised far-right Czech party site.
- Lookalike domains mirrored the official America250 site and Raffles London at The OWO hotel.
- A Ukrainian web analytics service, Plerdy, had its SEO tracker modified between August 27 and September 3, 2026. Thousands of sites, mostly Ukrainian, loaded it.
- Apple and Google have patched every vulnerability used. Fully updated devices are not exposed.
Not publicly stated, as far as we could verify: the number of infected devices, the identity of individual victims, and whether any operational technology network was reached. Names of the affected organizations beyond the descriptions above were not disclosed in the coverage we reviewed.
Root cause: patched flaws on devices that were not updated
The root cause on the device side is unpatched software. Every exploit in the campaign targets a known, already-fixed vulnerability (an n-day), so the attack only works on iPhones and Chrome-for-Android builds that are behind on updates. On the delivery side, the root causes are compromised web content: injected JavaScript on legitimate sites, reverse-proxy clones of trusted brands, and a tampered third-party script. How the attackers first broke into each website or into Plerdy’s infrastructure has not been detailed in the coverage we reviewed.
Attack methodology: three delivery vectors, one fingerprinting script
Initial access: how victims reach the exploit
- Direct injection. A few lines of JavaScript were added to page templates of legitimate sites, which pulled a script from attacker-controlled infrastructure (Cryptika).
- Lookalike domains. america250[.]holiday and theowo[.]club act as adversary-in-the-middle reverse proxies that relay the real sites’ content. Sekoia suspects spear-phishing lures aimed at diplomats and officials.
- Supply-chain compromise. Between August 27 and September 3, 2026, the tracker file served from a.plerdy[.]com was modified so every site loading it also loaded the attacker’s script.
Profiling and exploit delivery
All three vectors load a script Sekoia calls UltimateFingerprinter, hidden behind roughly 2.3 MB of dead AngularJS code. It collects 394 fields through 61 collectors and posts them to a server. The server returns an exploit only if basic checks pass, such as a plausible phone screen size and a non-zero touch-point count. Sekoia saw no sign that the rest of the fingerprint affected delivery (GBHackers).
Sekoia found four more vulnerabilities in unreachable code or alternate paths that were not used in the analyzed chains. Stolen data goes to ad.starx-net[.]com:8881/telemetry/v12. None of the payloads established persistence, so a reboot ends the infection until the device visits a compromised page again. The campaign collects any cookie, whereas APT29’s 2024 Mongolian campaign targeted only a hard-coded list of webmail and login sites.
A note on terminology: the chains are often called zero-click because they need no tap, download or prompt after the page loads. The victim must still visit a page that serves the exploit. Lateral movement and privilege escalation on enterprise networks were not part of the reported activity; the goal observed was session and credential theft from the phone itself.
Threat actor and attribution: what is known about APT29
Attribution here is a private-sector assessment, not an official government statement. Sekoia assesses APT29 with moderate-to-high confidence. APT29 is widely linked to Russia’s Foreign Intelligence Service (SVR), and the U.S. and UK governments have attributed Midnight Blizzard to Russian intelligence in past advisories. We found no government attribution of this specific campaign.
Evidence Sekoia cites:
- Files on one compromised site matched a private report about a 2025 APT29 watering-hole campaign, which a partner supplied.
- Tactics match the 2024 APT29 campaign against Mongolian government sites reported by Google TAG.
- Infrastructure overlaps and use of multiple autonomous systems, plus victimology aligned with Russian strategic interests (Ukraine, the U.S., Europe). Sekoia researcher Amaury-Jacques Garçon described the target list as unusually scattered at first glance, with the full picture only visible when the delivery chain is considered (GovInfoSecurity).
Context that is relevant but separate: Google described DarkSword in March 2026 as an iOS exploit chain adopted by commercial surveillance vendors and suspected state actors, and noted that a suspected Russian espionage cluster tracked as UNC6353 used it against Ukrainian sites. Sekoia’s report does not equate UNC6353 with APT29, and we do not either. Google TAG’s 2024 report found APT29 reusing exploits that were identical or strikingly similar to those of NSO Group and Intellexa, and said it did not know how they were acquired (SecurityWeek). Whether the same supply route applies to DarkSword is unknown.
Unknowns: operator identities, the exact objective for each victim set, and whether other actors share the exploit kit.
Impact assessment: stolen sessions, not service outages
No service disruption, ransomware, financial loss figure or regulatory action has been reported for this campaign. The impact is espionage-oriented and mostly potential: stolen authentication cookies can let an attacker reuse an authenticated session and reach webmail without a password, as GBHackers notes in its coverage. Chain B goes further and can pull messaging databases, Keychain secrets and location data from the phone. The number of compromised devices is not public. Sekoia is coordinating with the CERTs of affected countries on victim identification and possible infrastructure disruption, per the same coverage.
Reputational exposure falls mainly on the website owners whose pages served the script, and on Plerdy’s customers. The site owners were victims of the intrusion, not the intended targets, which is how watering-hole operations normally work.
IT, OT and critical infrastructure implications
This is a mobile and web-supply-chain incident, not an attack on control systems. There is no evidence in the reporting we reviewed of any ICS, SCADA or plant-network compromise. It still matters to industrial security teams for three reasons.
- Sector overlap. A gas producer’s and a chemical trade association’s websites were used as bait or injection points. That fits state-aligned interest in energy and chemicals, but the reporting does not say why those sites were chosen, and Sekoia notes the victim list looks scattered.
- Phones are the bridge to OT. Engineers and operators use phones for remote-access apps, MFA approvals, vendor chat and email. A stolen session cookie or Keychain secret on a personal or corporate phone can become an entry point to IT and, through jump hosts and remote-access tools, to OT environments. That path is a risk assessment, not a reported outcome here.
- Third-party scripts are an OT-adjacent exposure. Organizations that host public sites, supplier portals or customer dashboards for industrial products load analytics and tracking scripts. The Plerdy compromise shows a one-week tampering of a widely loaded script can reach thousands of sites.
Incident response and recovery status
The response so far is research-led rather than victim-led. Sekoia worked with CERT-UA and an unnamed partner to investigate, and says it is working with the CERTs of affected countries on victim identification and possible takedown of the infrastructure (Mallory, GBHackers). We found no public statements from the affected website owners, from Plerdy, or from Apple or Google about this campaign. Apple and Google fixed all the exploited flaws earlier, including backports to older iOS releases, per BleepingComputer. Whether the injected scripts have been removed from every compromised site and whether the attacker infrastructure is down is not confirmed.
Latest developments (as of November 4, 2026)
- Sekoia’s report, titled “Poisoned Source: APT29 Watering Holes Target Mobile Devices with N-Day Exploits”, is on the Sekoia blog. We could not open it directly; the technical details above come from press coverage that quotes it. Publication date: one secondary report dates it to October 29, 2026, while broader coverage started November 4.
- BleepingComputer connects the actor to recent hotel Wi-Fi attacks. Those are a separate activity set.
- Victim notification, takedown progress and any government advisory are still open. This article will need an update if CERT-UA, CISA or Apple or Google publish guidance.
Security recommendations: how to defend against mobile watering-hole attacks
Patch and verify mobile fleets (highest priority)
- Update iOS and Chrome for Android. Sekoia says none of the chains work on updated devices. Use MDM to list iPhones still on old releases, in particular iOS 16.x, and Android devices running Chrome 139 to 145.
- Where updates are impossible, Google recommends Lockdown Mode on iPhones, as GBHackers reports.
- Treat unsupported phones as untrusted for access to email, VPN, remote-access and OT-adjacent apps.
Hunt and contain
- Search DNS, proxy and mobile-threat-defense logs for starx-net, flux-telemetry and clouds-stacks domains, plus america250[.]holiday, theowo[.]club and adsprism-stat[.]com. Defang indicators in tickets and only re-fang in controlled platforms.
- Review any use of the Plerdy tracker (a.plerdy[.]com) across your web properties, especially between August 27 and September 3, 2026.
- If a device may have visited a compromised page: reboot it (no persistence was reported), update it, then revoke and reissue sessions for webmail, SSO and messaging apps, and rotate Wi-Fi and saved credentials.
Reduce the damage of cookie theft
- Shorten session lifetimes and bind tokens to devices where your identity provider supports it. Use conditional access that checks device compliance.
- Prefer phishing-resistant MFA, and watch for session replay from new IPs or user agents.
For website owners and OT vendors
- Inventory every third-party script on public sites. Use Subresource Integrity where a script is static, a strict Content Security Policy, and file-integrity monitoring on page templates.
- Keep operator and engineer phones out of the same trust tier as OT jump hosts. Require managed, patched devices for remote access to plant networks.
- Add mobile browser compromise to tabletop exercises, including who can revoke sessions and how fast.