1-minute read
What a defender needs to know
An attacker noticed monitoring on a Windows VM and attempted to clean up after a replay of UTA0560’s Chrome-to-Windows exploit chain. Volexity acquired RAM, registry hives, event logs, the USN journal ($UsnJournal) and master file table ($MFT). Volcano flagged memory-only components in chrome.exe; an expanded indicator scan found GRIMWEDGE-encoded JavaScript in free memory. The original campaign used CVE-2026-85046, CVE-2026-87491 and CVE-2026-85880 to reach the host. UTA0560 deployed GRIMWEDGE, while JungleBamboo used the same exploit components to deliver a credential-stealing Chrome extension.
Preserve RAM before restarting a suspected endpoint. Check available browser history and event logs for cloud.shinewrist[.]net, then correlate hits with shell and curl command lines, memory findings and persistence artifacts. In Volexity’s separate demonstration, a deliberately seeded Edge-history URL triggered a small browser-and-registry collection and then a broader file-and-memory collection on one Windows Server. Verify the workflow by confirming the first collection’s evidence and alert, then the second collection’s RAM and requested files. Volexity evaluated its own Volcano product using an AI client; the collection artifacts, rather than an AI label alone, are what an investigator should inspect.