AINEWS
Proofpoint says four state aligned espionage clusters adopted the same Chrome and Windows attack chain within days.
AI-assisted browser exploits now have a public case study. On 9 September, Proofpoint disclosed a new Chrome-and-Windows attack chain it calls BlueMoon, and the kit's operational fingerprints are the roughest the vendor has documented in a browser attack: heavy debug logging, a markdown handover document, and a default configuration that downloads and runs a remote binary via curl. The vendor stops short of attributing the kit to AI authorship; what the indicators do support is a different claim, that a Chrome V8 fix landing upstream is no longer the safety margin it used to be.
BlueMoon chains three vulnerabilities: a V8 type-confusion remote code execution bug (CVE-2026-85046), a V8 sandbox escape, and a Windows kernel local privilege escalation (CVE-2026-85880) that only works on older Windows builds. All three are "patch-gap" zero-days, already fixed in the upstream Chromium source, but not yet rolled into the latest stable Chrome or Edge releases at the time of exploitation. Proofpoint's Once BlueMoon, multiple state-aligned threat actors rapidly adopt novel exploit walkthrough documents the chain in detail; Ars Technica's summary by Dan Goodin is the independent second source for the four-actor timeline.
The first observed BlueMoon use was on 28 August 2026 by TA412 (also tracked as JungleBamboo, Violet Typhoon, APT31, and TIDE CASTLE), a China-aligned espionage group. Within days, three other clusters had adopted the kit: UNK_LateNight (also China-aligned, focused on US aerospace targets), UNK_DoubleCheck (a Vietnamese manufacturing entity), and UNK_QuietRacket (active against Singapore and Indonesia). The delivery infrastructure, including campaign landing pages and redirectors, went up the same day or in the days immediately preceding use, consistent with a rushed, opportunistically shared capability rather than a long-planned operation. The LPE's narrow target window (older Windows builds, including the Windows 10 October 2018 Update, Windows Server 2019, Windows 10 2004, Windows Server 2022, and the initial Windows 11 release) and the chain's lower reliability reinforce the same read: speed over yield.
The root cause of the V8 type confusion sits in Maglev's TryReduceArrayPrototypeSort, where a mixed-feedback Array.prototype.sort() call can transition a packed-Smi array into a packed-elements map without the inlining machinery catching up, a confusion the original bug reporter documents in "When Sorting Leads to Confusion". That mechanism is the lever that makes the kit fast to repurpose: the public patch is itself a recipe for the working exploit, and the time between patch and stable rollout is the window in which AI-assisted iteration can outpace defensive cadence.
All three CVEs were patched within 24 hours of Proofpoint's disclosure window. The vendor expects BlueMoon to keep proliferating as those patches roll out, and to spread from state-aligned espionage clusters to financially motivated actors now that the chain is public. Treat a Chrome V8 fix landing upstream as a start-gun for capability iteration, not a finished fix, and assume the next patch-gap kit will land in more than one operation at once.