Skip to content

Security Reports disagree2 publishers 3 min read Published Updated

A reflected XSS on a US university site launched a three-CVE Chrome chain at NGOs

Volexity attributes September 1 spear-phishing at multiple NGOs to the Chinese cluster UTA0560. The chain used two Chrome flaws and one in Windows ALPC, and a second China-nexus actor ran the same chain.

The Watch · Security desk

Send a correction

Illustration accompanying A reflected XSS on a US university site launched a three-CVE Chrome chain at NGOs
Generated illustration

What happened

  • Volexity says the Chinese cluster it tracks as UTA0560 spear-phished multiple non-governmental organizations on September 1, 2026, with links that led to a US university web site.
  • The final payload arrives as an MSI whose custom actions run an obfuscated JavaScript backdoor, GRIMWEDGE, after a msgbox.exe loader sideloads a malicious wsc.dll.
  • Volexity saw a second China-nexus actor, JungleBamboo or APT31, running the same chain around the same time to deploy a loader called SUPERSTOMP.

Why it matters

  • What it limits constraint Domain reputation cannot separate a poisoned university URL from a clean one, so on a click the browser build is the only thing left between the user and code execution.
  • What's now possible capability Two clusters holding the same three exploits means detection content built from one intrusion covers neither fully; a sweep for msgbox.exe and wsc.dll never reaches the APT31 branch.
  • Who's exposed exposure NGO staff who clicked on Chrome for Windows are exposed on two different tracks: an in-memory foothold that reads files and fetches tooling, or a fake Gemini extension harvesting cookies and sessions.
  • What it sets up precedent Using someone else's unpatched XSS as the launch point, with server-side filtering to Chrome on Windows, gives any operator a trusted first hop and a way to keep responders' test traffic from ever seeing the exploit.

The link in the phishing mail pointed at a legitimate university domain. "The emails contained a message encouraging the users to click a link that led to the website of a U.S.-based university," Volexity researchers Ankur Saini, Conor Quigley, Sean Koessel, Steven Adair and Tom Lancaster said. "These links abused a reflected cross-site scripting (XSS) vulnerability on the website, redirecting recipients to threat-actor-controlled infrastructure hosting a multi-stage exploit chain." [3] The report describes the site only as U.S.-based.

The exploit page then filtered visitors, serving only systems running Chrome on Windows [7]. Replaying one of those URLs from Firefox, or from a Linux analysis box, returns nothing useful.

The three flaws run in sequence. CVE-2026-85046 gives arbitrary read/write inside the V8 sandbox [5]. CVE-2026-87491 escapes the browser sandbox [19]. CVE-2026-85880, in Windows Advanced Local Procedure Call, injects code into the Chrome browser process for arbitrary code execution [6]. Because each step depends on the one before it, a fix for any single link stops the chain at that step [18]. Proofpoint documented the chain, which Volexity calls BlueMoon, before this campaign [4].

After execution, the page decodes three Base64 shellcode blobs from its own JavaScript: p1 for host reconnaissance, p2 for kernel privilege escalation, pp for browser process injection and payload download [8]. The loader that follows, msgbox.exe, extracts a legitimate Windows binary and a malicious wsc.dll and sideloads it; the DLL then requests a text file named after the hostname collected during profiling [9]. That text file is an MSI, and its custom actions execute the obfuscated JavaScript backdoor [10]. GRIMWEDGE polls ocr.opusaccel[.]top and runs what it gets back in memory through eval() [11].

It is a thin implant on purpose. "The code has no built-in persistence, lateral movement, or exfiltration mechanism beyond the file-read and upload commands," the researchers said [12]. What it does support is Type, which reads a file up to 5 MB, Run, which executes a command in a hidden window, and a chunked Upload that reassembles a file from the C2 in memory before writing it to disk [14]. The researchers said the foothold is "sufficient enough for UTA0560 to survey the host, retrieve files of interest, and deploy additional tooling via the Run and Upload commands" [13].

Volexity also saw JungleBamboo, also tracked as APT31, using the same chain around the same time to drop a loader called SUPERSTOMP, which pulls down LONGTALE, a credential-stealing Chrome extension also known as GemStone [15]. LONGTALE poses as a Google Gemini extension under ID ckiknalbeplpcpofpnabcnhjcegckfei and does keylogging and form capture, cookie and session theft, keyword-triggered screenshots, and bulk exfiltration of keystrokes, cookies, storage, history and session metadata [16]. So an inventory sweep for msgbox.exe and wsc.dll covers the UTA0560 branch alone [20].

Volexity describes the flaws as recently patched and the chain as zero-day at the time of use, without dating the fixes [17]. For the NGOs hit on September 1, then, there was no patch to have applied [2]. All three bugs are fixed, so patch state decides who is reachable from here. Who was compromised that day is a separate question, and it has to be answered with retrospective hunting on browser process and DNS telemetry.

What to watch

  • Whether Volexity or the university identifies the site with the reflected XSS and confirms it is fixed.
  • Whether a third cluster turns up using the same three CVEs, which would point at a shared exploit supplier rather than two crews.
  • Whether the LONGTALE extension ID ckiknalbeplpcpofpnabcnhjcegckfei shows up in enterprise Chrome inventories outside these two campaigns.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence60
