top of page

The Worm Inside the Apple: How APT29 Exploited Patched Vulnerabilities to Steal Browser Secrets

6 nov
7 min de lectura

The apple was beautiful.

Its red skin glistened under the light. Its surface was smooth, its shape perfect.

There was no visible sign of danger.

But beneath that flawless exterior, something was moving.

A worm.

It had found a tiny weakness in the fruit’s protective skin.

Once inside, it began tunneling through the flesh, moving closer to the core.

The apple still looked healthy from the outside.

But its defenses had already been breached.

The danger wasn’t what the apple revealed. It was what remained hidden beneath its surface.

That image captures the threat described in a campaign attributed to APT29, also known as Cozy Bear and Midnight Blizzard, with moderate-to-high confidence.

The operation reportedly exploited previously patched browser and Apple vulnerabilities to deliver information-stealing capabilities.

On November 4, 2026, CISA added CVE-2024-27834 to its Known Exploited Vulnerabilities catalog, confirming active exploitation of the flaw.


Phase 1 — The Perfect Apple


Apple devices incorporate multiple security mechanisms intended to protect users against unauthorized code execution and exploitation.

One of those mechanisms is Pointer Authentication, commonly abbreviated as PAC.

Pointer Authentication helps protect certain software pointers against unauthorized manipulation.

By making it more difficult to redirect program execution through corrupted pointers, PAC adds a layer of protection against some exploitation techniques.

But like any security mechanism, its effectiveness depends on the integrity of its implementation.

A vulnerability that allows an attacker to bypass PAC can weaken this protective layer.

The flaw at the center of the CISA alert is:

CVE-2024-27834 — CVSS 5.5

This vulnerability involves improper authentication and can allow an attacker with arbitrary read-and-write capability to bypass Pointer Authentication.

It is important to understand the prerequisite.

The vulnerability does not, by itself, mean that any website can immediately take control of an Apple device.

The attacker must already possess the required memory access capability.

Its danger becomes clearer when it is combined with another vulnerability in an exploit chain.

The apple’s skin was designed to resist intrusion. But the worm had discovered a weakness in one of its protective layers.


Phase 2 — The Worm Finds Its Way In


The campaign described by Sekoia used multiple methods to deliver malicious JavaScript to potential victims.

Rather than relying on one attack website, the operators reportedly used three pathways:

  • Compromised legitimate websites.

  • Fake websites impersonating popular destinations.

  • A supply-chain compromise involving Plerdy SEO Tracker.

Each pathway created an opportunity to expose visitors to attacker-controlled content.

A compromised legitimate website could appear completely normal to users.

An impersonation site could imitate a familiar online service.

A compromised third-party script could introduce malicious content into websites that depended on the affected supplier.

The attacker did not necessarily need to persuade every victim to install an application.

Instead, malicious JavaScript could be delivered through the browsing experience itself.

The worm didn’t need to tear the apple apart. It only needed to reach the fruit through a vulnerable point in its surface.


Phase 3 — The Worm Examines the Fruit


Before attempting exploitation, the malicious JavaScript reportedly profiled the visitor’s device.

This allowed the attackers to assess the environment and determine whether it might be suitable for the exploit chain.

Browser exploitation can depend on factors such as software versions, operating system characteristics and available security protections.

An exploit designed for one configuration may fail against another.

Profiling therefore helps attackers identify potentially vulnerable systems.

The supplied reporting does not specify every attribute collected during this stage.

But the purpose is clear: the attacker wanted to determine whether the visitor’s device presented an exploitable opportunity.

The worm didn’t burrow blindly. It searched for the softest point in the apple before moving toward the core.


Phase 4 — Breaking Through the Skin


The reported exploit chain involved a WebKit remote code execution vulnerability:

CVE-2025-43529

WebKit is the browser engine used by Safari and other Apple software.

A successful remote code execution exploit can provide an attacker with a foothold in the affected software environment.

The campaign also involved the Pointer Authentication bypass:

CVE-2024-27834

These vulnerabilities served different roles.

The WebKit flaw was associated with gaining code execution.

The PAC bypass could help defeat a security mechanism that would otherwise obstruct further exploitation.

The source article contains an apparent identifier inconsistency, repeating CVE-2025-43529 for both flaws in one sentence. Its earlier description, however, identifies CVE-2024-27834 as the Pointer Authentication bypass.

The attack was described as a zero-click chain, meaning that once the malicious content was encountered, no additional victim interaction was required to trigger the reported exploitation sequence.

The exact outcome still depended on the device being vulnerable and the exploit succeeding.

The worm first found a way through the skin. Then it overcame another barrier protecting the fruit’s interior.


Phase 5 — Feeding on the Core


The reported payload targeted browser cookies and device information.

Browser cookies can contain information used by websites to maintain sessions and remember user preferences.

Some cookies are associated with authenticated sessions.

If an attacker obtains usable session-related data, it may help facilitate unauthorized access to accounts, depending on the service’s security controls.

Not every cookie is an authentication token, and possession of browser data does not automatically grant access to every account.

Nevertheless, information stored in a browser can be valuable to an espionage operator.

Device information may also help attackers understand the victim’s environment or support further targeting.

The reporting does not establish how many devices were successfully compromised or how much information was stolen.

What it describes is an operation designed to harvest valuable data after exploiting vulnerable systems.

The worm wasn’t interested in the apple’s appearance. It wanted to reach the valuable material hidden inside.


Phase 6 — The Parasite Behind the Attack


Sekoia attributed the reported activity to APT29 with moderate-to-high confidence.

APT29 is also known as Cozy Bear and Midnight Blizzard.

