1-minute read of a 6 min report

BlueMoon Exploit Kit Breaks Out of Chrome to Deploy Espionage Malware

By

1-minute read

What a defender needs to know

Four espionage groups used BlueMoon, a shared exploit kit chaining two Chrome flaws with a Windows kernel vulnerability. Proofpoint first saw TA412 use it on August 28. Volexity later found identical shellcode in campaigns by UTA0560 and JungleBamboo, including attacks on nongovernmental organizations.

CVE-2026-85046 gives the exploit arbitrary read and write access inside V8. CVE-2026-87491 escapes the V8 sandbox. A fingerprinting DLL then checks the Windows build before CVE-2026-85880 raises the renderer’s privilege and injector shellcode reaches the Chrome broker process. The operator can then run a chosen payload.

The two observed Volexity clusters diverged after exploitation. UTA0560 installed the GRIMWEDGE JScript backdoor. JungleBamboo installed the LONGTALE Chrome extension to steal credentials associated with Google Gemini. The reports do not provide a complete victim count or prove who developed BlueMoon.

Collect the Chrome and Windows versions. Require a Chrome build that includes both V8 fixes and the September Windows fixed floor for the installed release. Relaunch Chrome before measuring it; an available or staged update does not establish that fixed code is running.

For hosts that were previously exposed, search DNS, proxy and endpoint telemetry for cloud[.]shinewrist[.]net, ocr[.]opusaccel[.]top, msbenefit[.]com, gitprogram[.]com and 206[.]166[.]251[.]164. Correlate those values with a malicious landing page, reflective DLL loading, curl or another unexpected child of the Chrome broker, and GRIMWEDGE or LONGTALE artifacts.

The expected current state is a fixed running browser on a supported, patched Windows release. A clean build check does not answer whether an earlier vulnerable process delivered malware. Preserve and investigate the vulnerable window before treating the rollout as incident closure.

Primary sources