Mobile espionage: why ngCERT’s warning matters to African leaders
Compromised sites, lookalike domains and a poisoned analytics script delivered already-patched iOS and Android exploit chains. No African victim is established, but mobile sessions and unsupported devices require a structured response.
Severity
4Affected country
NGSector
Cross-sectorPublished
21 November 2026
Our score measures operational relevance to Africa — not the global virality of the story.

Contents · 6
A Nigerian warning about an external campaign
Nigeria’s ngCERT published a high-level alert on 18 November 2026 concerning an espionage campaign targeting iOS and Android users. The advisory draws on research published by Sekoia on 4 November describing three delivery mechanisms: code injected into compromised legitimate websites, domains resembling well-known sites and temporary compromise of a third-party analytics script.
When a vulnerable phone loaded the page, a script collected browser and device characteristics and selected a matching exploit chain. Sekoia says the final payloads could steal cookies, Wi-Fi passwords and, in selected iPhone scenarios, extensive device data. No voluntary application download was required after opening the page.
The phrase “zero click” needs precision. A victim did not have to click an attachment or install a package, but the browser still had to load a compromised site or script. That distinction directs defenders toward the right evidence: web history, DNS resolution, proxy records, JavaScript dependencies and operating-system versions rather than a visible malicious application.
What is established and what remains assessed
Sekoia attributes the campaign, named Poisoned Source, to APT29 with moderate-to-high confidence. That remains the company’s technical assessment. Public material supports examination of recovered infrastructure and exploit chains, but it is not judicial identification of individual operators. Africa Cyber Review therefore does not present the attribution as finally resolved fact.
The described chains exploit eight vulnerabilities already patched by Apple, Google or relevant component vendors. iOS references include CVE-2025-43529, CVE-2024-27834 and CVE-2026-20700. The Android chain combines browser and graphics-component issues. The essential operational point is that users who installed updates appropriate to their devices are not exposed to the observed chains as described.
No reviewed source confirms an African victim or African hosting of the campaign infrastructure. ngCERT’s warning is not a declaration of compromise in Nigeria. It warns that a global, reusable method could reach Nigerian or other African users when they visit a compromised page from an insufficiently patched device.
A phone has become an access key
For executives, public officials, journalists, system administrators and financial managers, a phone contains far more than messages. It commonly holds email sessions, recovery codes, authenticator applications, bank interactions, crisis groups and sensitive contacts. Cookie theft may enable reuse of a web session without immediately knowing the account password.
In African organisations, the same device may support personal and professional use, two SIM cards and several payment accounts. That concentration raises its value. It also complicates response: wiping too quickly can destroy useful evidence, while continued use may leave compromised sessions active.
Uneven update delivery increases risk. Android phones do not all receive fixes at the same time, and some affordable models leave support quickly. A user may believe the device is current because no notification appears while its patch level remains old. An iPhone may similarly remain on an older branch for compatibility or storage reasons.
Third-party scripts are security dependencies
Sekoia’s research describes compromise of a Plerdy analytics script between 27 August and 3 September. Customer pages could load modified code without any visible content change. The episode illustrates a broader risk for African websites: analytics, advertising, support, payment widgets and external fonts execute code in visitors’ browsers.
A site can therefore become a delivery path without direct compromise of its own server. Publishers should inventory external scripts, remove those no longer needed, apply a suitable Content Security Policy and monitor change. Subresource Integrity can help with static files whose content does not change, but is not automatically suitable for every dynamic service.
Lookalike domains provide another route. African brands, authorities and media organisations need monitoring for registrations close to their names, strong protection for DNS and certificate accounts, and a rapid reporting process. The goal is not to block every similar domain, but to qualify those that copy content, proxy the real site or target its users.
Response for organisations and high-risk users
The first action is to verify operating-system, browser and patch versions, then install the latest update actually offered by the manufacturer. Where a device no longer receives fixes, organisations need to restrict sensitive access or schedule replacement, starting with highly privileged profiles.
If credible exposure is identified, updating closes known vulnerabilities but does not invalidate cookies or tokens already stolen. Sensitive sessions should be revoked from a trusted device, passwords and recovery factors reassessed, and account sign-ins reviewed. A serious response separates evidence preservation, account containment and device restoration.
Teams can take the following steps:
- inventory phones with access to administrative, financial and communications accounts;
- enforce a minimum OS and patch level rather than accepting a generic “up to date” claim;
- keep highly sensitive accounts off unmanaged devices;
- retain DNS, proxy, identity and cloud-access logs long enough to reconstruct a visit;
- revoke sessions and tokens when compromise is suspected, not only change passwords;
- inventory and monitor third-party scripts loaded by organisational websites;
- maintain a tailored process for journalists, executives and exposed staff.
The African lesson is practical
This alert matters not because of an assumed African victim or the name assigned to an operator. It matters because of the attack model: turning a familiar website or web dependency into an automated selection mechanism for vulnerable phones. That method bypasses advice limited to “do not download unknown apps.”
African organisations need to integrate mobile security with identity and web governance. Patched phones, revocable sessions, controlled third-party scripts and usable logs reduce risk more effectively than a generic warning asking users simply to be careful.
— ◆ —