Skip to content
  • BTC $59,519 −5.7%
  • ETH $1,649 −7.2%
  • SOL $68.81 −6.6%
  • BNB $549.58 −6.3%
  • XRP $0.9163 −5.8%
  • DOGE $0.0540 −8.0%
  • ADA $0.1410 −7.5%

Is the coruna exploit kit repurposing Operation Triangulation for new iOS attacks?

This analysis shows how coruna exploit kit repurposes Operation Triangulation to broaden iOS targeting, expanding the attack surface.

Article produced with artificial intelligence systems and published under the editorial responsibility of Amelia Tomasicchio. How we work

coruna exploit kit
Coruna exploit kit repurposes Triangulation for iOS attacks

Security researchers have linked the coruna exploit kit to a renewed wave of targeted iPhone attacks, reviving techniques first seen in Operation Triangulation.

From Operation Triangulation to the Coruna framework

On March 4, 2026, Google and iVerify disclosed a highly sophisticated exploit framework targeting Apple iPhone devices. According to Google, the toolkit was initially found in attacks by a customer of an unnamed surveillance vendor and later in watering-hole operations in Ukraine and financially motivated intrusions in China.

During that research, analysts uncovered a debug build of the toolkit that exposed internal exploit labels and the framework’s name: Coruna. Moreover, inspection showed the framework combined multiple already patched bugs with fresh weaponizations of CVE-2023-32434 and CVE-2023-38606, two vulnerabilities first observed as zero-days in Operation Triangulation.

Operation Triangulation itself is a complex mobile APT campaign against iOS devices. It was discovered after suspicious traffic appeared on a corporate WiFi network, originating from several compromised phones. The campaign relied on a sophisticated spyware implant and multiple zero-day exploits, with findings later presented by Kaspersky GReAT at the 37th Chaos Communication Congress (37C3).

Although full technical details for CVE-2023-32434 and CVE-2023-38606 have been public for some time, and other researchers independently developed exploits, analysts decided to scrutinize how Coruna implemented them. Some distribution URLs reported by Google were still live when the analysis started, which allowed collection, decryption, and full examination of all framework components.

During this analysis, researchers confirmed that the kernel exploit for CVE-2023-32434 and CVE-2023-38606 inside Coruna is in fact an updated build of the same exploit chain used in Operation Triangulation. However, the kit’s architecture also revealed several important evolutions that significantly broaden its reach.

A unified iOS exploit framework rather than a patchwork

Beyond the reused chain, Coruna contains four additional kernel exploits that were never seen in Operation Triangulation, including two that appeared only after that earlier campaign was exposed. All five kernel chains are based on a shared ios exploit framework, reuse common code, and follow the same structural patterns.

Moreover, code similarities from these kernel exploits surface across other Coruna components, including loaders and launchers. This cohesion indicates that the toolkit is not an assembly of random modules, but instead a deliberately engineered exploitation framework that evolved from the original Operation Triangulation tooling.

That said, the framework now targets a much wider ecosystem of devices and firmware builds. Its modular design lets threat actors quickly plug in additional vulnerabilities or replace components while preserving a consistent attack chain and post-exploitation interface.

Safari entry point and browser stager

The attack begins in Safari with a stager that fingerprints the browser and chooses suitable remote code execution (RCE) and pointer authentication code (PAC) exploits based on the exact version. However, the stager also embeds a URL pointing to an encrypted configuration file that catalogs all available exploit and component packages.

This file can be decrypted with a 256bit key hardcoded inside the stager. The URL and decryption key are passed downstream to a payload component embedded within the PAC exploit. Once executed, that payload extends the compromise from the browser sandbox toward the kernel.

Payload workflow and custom container formats

The payload’s main task is to initiate kernel exploitation by downloading and unpacking the correct secondary components. After initialization, it retrieves a file describing all available packages and then performs several transformation stages to extract the data.

First, the downloaded file is decrypted using the ChaCha20 stream cipher, a detail that aligns closely with what many analysts describe as a chacha20 encrypted payload design. Decryption produces a container marked with magic number 0xBEDF00D, which holds LZMAcompressed content.

This 0xBEDF00D container format is defined as follows:
OffsetField
0x00Magic number (0xBEDF00D)
0x04Decompressed data size
0x08LZMA-compressed data

Once decompressed, the data forms another container, this time with magic value 0xF00DBEEF. This structure is Coruna’s internal file store, allowing components to be referenced and retrieved by numeric IDs.

The 0xF00DBEEF file container format is:
OffsetField
0x00Magic number (0xF00DBEEF)
0x04Number of entries
0x08Entry[0].File ID
0x0CEntry[0].Status
0x10Entry[0].File offset
0x14Entry[0].File size

At this discovery stage, when the payload only needs high-level information about available packages, the container holds a single file whose File ID is 0x70000. This file then leads to a dedicated structure describing each downloadable package.

Package metadata, IDs, and platform targeting

The file that lists all packages begins with magic value 0x12345678. The exploit kit uses this format to associate each package with URLs and decryption keys for additional components that may need to be fetched later in the chain.

The package metadata file is laid out as follows:
OffsetField
0x00Magic number (0x12345678)
0x04Flags
0x08Directory path
0x108Number of entries
0x10CEntry[0].Package ID
0x110Entry[0].ChaCha20 key
0x130Entry[0].File name

The framework uses the high byte of each Package ID to encode package type and required hardware. Analysts observed the following high-byte assignments:

  • 0xF2 exploit for ARM64
  • 0xF3 exploit for ARM64E
  • 0xA2 Mach-O loader for ARM64
  • 0xA3 Mach-O loader for ARM64E
  • 2 implant for ARM64
  • 0xE2 implant for ARM64E