The group is associated with Russia’s Foreign Intelligence Service, the SVR, and has been linked to sophisticated cyberespionage activity.

The reported operation combined several techniques:

Compromising legitimate websites to reach unsuspecting visitors.

Creating convincing impersonation sites.

Targeting a third-party service used by other websites.

Profiling devices before exploitation.

Combining vulnerabilities to bypass multiple security layers.

Deploying information-stealing capabilities.

The attribution assessment should be distinguished from a confirmed identification of every individual operator involved.

Moderate-to-high confidence indicates that researchers found substantial supporting evidence, while still acknowledging uncertainty.

The worm was not a random insect. Investigators associated the operation with an experienced intelligence organization.


Phase 7 — A Hole That Had Already Been Repaired


One of the most important details is that CVE-2024-27834 had been patched long before the November 2026 report.

Apple addressed the flaw in May 2024.

The relevant fixes included:

  • iOS 16.7.8 and iPadOS 16.7.8.

  • iOS 17.5 and iPadOS 17.5.

  • macOS Sonoma 14.5.

  • tvOS 17.5.

  • watchOS 10.5.

  • Safari 17.5.

The vulnerability had previously been demonstrated as a zero-day at Pwn2Own Vancouver in March 2024.

Its later exploitation illustrates why patch management remains essential.

Once a vulnerability becomes publicly known, attackers may continue searching for devices that have not received the relevant fixes.

Older software installations can remain exposed even when the manufacturer has already provided a remedy.

The hole in the apple’s skin had been identified and repaired. But some apples were still carrying the old weakness.


Phase 8 — The Rotten Supply Chain


The involvement of Plerdy SEO Tracker highlights another important aspect of the campaign.

Websites often rely on third-party JavaScript for analytics, optimization and other functionality.

These dependencies can provide legitimate business value.

But they also introduce trust relationships.

If an attacker compromises a supplier’s code delivery mechanism, malicious content may reach websites that did not directly experience an intrusion.

This is the essence of a software supply-chain risk.

The supplied article does not establish the full scope of the Plerdy compromise or the number of downstream victims.

Nevertheless, the reported pathway illustrates how attackers can use trusted software relationships to distribute malicious code.

The worm didn’t have to reach every apple individually. Contaminating part of the supply chain could expose multiple fruits to the same threat.


Phase 9 — CISA Finds the Worm


CISA added CVE-2024-27834 to its Known Exploited Vulnerabilities catalog on November 4, 2026, according to the report.

The KEV catalog identifies vulnerabilities for which evidence of exploitation in the wild exists.

This is important because the flaw carries a medium-severity CVSS score of 5.5.

A medium-severity vulnerability may still represent significant operational risk when used as part of a broader exploit chain.

Attackers do not necessarily depend on one critical vulnerability to compromise a device.

They may combine several weaknesses, each serving a different purpose.

In this case, the reported chain paired a browser exploitation capability with a bypass of an Apple security protection.

For U.S. Federal Civilian Executive Branch agencies, the remediation deadline is November 18, 2026.

The worm was no longer a theoretical possibility. Security authorities had evidence that the weakness was being exploited.


Phase 10 — Protecting the Apple Before the Worm Gets In


The most important defensive measure is to ensure affected devices have received the necessary security updates.

Organizations should address the vulnerabilities involved in the reported exploit chain rather than focusing exclusively on CVE-2024-27834.

Additional measures include:

Update operating systems and browsers. Install supported Apple security releases and keep browser software current.

Identify outdated devices. Prioritize systems missing historical patches or running unsupported versions.

Review third-party JavaScript. Website operators should understand which external scripts their websites load and assess the security of those dependencies.

Monitor suspicious browser activity. Investigate unexpected execution behavior, unusual connections and other indicators supported by endpoint telemetry.

Protect authentication sessions. Use appropriate account protections and revoke potentially exposed sessions when investigation supports doing so.

Investigate suspected exploitation. Review available logs and forensic evidence when vulnerable devices may have encountered malicious web content.

Apply layered security. Endpoint monitoring, least privilege and appropriate browser protections can reduce the impact of exploitation.

The supplied reporting does not provide a comprehensive list of malicious domains or confirmed payload indicators.

Therefore, organizations should rely on validated threat intelligence and case-specific evidence when investigating potential compromise.

The best defense isn’t waiting until the apple begins to rot. It’s repairing the vulnerable skin and protecting the fruit before the worm enters.


The Final Bite — The Apple Looked Perfect


The reported APT29 campaign demonstrates how attackers can combine previously patched vulnerabilities with malicious web content to target valuable information.

Compromised legitimate websites, impersonation pages and a supply-chain compromise reportedly delivered malicious JavaScript.

Device profiling helped identify potentially vulnerable visitors.

A WebKit vulnerability and a Pointer Authentication bypass formed part of the reported exploitation chain.

The intended result included theft of browser cookies and device information.

CISA’s addition of CVE-2024-27834 to its KEV catalog confirms that the flaw is being actively exploited.

But the wider lesson goes beyond one vulnerability.

Security protections are layered for a reason.

When attackers find a way through one layer, they may exploit additional weaknesses to move deeper into a system.

And when devices remain unpatched, old vulnerabilities can continue providing opportunities long after fixes become available.

The apple still looked beautiful.

Its skin remained bright.

Nothing on the surface revealed the tunnels forming beneath it.

But the worm had already found a way in.

Because the most dangerous apple isn’t always the one that looks rotten.

It’s the one that looks perfectly safe while something is already feeding on its core.



The Hacker News


 
 
 

Comentarios


bottom of page