Adoption
Not scored
Hype gap+5
Incentives
Not scored
Confidence62
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Volexity attributes a spear-phishing campaign exploiting recently patched Google Chrome and Microsoft Windows flaws to a Chinese threat cluster it tracks as UTA0560, delivering a JavaScript backdoor called GRIMWEDGE.

    Reported SupportedView cited source
  2. [2]

    Volexity said the UTA0560 activity targeted multiple non-governmental organizations on September 1, 2026.

    Reported SupportedView cited source
  3. [3]

    Volexity researchers Ankur Saini, Conor Quigley, Sean Koessel, Steven Adair and Tom Lancaster said: "The emails contained a message encouraging the users to click a link that led to the website of a U.S.-based university. These links abused a reflected cross-site scripting (XSS) vulnerability on the website, redirecting recipients to threat-actor-controlled infrastructure hosting a multi-stage exploit chain."

    Reported SupportedView cited source
  4. [4]

    The exploit chain, previously highlighted by Proofpoint, involves three separate flaws: two in Chrome and one in Windows Advanced Local Procedure Call (ALPC). Volexity also calls the chain BlueMoon.

    Reported SupportedView cited source
  5. [5]

    The chain first abuses CVE-2026-85046 to gain arbitrary read/write within the V8 sandbox.

    Reported SupportedView cited source
  6. [6]

    The chain finally employs CVE-2026-85880, in Windows Advanced Local Procedure Call, to inject code into the Chrome browser process and achieve arbitrary code execution.

    Reported SupportedView cited source
  7. [7]

    The threat actor filtered out systems not using Chrome on Windows when they visited the URL.

    Reported SupportedView cited source
  8. [8]

    The final exploit page embeds three binary payloads as Base64-encoded strings within JavaScript: p1, shellcode that reflectively loads a DLL for host reconnaissance and fingerprinting; p2, shellcode that reflectively loads a DLL for Windows kernel privilege escalation; and pp, shellcode for browser process injection and payload download.

    Reported SupportedView cited source
  9. [9]

    For UTA0560 the next-stage payload is an executable named msgbox.exe, a loader that extracts from itself a legitimate Windows binary and a malicious DLL (wsc.dll) to start a DLL sideloading chain; the DLL contacts the same server to fetch a text file named after the device hostname obtained during profiling.

    Reported SupportedView cited source
  10. [10]

    The fetched text file is an MSI installer designed to execute an obfuscated JavaScript backdoor contained within the MSI custom actions.

    Reported SupportedView cited source
  11. [11]

    Once launched, GRIMWEDGE enters a persistent command loop polling a command-and-control server at ocr.opusaccel[.]top and executes instructions in memory via eval().

    Reported SupportedView cited source
  12. [12]

    The Volexity researchers said: "The code has no built-in persistence, lateral movement, or exfiltration mechanism beyond the file-read and upload commands."

    Reported SupportedView cited source
  13. [13]

    The Volexity researchers said the backdoor provides an initial foothold on a compromised host "sufficient enough for UTA0560 to survey the host, retrieve files of interest, and deploy additional tooling via the Run and Upload commands."

    Reported SupportedView cited source
  14. [14]

    GRIMWEDGE parses commands including Info, Dir, Mkdir, Del, Tasklist, Taskkill, Type (read a file up to 5 MB), Run (execute a command within a hidden window), Upload (chunk), which appends a Base64-encoded chunk from the C2 to an in-memory buffer, and Upload (commit), which saves the buffer to disk.

    Reported SupportedView cited source
  15. [15]

    Volexity said it also observed a second China-nexus threat actor known as JungleBamboo (aka APT31) using the same exploit chain around the same time to deploy a loader named SUPERSTOMP, which installs LONGTALE, a credential-stealing Chrome extension also referred to as GemStone, from a remote server.

    Reported SupportedView cited source
  16. [16]

    LONGTALE masquerades as a Google Gemini Chrome extension (ID: ckiknalbeplpcpofpnabcnhjcegckfei) to evade detection and supports keylogging and form capture, cookie and session theft, screenshot capture triggered by C2-supplied page keywords, and bulk exfiltration of keystrokes, cookies, storage data, navigation history and session metadata.

    Reported SupportedView cited source
  17. [17]

    Volexity's account describes the Chrome and Windows flaws as recently patched and calls the exploit chain a zero-day chain at the time of use, and does not state when the three fixes shipped.

    Reported SupportedView cited source
  18. [18]

    The three exploits run in a fixed order, so a fix for any one of CVE-2026-85046, CVE-2026-87491 or CVE-2026-85880 halts the chain at that step.

    Derived Supported
  19. [19]

    The chain then escapes the browser sandbox via CVE-2026-87491.

    Reported ContestedView cited source
  20. [20]

    The same three-CVE chain delivered two unrelated payload sets, UTA0560's msgbox.exe and GRIMWEDGE and JungleBamboo's SUPERSTOMP and LONGTALE, so host indicators from one campaign do not detect the other.

    Derived Contested

Sources

2 independent publishers whose own reporting we read for this story.

  1. securityaffairs.com

    1 article · September 15, 2026

    One Exploit Chain, Two Espionage Campaigns: Chrome and Windows Under Fire
  2. thehackernews.com

    2 articles · September 15, 2026

    China-Linked Hackers Exploit Chrome-Windows Zero-Day Chain to Deploy GRIMWEDGE

Topics and entities