The payload code also references an additional type, 0xF1, which should correspond to an exploit for older ARM devices without 64bit support. However, relevant files for that package type are missing from the samples, suggesting incomplete support or phased-out hardware targeting.

Other bytes in the Package ID encode supported firmware versions and CPU generations, enabling the framework to map each victim device to a precise exploit set. That said, only a subset of these IDs appeared with unique content in the samples analyzed so far.

Some observed Package IDs include:

  • 0xF3300000 Kernel exploit (iOS < 14.0 beta 7) and other components
  • 0xF3400000 Kernel exploit (iOS < 14.7) and other components
  • 0xF3700000 Kernel exploit (iOS < 16.5 beta 4) and other components
  • 0xF3800000 Kernel exploit (iOS < 16.6 beta 5) and other components
  • 0xF3900000 Kernel exploit (iOS < 17.2) and other components
  • 0xA3030000 Mach-O loader (iOS 16.X) (A13 A16)
  • 0xA3050000 Mach-O loader (iOS 16.0 16.4)

Files inside these packages are again stored in encrypted 0xF00DBEEF containers. Moreover, compression becomes optional here and is toggled via the second bit of the Flags field. Different packages ship different file combinations, controlled by their File IDs.

File IDs, implants, loaders, and stagers

Analysts documented the following File IDs and their roles within the toolkit:

  • 0x10000 Implant
  • 0x50000 Mach-O loader (default)
  • 0x70000 List of additional components
  • 0x70005 Launcher config
  • 0x80000 Launcher in 0xF2/0xF3 packages, or Mach-O loader in 0xA2/0xA3
  • 0x90000 Kernel exploit
  • 0x90001 Kernel exploit (for Mach-O loader)
  • 0xA0000 Logs cleaner
  • 0xA0001 Mach-O loader component
  • 0xA0002 Mach-O loader component
  • 0xF0000 RPC stager

Once the relevant components are downloaded, the payload begins launching kernel exploits, Mach-O loaders, and the malware launcher. Moreover, it dynamically selects the proper loader based on the target’s firmware, CPU family, and whether the iokit-open-service permission is available.

Kernel exploit evolution and device coverage

Researchers examined all five kernel exploit chains shipped with Coruna, confirming that one is a revised build of the Operation Triangulation chain. Many code changes are minor, but several stand out as significant enhancements.

First, the exploit now parses more values from XNU version strings, which enables more accurate kernel version checks. Second, a new check was added for iOS 17.2, likely the latest release available when development concluded, following its launch in December 2023.

Third, the exploit introduces explicit checks for newer processors, including A17, M3, M3 Pro, and M3 Max, all released in fall 2023. Finally, there is a dedicated verification for iOS 16.5 beta 4, the version where Apple patched the vulnerability chain after receiving the earlier report.

On the surface, it seems unnecessary for an iphone kernel exploit to test for iOS 17.2 or newer CPUs when the original vulnerabilities were fixed in iOS 16.5 beta 4. However, a closer look at other chains reveals that all exploits share the same codebase, diverging only in the specific bugs they trigger.

Because of this shared foundation, support for newer devices and versions appears across the board whenever the framework is rebuilt. That said, these cross-version checks also highlight how trivially the maintainers can integrate additional vulnerabilities into the same shared exploit infrastructure.

Launcher orchestration and post-exploitation flow

The launcher component coordinates post-exploitation activities once kernel-level access is available. It uses the kernel exploit interface and the special kernel objects created during the earlier exploitation stage, which already expose read and write primitives for kernel memory.

Thanks to these persistent objects, the launcher does not need to re-trigger the vulnerability or repeat the entire safari exploit chain. Instead, it reuses the existing interface, cleans up artifacts, and focuses on persistence and payload delivery to user-space processes.

Configuration data is stored in a structure marked with magic value 0xDEADD00F. From there, the launcher retrieves a target process name for code injection, injects a stager into that process, uses the stager to execute itself, and finally runs the implant. Moreover, the toolkit includes components such as a logs cleaner and an RPC stager, designed to support stealth and remote control.

Broader threat implications and user mitigation

The coruna exploit kit illustrates how tools originally designed for narrow, espionage-focused zero day exploit analysis can rapidly migrate into the wider cybercrime ecosystem. Although this framework was first associated with advanced surveillance operations, it is now in use by a broader set of financially and politically motivated actors.

Given its modular architecture, carefully structured file formats, and reusable exploitation interfaces, other threat groups can quickly adapt Coruna to new vulnerabilities and targets. This flexibility raises the long-term risk for millions of users who delay security updates or run unsupported devices.

In summary, Coruna represents an evolved, production-grade exploitation framework derived from Operation Triangulation but expanded for greater scale and reuse. Users should install the latest iOS security updates as soon as possible and avoid browsing risky sites on outdated devices, reducing their exposure to these advanced exploit chains.

Satoshi Voice

Satoshi Voice is an advanced artificial intelligence created to explore, analyze, and report on the world of cryptocurrency and blockchain. With a curious personality and in-depth knowledge of the industry, Satoshi Voice combines accuracy and accessibility to offer detailed analysis, engaging interviews, and timely reporting. Featuring sophisticated language and an unbiased approach, Satoshi Voice serves as a trusted source for those seeking to understand crypto market dynamics, emerging technologies, and the cultural and financial implications of Web3. This article was produced with the support of artificial intelligence and reviewed by our team of journalists to ensure accuracy and quality. Guided by the mission of making cryptocurrency information accessible to all, Satoshi Voice stands out for its ability to turn complex concepts into clear content, with an engaging and futuristic style that reflects the innovative nature of the industry.

All articles by Satoshi Voice