Web threats / iOS exploit kits
GhostWave iOS exploit kit
GhostWave is a fork of DarkSword's iPhone exploit chain. Its B9 route serves iOS 18.4 to 18.7 and its C10 route serves iOS 26, where the chain's own log calls it not working. Routers send it iPhones from hacked sites and, in November 2026, from compromised script vendors. Our rules first matched its code on 16 November, on the operator's own hosts.
GhostWave in numbers
Since 16 November, the first GhostWave match in our records, counted on 20 November 2026. How we count.
| Sites with GhostWave code | 0 |
|---|---|
| Sites with a match in the last 30 days | 0 |
| Operator hosts our rules matched | 3 |
| Latest match | 16 November |
A fork of DarkSword
GhostWave is DarkSword's iPhone chain, reworked, and one of the iOS exploit kits we track. DarkSword attacks iOS 18.4 to 18.7.2 and its code leaked in March 2026. GhostWave reuses DarkSword's entry page, loader and WebKit worker, with a new configuration in the loader, renamed keys in the entry page and additions to the worker. It comes in two routes:
- B9, for iOS 18.4 to 18.7
- C10, for iOS 26.0 to 26.3
The name is the kit's own. The next-chain router's boot.js calls its iOS 18.7.3 to 26 chain ghostwave, and the C10 worker's header calls itself a "GhostWave 26.x lab fork" of DarkSword's rce_worker_18.7.js. NetAskari's July 2026 post described a command panel called Ghostwave that ran the Coruna and DarkSword chains.
Three files tie it to DarkSword
The entry page, C10/b.html, is DarkSword's D12 entry code with its keys renamed from ds_d12_* to ds_b9_chain_*. It posts the visitor's details to /api/track, asks /api/gs_state and /api/pe_ok whether this phone has already run a chain, and if not loads rce_loader.js.
rce_loader.js opens with a __LDY_CFG object that holds the operator's server, delivery and fallback addresses. After that it is DarkSword's loader: the same slide and chipset globals and the same inline dlopen worker. It sorts each phone into a class, ghostwave among them, and picks rce_worker_18.x for iOS 18 or rce_worker_26.x for iOS 18.7.3 and 26.
The worker is the WebKit exploit. Both builds publish the same pair of arrays on self[0] and self[1] that DarkSword's worker builds its memory access from. The C10 worker adds a cap on how much it logs, and reads self.__B9_VK__, a name from the B9 route. The B9 worker for iOS 18.6 adds a function, _b9PatchPeJs, that rewrites the command server's address.
The router that carried it
In November 2026 a router reached iPhones through scripts that sites load from their vendors: Optimizely, Kissmetrics, StorifyMe and minute-ly, among others. The DarkSword page has that wave. The router's boot.js sends iOS 13 to 17 to Coruna, iOS 18 to DarkSword's D11 route and iOS 26 to C10/b.html.
On 16 November an iOS 26.3 visit to 5vobauua3ojpklx[.]icu got the C10 entry page, then evil_43818.heic, rce_loader.js and the 1.3 MB rce_worker_26.x.js. The chain logs each step to /api/log, and its own log reads usable_grade=DEAD weaponized=false. The operator ships the iOS 26 route, and the code says it does not work yet. An iOS 18.6 visit to t8d5qcrnupkve1x[.]icu the same day got the B9 loader and its 18.6 worker.
je4ft3gn8vxudum[.]icu serves the C10 route too. It is also the host of the operator's panel, which keeps a ledger of the seed phrases and private keys taken from each phone.
The route was off, then on
C10 is older than the vendor wave. On 5 November 2026 an OKX-branded server kept the route behind a switch, /profiles/c10_deploy.json, which read "enabled": false, and /C10/b.html returned 404. DarkSword router's iOS 26 route, C10, is switched off has that read. By 16 November the route was live on the vendor router's hosts.
Another router sends iOS 26.0 and 26.1 to C10 on purpose. A route.js on zeeoe[.]com, dated 20261111-c10-v5 in its code, explains in a Chinese comment that those versions all failed on the DarkSword chain, so it sends them to /chain/c10/b.html instead. The comment calls C10 "the author's V2 port chain". The kit is sold as Caishen iOS C2 V2, and one listing names its chains Coruna, DarkSword and C10.
The next-chain router grades its own chains. It calls iOS 18.4 to 18.7.2 DarkSword, weaponized: true, and 18.7.3 to 26.5 GhostWave, weaponized: false, with the warning "Do not treat GhostWave as production-ready".
Checking for GhostWave
Keep the page source, every frame it opens and the scripts each frame loads. Look for:
- frames or requests to
C10/b.html,/chain/c10/b.htmlor aB9/path on a router host ds_b9_chain_activeords_b9_chain_startin session storage- a
rce_loader.jsthat opens withvar __LDY_CFG - a
rce_worker_26.x.jsworker,__B9_VK__or_b9PatchPeJs - requests to
/api/track,/api/gs_stateor/api/pe_okfrom a frame - a script tag loading
boot.jswithdata-landing,data-channel-codeanddata-chain-url
Remove the router or frame injection and restore the changed files from a trusted deployment. Review CMS, hosting and deployment access and rotate affected credentials.