CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Microsoft Edge

product · product:microsoft-edge single-source

Coverage
6
first 2026-07-28 → last 2026-10-21
Latest activity
2026-10-21
Symantec: APT28's hidden-Edge backdoor hit law-enforcement and defence targets; at a shipbuilder it added an…
Peak priority
high
2 high · 3 notable · 1 routine
Targets
public-sector
sectors: public-sector, defense, manufacturing · regions: europe, us, apac
Sources cited
22
18 hosts

Action items (2)

Do-now tasks recorded on the entries about Microsoft Edge, newest first. Check the date before acting on an older one.

  • After confirming Chrome ≥152.0.7977.82 and the September Windows cumulative update are deployed fleet-wide, separately audit installed Chromium extensions requesting broad host/tab/storage permissions and any browser-associated scheduled task created in the days before patching; neither the malicious GemStone extension nor the kit's scheduled-task persistence is removed by the OS/browser patch.
    2026-09-10CVE-2026-85046 +2
  • Update Chrome, Edge and every other Chromium-based browser in the fleet to ≥153.0.8010.36 now; this is the seventh actively-exploited Chrome zero-day patched in 2026, and Google has disclosed no interim mitigation short of the update.
    2026-09-10CVE-2026-87491

Defender insights

What each entry about Microsoft Edge tells a defender to do, newest first.

2026-10-21NOTABLESymantec: APT28's hidden-Edge backdoor hit law-enforcement and defence targets; at a shipbuilder it added an SSH tunnel

Exposure · triage · detection

2026-09-10HIGHexploitedSix espionage clusters ran the identical click-to-SYSTEM exploit kit within days of each other; Proofpoint calls it the same code, not parallel development

Triage

2026-09-24ROUTINEA malware implant treats commercial AI chatbot endpoints as its command-and-control infrastructure, no attacker server required

Triage · detection

2026-09-21NOTABLEElastic Security Labs: a Brazilian banking-fraud toolkit defeats Chromium's extension-integrity check by extracting the browser's own signing keys from memory

Triage

2026-07-28NOTABLEMedusaHVNC rides real logged-in browser sessions on a hidden Windows desktop, defeating device-based fraud checks

Triage

Story timeline

  1. 2026-10-21APT28 (Swallowtail) used the HOOKEDGE backdoor against a law-enforcement agency, a naval shipbuilder and an aircraft-engine maker in two NATO states; at the shipbuilder it then pushed an SSH key for a persistent tunnel, captured NTLM handshakes and ran a reflective loader
    active-threatsSymantec: APT28's hidden-Edge backdoor hit law-enforcement and defence targets; at a shipbuilder it added an SSH tunnel
  2. 2026-09-24CLOSEDQUORUM: Cisco Talos documents what it calls, to its knowledge, the first publicly documented Windows implant that lets a panel of four commercial LLMs vote on its next action instead of a human operator
    active-threatsA malware implant treats commercial AI chatbot endpoints as its command-and-control infrastructure, no attacker server required
  3. 2026-09-21REF9334/KREMLIN forges Chromium's own Secure Preferences integrity hashes to silently install a banking-fraud browser extension outside the Web Store, resolving C2 through an Ethereum smart contract
    active-threatsElastic Security Labs: a Brazilian banking-fraud toolkit defeats Chromium's extension-integrity check by extracting the browser's own signing keys from memory
  4. 2026-09-10CVE-2026-87491, Google Chrome: V8 out-of-bounds write exploited in the wild, patched in Chrome 153 (seventh exploited Chrome zero-day of 2026)
    trending-vulnerabilitiesGoogle ships an emergency Chrome fix for a seventh actively exploited V8 zero-day this year
  5. 2026-09-10BlueMoon: six separate state-nexus actor clusters independently weaponize a shared Chrome V8 + Windows kernel zero-day chain
    active-threatsSix espionage clusters ran the identical click-to-SYSTEM exploit kit within days of each other; Proofpoint calls it the same code, not parallel development
  6. 2026-07-28MedusaHVNC: a malware-as-a-service RAT that drives the victim's own logged-in browser on an invisible second Windows desktop
    active-threatsMedusaHVNC rides real logged-in browser sessions on a hidden Windows desktop, defeating device-based fraud checks
ATT&CK techniques (54 across 12 tactics)

54 techniques observed across 6 entries about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.0 · compare on the matrix · Navigator layer (JSON)

  • Resource DevelopmentAcquire Infrastructure: Domains
  • Initial AccessDrive-by Compromise · Phishing: Spearphishing Attachment · Phishing: Spearphishing Link
  • ExecutionScheduled Task/Job: Scheduled Task · Command and Scripting Interpreter: PowerShell · Command and Scripting Interpreter: Windows Command Shell · Command and Scripting Interpreter: Visual Basic · Command and Scripting Interpreter: JavaScript · Exploitation for Client Execution · User Execution: Malicious File · Inter-Process Communication: Component Object Model · Hijack Execution Flow: DLL
  • PersistenceScheduled Task/Job: Scheduled Task · Software Extensions · Event Triggered Execution: Windows Management Instrumentation Event Subscription · Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder
  • Privilege EscalationScheduled Task/Job: Scheduled Task · Process Injection · Process Injection: Asynchronous Procedure Call · Process Injection: Process Hollowing · Exploitation for Privilege Escalation · Event Triggered Execution: Windows Management Instrumentation Event Subscription · Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder
  • StealthObfuscated Files or Information · Obfuscated Files or Information: Dynamic API Resolution · Process Injection · Process Injection: Asynchronous Procedure Call · Process Injection: Process Hollowing · Indicator Removal: File Deletion · Deobfuscate/Decode Files or Information · System Binary Proxy Execution: Msiexec · Virtualization/Sandbox Evasion · Virtualization/Sandbox Evasion: Time Based Checks · Hide Artifacts: Hidden Window · Hijack Execution Flow: DLL · Reflective Code Loading
  • Defense ImpairmentSubvert Trust Controls · Subvert Trust Controls: Mark-of-the-Web Bypass · Disable or Modify Tools
  • Credential AccessOS Credential Dumping: LSASS Memory · Input Capture: Keylogging · Forced Authentication · Steal Web Session Cookie · Credentials from Password Stores: Credentials from Web Browsers
  • DiscoverySystem Network Configuration Discovery · System Owner/User Discovery · Process Discovery · Permission Groups Discovery · System Information Discovery · File and Directory Discovery · Virtualization/Sandbox Evasion · Virtualization/Sandbox Evasion: Time Based Checks
  • CollectionInput Capture: Keylogging · Screen Capture · Clipboard Data · Browser Session Hijacking
  • Command and ControlApplication Layer Protocol: Web Protocols · Application Layer Protocol: DNS · Web Service: Dead Drop Resolver · Web Service: Bidirectional Communication · Ingress Tool Transfer · Protocol Tunneling · Encrypted Channel: Symmetric Cryptography
  • ExfiltrationExfiltration Over Web Service: Exfiltration Over Webhook

Resource Development TA0042

T1583.001Acquire Infrastructure: Domains×1

Adversaries may acquire domains that can be used during targeting. Domain names are the human readable names used to represent one or more IP addresses. They can be purchased or, in some cases, acquired for free.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

Initial Access TA0001

T1189Drive-by Compromise×2

Adversaries may gain access to a system through a user visiting a website over the normal course of browsing. Multiple ways of delivering exploit code to a browser exist (i.e., Drive-by Target), including:

Evidence: 2026-09-10/cve-2026-87491-chrome-v8-oob-write-seventh-2026-zero-day · 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1566.001Phishing: Spearphishing Attachment×1

Adversaries may send spearphishing emails with a malicious attachment in an attempt to gain access to victim systems. Spearphishing attachment is a specific variant of spearphishing. Spearphishing attachment is different from other forms of spearphishing in that it employs the use of malware attached to an email. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries attach a file to the spearphishing email and usually rely upon User Execution to gain execution. Spearphishing may also involve social engineering techniques, such as posing as a trusted source.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

T1566.002Phishing: Spearphishing Link×1

Adversaries may send spearphishing emails with a malicious link in an attempt to gain access to victim systems. Spearphishing with a link is a specific variant of spearphishing. It is different from other forms of spearphishing in that it employs the use of links to download malware contained in email, instead of attaching malicious files to the email itself, to avoid defenses that may inspect email attachments. Spearphishing may also involve social engineering techniques, such as posing as a trusted source.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

Execution TA0002

T1053.005Scheduled Task/Job: Scheduled Task×3

Adversaries may abuse the Windows Task Scheduler to perform task scheduling for initial or recurring execution of malicious code. There are multiple ways to access the Task Scheduler in Windows. The schtasks utility can be run directly on the command line, or the Task Scheduler can be opened through the GUI within the Administrator Tools section of the Control Panel. In some cases, adversaries have used a .NET wrapper for the Windows Task Scheduler, and alternatively, adversaries have used the Windows netapi32 library and Windows Management Instrumentation (WMI) to create a scheduled task. Adversaries may also utilize the Powershell Cmdlet `Invoke-CimMethod`, which leverages WMI class `PS_ScheduledTask` to create a scheduled task via an XML path.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · 2026-09-24/closedquorum-llm-orchestrated-c2-implant · 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1059.001Command and Scripting Interpreter: PowerShell×1

Adversaries may abuse PowerShell commands and scripts for execution. PowerShell is a powerful interactive command-line interface and scripting environment included in the Windows operating system. PowerShell can also be installed on Linux and macOS. Adversaries can use PowerShell to perform a number of actions, including discovery of information and execution of code. Examples include the <code>Start-Process</code> cmdlet which can be used to run an executable and the <code>Invoke-Command</code> cmdlet which runs a command locally or on a remote computer (though administrator permissions are required to use PowerShell to connect to remote systems).

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

T1059.003Command and Scripting Interpreter: Windows Command Shell×1

Adversaries may abuse the Windows command shell for execution. The Windows command shell (cmd) is the primary command prompt on Windows systems. The Windows command prompt can be used to control almost any aspect of a system, with various permission levels required for different subsets of commands. The command prompt can be invoked remotely via Remote Services such as SSH.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

T1059.005Command and Scripting Interpreter: Visual Basic×1

Adversaries may abuse Visual Basic (VB) for execution. VB is a programming language created by Microsoft with interoperability with many Windows technologies such as Component Object Model and the Native API through the Windows API. Although tagged as legacy with no planned future evolutions, VB is integrated and supported in the .NET Framework and cross-platform .NET Core.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

T1059.007Command and Scripting Interpreter: JavaScript×1

Adversaries may abuse various implementations of JavaScript for execution. JavaScript (JS) is a platform-independent scripting language (compiled just-in-time at runtime) commonly associated with scripts in webpages, though JS can be executed in runtime environments outside the browser.

Evidence: 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

T1203Exploitation for Client Execution×2

Adversaries may exploit software vulnerabilities in client applications to execute code. Vulnerabilities can exist in software due to unsecure coding practices that can lead to unanticipated behavior. Adversaries can take advantage of certain vulnerabilities through targeted exploitation for the purpose of arbitrary code execution. Oftentimes the most valuable exploits to an offensive toolkit are those that can be used to obtain code execution on a remote system because they can be used to gain access to that system. Users will expect to see files related to the applications they commonly used to do work, so they are a useful target for exploit research and development because of their high utility.

Evidence: 2026-09-10/cve-2026-87491-chrome-v8-oob-write-seventh-2026-zero-day · 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1204.002User Execution: Malicious File×2

An adversary may rely upon a user opening a malicious file in order to gain execution. Users may be subjected to social engineering to get them to open a file that will lead to code execution. This user action will typically be observed as follow-on behavior from Spearphishing Attachment. Adversaries may use several types of files that require a user to execute them, including .doc, .pdf, .xls, .rtf, .scr, .exe, .lnk, .pif, .cpl, .reg, and .iso.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · 2026-09-21/ref9334-kremlin-chromium-secure-preferences-hmac-forge · ATT&CK page ↗

T1559.001Inter-Process Communication: Component Object Model×1

Adversaries may use the Windows Component Object Model (COM) for local code execution. COM is an inter-process communication (IPC) component of the native Windows application programming interface (API) that enables interaction between software objects, or executable code that implements one or more interfaces. Through COM, a client object can call methods of server objects, which are typically binary Dynamic Link Libraries (DLL) or executables (EXE). Remote COM execution is facilitated by Remote Services such as Distributed Component Object Model (DCOM).

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1574.001Hijack Execution Flow: DLL×2

Adversaries may abuse dynamic-link library files (DLLs) in order to achieve persistence, escalate privileges, and evade defenses. DLLs are libraries that contain code and data that can be simultaneously utilized by multiple programs. While DLLs are not malicious by nature, they can be abused through mechanisms such as side-loading, hijacking search order, and phantom DLL hijacking.

Evidence: 2026-09-21/ref9334-kremlin-chromium-secure-preferences-hmac-forge · 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

Persistence TA0003

T1053.005Scheduled Task/Job: Scheduled Task×3

Adversaries may abuse the Windows Task Scheduler to perform task scheduling for initial or recurring execution of malicious code. There are multiple ways to access the Task Scheduler in Windows. The schtasks utility can be run directly on the command line, or the Task Scheduler can be opened through the GUI within the Administrator Tools section of the Control Panel. In some cases, adversaries have used a .NET wrapper for the Windows Task Scheduler, and alternatively, adversaries have used the Windows netapi32 library and Windows Management Instrumentation (WMI) to create a scheduled task. Adversaries may also utilize the Powershell Cmdlet `Invoke-CimMethod`, which leverages WMI class `PS_ScheduledTask` to create a scheduled task via an XML path.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · 2026-09-24/closedquorum-llm-orchestrated-c2-implant · 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1176Software Extensions×2

Adversaries may abuse software extensions to establish persistent access to victim systems. Software extensions are modular components that enhance or customize the functionality of software applications, including web browsers, Integrated Development Environments (IDEs), and other platforms. Extensions are typically installed via official marketplaces, app stores, or manually loaded by users, and they often inherit the permissions and access levels of the host application.

Evidence: 2026-09-21/ref9334-kremlin-chromium-secure-preferences-hmac-forge · 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1546.003Event Triggered Execution: Windows Management Instrumentation Event Subscription×1

Adversaries may establish persistence and elevate privileges by executing malicious content triggered by a Windows Management Instrumentation (WMI) event subscription. WMI can be used to install event filters, providers, consumers, and bindings that execute code when a defined event occurs. Examples of events that may be subscribed to are the wall clock time, user login, or the computer's uptime.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · ATT&CK page ↗

T1547.001Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder×2

Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. These programs will be executed under the context of the user and will have the account's associated permissions level.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

Privilege Escalation TA0004

T1053.005Scheduled Task/Job: Scheduled Task×3

Adversaries may abuse the Windows Task Scheduler to perform task scheduling for initial or recurring execution of malicious code. There are multiple ways to access the Task Scheduler in Windows. The schtasks utility can be run directly on the command line, or the Task Scheduler can be opened through the GUI within the Administrator Tools section of the Control Panel. In some cases, adversaries have used a .NET wrapper for the Windows Task Scheduler, and alternatively, adversaries have used the Windows netapi32 library and Windows Management Instrumentation (WMI) to create a scheduled task. Adversaries may also utilize the Powershell Cmdlet `Invoke-CimMethod`, which leverages WMI class `PS_ScheduledTask` to create a scheduled task via an XML path.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · 2026-09-24/closedquorum-llm-orchestrated-c2-implant · 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1055Process Injection×2

Adversaries may inject code into processes in order to evade process-based defenses as well as possibly elevate privileges. Process injection is a method of executing arbitrary code in the address space of a separate live process. Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via process injection may also evade detection from security products since the execution is masked under a legitimate process.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

T1055.004Process Injection: Asynchronous Procedure Call×1

Adversaries may inject malicious code into processes via the asynchronous procedure call (APC) queue in order to evade process-based defenses as well as possibly elevate privileges. APC injection is a method of executing arbitrary code in the address space of a separate live process.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · ATT&CK page ↗

T1055.012Process Injection: Process Hollowing×1

Adversaries may inject malicious code into suspended and hollowed processes in order to evade process-based defenses. Process hollowing is a method of executing arbitrary code in the address space of a separate live process.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · ATT&CK page ↗

T1068Exploitation for Privilege Escalation×1

Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1546.003Event Triggered Execution: Windows Management Instrumentation Event Subscription×1

Adversaries may establish persistence and elevate privileges by executing malicious content triggered by a Windows Management Instrumentation (WMI) event subscription. WMI can be used to install event filters, providers, consumers, and bindings that execute code when a defined event occurs. Examples of events that may be subscribed to are the wall clock time, user login, or the computer's uptime.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · ATT&CK page ↗

T1547.001Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder×2

Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. These programs will be executed under the context of the user and will have the account's associated permissions level.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

Stealth TA0005

T1027Obfuscated Files or Information×2

Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit. This is common behavior that can be used across different platforms and the network to evade defenses.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1027.007Obfuscated Files or Information: Dynamic API Resolution×1

Adversaries may obfuscate then dynamically resolve API functions called by their malware in order to conceal malicious functionalities and impair defensive analysis. Malware commonly uses various Native API functions provided by the OS to perform various tasks such as those involving processes, files, and other system artifacts.

Evidence: 2026-09-21/ref9334-kremlin-chromium-secure-preferences-hmac-forge · ATT&CK page ↗

T1055Process Injection×2

Adversaries may inject code into processes in order to evade process-based defenses as well as possibly elevate privileges. Process injection is a method of executing arbitrary code in the address space of a separate live process. Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via process injection may also evade detection from security products since the execution is masked under a legitimate process.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

T1055.004Process Injection: Asynchronous Procedure Call×1

Adversaries may inject malicious code into processes via the asynchronous procedure call (APC) queue in order to evade process-based defenses as well as possibly elevate privileges. APC injection is a method of executing arbitrary code in the address space of a separate live process.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · ATT&CK page ↗

T1055.012Process Injection: Process Hollowing×1

Adversaries may inject malicious code into suspended and hollowed processes in order to evade process-based defenses. Process hollowing is a method of executing arbitrary code in the address space of a separate live process.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · ATT&CK page ↗

T1070.004Indicator Removal: File Deletion×1

Adversaries may delete files left behind by the actions of their intrusion activity. Malware, tools, or other non-native files dropped or created on a system by an adversary (ex: Ingress Tool Transfer) may leave traces to indicate to what was done within a network and how. Removal of these files can occur during an intrusion, or as part of a post-intrusion process to minimize the adversary's footprint.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

T1140Deobfuscate/Decode Files or Information×1

Adversaries may use Obfuscated Files or Information to hide artifacts of an intrusion from analysis. They may require separate mechanisms to decode or deobfuscate that information depending on how they intend to use it. Methods for doing that include built-in functionality of malware or by using utilities present on the system.

Evidence: 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

T1218.007System Binary Proxy Execution: Msiexec×1

Adversaries may abuse msiexec.exe to proxy execution of malicious payloads. Msiexec.exe is the command-line utility for the Windows Installer and is thus commonly associated with executing installation packages (.msi). The Msiexec.exe binary may also be digitally signed by Microsoft.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1497Virtualization/Sandbox Evasion×1

Adversaries may employ various means to detect and avoid virtualization and analysis environments. This may include changing behaviors based on the results of checks for the presence of artifacts indicative of a virtual machine environment (VME) or sandbox. If the adversary detects a VME, they may alter their malware to disengage from the victim or conceal the core functions of the implant. They may also search for VME artifacts before dropping secondary or additional payloads. Adversaries may use the information learned from Virtualization/Sandbox Evasion during automated discovery to shape follow-on behaviors.

Evidence: 2026-09-21/ref9334-kremlin-chromium-secure-preferences-hmac-forge · ATT&CK page ↗

T1497.003Virtualization/Sandbox Evasion: Time Based Checks×1

Adversaries may employ various time-based methods to detect virtualization and analysis environments, particularly those that attempt to manipulate time mechanisms to simulate longer elapses of time. This may include enumerating time-based properties, such as uptime or the system clock.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · ATT&CK page ↗

T1564.003Hide Artifacts: Hidden Window×2

Adversaries may use hidden windows to conceal malicious activity from the plain sight of users. In some cases, windows that would typically be displayed when an application carries out an operation can be hidden. This may be utilized by system administrators to avoid disrupting user work environments when carrying out administrative tasks.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

T1574.001Hijack Execution Flow: DLL×2

Adversaries may abuse dynamic-link library files (DLLs) in order to achieve persistence, escalate privileges, and evade defenses. DLLs are libraries that contain code and data that can be simultaneously utilized by multiple programs. While DLLs are not malicious by nature, they can be abused through mechanisms such as side-loading, hijacking search order, and phantom DLL hijacking.

Evidence: 2026-09-21/ref9334-kremlin-chromium-secure-preferences-hmac-forge · 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1620Reflective Code Loading×1

Adversaries may reflectively load code into a process in order to conceal the execution of malicious payloads. Reflective loading involves allocating then executing payloads directly within the memory of the process, vice creating a thread or process backed by a file path on disk (e.g., Shared Modules).

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

Defense Impairment TA0112

T1553Subvert Trust Controls×1

Adversaries may undermine security controls that will either warn users of untrusted activity or prevent execution of untrusted programs. Operating systems and security products may contain mechanisms to identify programs or websites as possessing some level of trust. Examples of such features would include a program being allowed to run because it is signed by a valid code signing certificate, a program prompting the user with a warning because it has an attribute set from being downloaded from the Internet, or getting an indication that you are about to connect to an untrusted site.

Evidence: 2026-09-21/ref9334-kremlin-chromium-secure-preferences-hmac-forge · ATT&CK page ↗

T1553.005Subvert Trust Controls: Mark-of-the-Web Bypass×1

Adversaries may abuse specific file formats to subvert Mark-of-the-Web (MOTW) controls. In Windows, when files are downloaded from the Internet, they are tagged with a hidden NTFS Alternate Data Stream (ADS) named <code>Zone.Identifier</code> with a specific value known as the MOTW. Files that are tagged with MOTW are protected and cannot perform certain actions. For example, starting in MS Office 10, if a MS Office file has the MOTW, it will open in Protected View. Executables tagged with the MOTW will be processed by Windows Defender SmartScreen that compares files with an allowlist of well-known executables. If the file is not known/trusted, SmartScreen will prevent the execution and warn the user not to run it.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1685Disable or Modify Tools×2

Adversaries may disable, degrade, or tamper with security tools or applications (e.g., endpoint detection and response (EDR) tools, intrusion detection systems (IDS), antivirus, logging agents, sensors, etc.) to impair or reduce visibility of defensive capabilities. This may include stopping specific services, killing processes, modifying or deleting tool configuration files and Registry keys, or preventing tools from updating. This may also include impairing defenses more broadly by disrupting preventative, detection, and response mechanisms across host, network, and cloud environments.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

Credential Access TA0006

T1003.001OS Credential Dumping: LSASS Memory×1

Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS). After a user logs on, the system generates and stores a variety of credential materials in LSASS process memory. These credential materials can be harvested by an administrative user or SYSTEM and used to conduct Lateral Movement using Use Alternate Authentication Material.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · ATT&CK page ↗

T1056.001Input Capture: Keylogging×1

Adversaries may log user keystrokes to intercept credentials as the user types them. Keylogging is likely to be used to acquire credentials for new access opportunities when OS Credential Dumping efforts are not effective, and may require an adversary to intercept keystrokes on a system for a substantial period of time before credentials can be successfully captured. In order to increase the likelihood of capturing credentials quickly, an adversary may also perform actions such as clearing browser cookies to force users to reauthenticate to systems.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1187Forced Authentication×1

Adversaries may gather credential material by invoking or forcing a user to automatically provide authentication information through a mechanism in which they can intercept.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

T1539Steal Web Session Cookie×2

An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials. Web applications and services often use session cookies as an authentication token after a user has authenticated to a website.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

T1555.003Credentials from Password Stores: Credentials from Web Browsers×3

Adversaries may acquire credentials from web browsers by reading files specific to the target browser. Web browsers commonly save credentials such as website usernames and passwords so that they do not need to be entered manually in the future. Web browsers typically store the credentials in an encrypted format within a credential store; however, methods exist to extract plaintext credentials from web browsers.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · 2026-09-21/ref9334-kremlin-chromium-secure-preferences-hmac-forge · 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

Discovery TA0007

T1016System Network Configuration Discovery×1

Adversaries may look for details about the network configuration and settings, such as IP and/or MAC addresses, of systems they access or through information discovery of remote systems. Several operating system administration utilities exist that can be used to gather this information. Examples include Arp, ipconfig/ifconfig, nbtstat, and route.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

T1033System Owner/User Discovery×1

Adversaries may attempt to identify the primary user, currently logged in user, set of users that commonly uses a system, or whether a user is actively using the system. They may do this, for example, by retrieving account usernames or by using OS Credential Dumping. The information may be collected in a number of different ways using other Discovery techniques, because user and username details are prevalent throughout a system and include running process ownership, file/directory ownership, session information, and system logs. Adversaries may use the information from System Owner/User Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

T1057Process Discovery×1

Adversaries may attempt to get information about running processes on a system. Information obtained could be used to gain an understanding of common software/applications running on systems within the network. Administrator or otherwise elevated access may provide better process details. Adversaries may use the information from Process Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

T1069Permission Groups Discovery×1

Adversaries may attempt to discover group and permission settings. This information can help adversaries determine which user accounts and groups are available, the membership of users in particular groups, and which users and groups have elevated permissions.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

T1082System Information Discovery×1

An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture. Adversaries may use this information to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions. This behavior is distinct from Local Storage Discovery which is an adversary's discovery of local drive, disks and/or volumes.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

T1083File and Directory Discovery×1

Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system. Adversaries may use the information from File and Directory Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

T1497Virtualization/Sandbox Evasion×1

Adversaries may employ various means to detect and avoid virtualization and analysis environments. This may include changing behaviors based on the results of checks for the presence of artifacts indicative of a virtual machine environment (VME) or sandbox. If the adversary detects a VME, they may alter their malware to disengage from the victim or conceal the core functions of the implant. They may also search for VME artifacts before dropping secondary or additional payloads. Adversaries may use the information learned from Virtualization/Sandbox Evasion during automated discovery to shape follow-on behaviors.

Evidence: 2026-09-21/ref9334-kremlin-chromium-secure-preferences-hmac-forge · ATT&CK page ↗

T1497.003Virtualization/Sandbox Evasion: Time Based Checks×1

Adversaries may employ various time-based methods to detect virtualization and analysis environments, particularly those that attempt to manipulate time mechanisms to simulate longer elapses of time. This may include enumerating time-based properties, such as uptime or the system clock.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · ATT&CK page ↗

Collection TA0009

T1056.001Input Capture: Keylogging×1

Adversaries may log user keystrokes to intercept credentials as the user types them. Keylogging is likely to be used to acquire credentials for new access opportunities when OS Credential Dumping efforts are not effective, and may require an adversary to intercept keystrokes on a system for a substantial period of time before credentials can be successfully captured. In order to increase the likelihood of capturing credentials quickly, an adversary may also perform actions such as clearing browser cookies to force users to reauthenticate to systems.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1113Screen Capture×1

Adversaries may attempt to take screen captures of the desktop to gather information over the course of an operation. Screen capturing functionality may be included as a feature of a remote access tool used in post-compromise operations. Taking a screenshot is also typically possible through native utilities or API calls, such as <code>CopyFromScreen</code>, <code>xwd</code>, or <code>screencapture</code>.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1115Clipboard Data×2

Adversaries may collect data stored in the clipboard from users copying information within or between applications.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

T1185Browser Session Hijacking×1

Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.

Evidence: 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

Command and Control TA0011

T1071.001Application Layer Protocol: Web Protocols×1

Adversaries may communicate using application layer protocols associated with web traffic to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1071.004Application Layer Protocol: DNS×1

Adversaries may communicate using the Domain Name System (DNS) application layer protocol to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1102.001Web Service: Dead Drop Resolver×1

Adversaries may use an existing, legitimate external Web service to host information that points to additional command and control (C2) infrastructure. Adversaries may post content, known as a dead drop resolver, on Web services with embedded (and often obfuscated/encoded) domains or IP addresses. Once infected, victims will reach out to and be redirected by these resolvers.

Evidence: 2026-09-21/ref9334-kremlin-chromium-secure-preferences-hmac-forge · ATT&CK page ↗

T1102.002Web Service: Bidirectional Communication×2

Adversaries may use an existing, legitimate external Web service as a means for sending commands to and receiving output from a compromised system over the Web service channel. Compromised systems may leverage popular websites and social media to host command and control (C2) instructions. Those infected systems can then send the output from those commands back over that Web service channel. The return traffic may occur in a variety of ways, depending on the Web service being utilized. For example, the return traffic may take the form of the compromised system posting a comment on a forum, issuing a pull request to development project, updating a document hosted on a Web service, or by sending a Tweet.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · 2026-09-24/closedquorum-llm-orchestrated-c2-implant · ATT&CK page ↗

T1105Ingress Tool Transfer×3

Adversaries may transfer tools or other files from an external system into a compromised environment. Tools or files may be copied from an external adversary-controlled system to the victim network through the command and control channel or through alternate protocols such as ftp. Once present, adversaries may also transfer/spread tools between victim devices within a compromised environment (i.e. Lateral Tool Transfer).

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · 2026-09-21/ref9334-kremlin-chromium-secure-preferences-hmac-forge · 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

T1572Protocol Tunneling×1

Adversaries may tunnel network communications to and from a victim system within a separate protocol to avoid detection/network filtering and/or enable access to otherwise unreachable systems. Tunneling involves explicitly encapsulating a protocol within another. This behavior may conceal malicious traffic by blending in with existing traffic and/or provide an outer layer of encryption (similar to a VPN). Tunneling could also enable routing of network packets that would otherwise not reach their intended destination, such as SMB, RDP, or other traffic that would be filtered by network appliances or not routed over the Internet.

Evidence: 2026-10-21/apt28-hookedge-backdoor-nato-police-shipbuilder-ssh-tunnel · ATT&CK page ↗

T1573.001Encrypted Channel: Symmetric Cryptography×1

Adversaries may employ a known symmetric encryption algorithm to conceal command and control traffic rather than relying on any inherent protections provided by a communication protocol. Symmetric encryption algorithms use the same key for plaintext encryption and ciphertext decryption. Common symmetric encryption algorithms include AES, DES, 3DES, Blowfish, and RC4.

Evidence: 2026-09-10/bluemoon-exploit-kit-four-state-actors-chrome-windows-chain · ATT&CK page ↗

Exfiltration TA0010

T1567.004Exfiltration Over Web Service: Exfiltration Over Webhook×1

Adversaries may exfiltrate data to a webhook endpoint rather than over their primary command and control channel. Webhooks are simple mechanisms for allowing a server to push data over HTTP/S to a client without the need for the client to continuously poll the server. Many public and commercial services, such as Discord, Slack, and `webhook.site`, support the creation of webhook endpoints that can be used by other services, such as Github, Jira, or Trello. When changes happen in the linked services (such as pushing a repository update or modifying a ticket), these services will automatically post the data to the webhook endpoint for use by the consuming application.

Evidence: 2026-09-24/closedquorum-llm-orchestrated-c2-implant · ATT&CK page ↗

Entries about Microsoft Edge (6)

2026-10-21 · view entry permalink →

NOTABLENATOB2

APT28 (Swallowtail) used the HOOKEDGE backdoor against a law-enforcement agency, a naval shipbuilder and an aircraft-engine maker in two NATO states; at the shipbuilder it then pushed an SSH key for a persistent tunnel, captured NTLM handshakes and ran a reflective loader

Symantec's Threat Hunter Team reports that Swallowtail, which it equates with APT28, Fancy Bear and Forest Blizzard, targeted organizations in two NATO member states: a law-enforcement agency, a naval shipbuilder and a manufacturer of military aircraft engines, none named (Symantec, 2026-10-20). Recorded Future had documented the HOOKEDGE backdoor in August, from campaigns between late September 2025 and early April 2026 against government and diplomatic organizations in Romania, Spain and Turkiye, and assesses with moderate confidence that BlueDelta, which overlaps APT28, is behind it (Recorded Future, 2026-08-27).

At the shipbuilder the vector was a macro-enabled Word document opened from the Outlook attachment cache on 2026-07-24, so it arrived by email; its macro dropped a VBScript launcher, an HTML pair that auto-submits a hidden form to a webhook endpoint and a batch script (Symantec, 2026-10-20). The batch script kills any running Microsoft Edge and restarts it as a one-pixel, off-screen window carrying an inline script instead of a URL, so the browser fetches the next task from the public webhook.site service, and the batch script then runs the task and uploads its output to the same endpoint (Symantec, 2026-10-20). A second stage then took its tasks from a dedicated address, and seven tasks arrived in about 30 seconds, a cadence Symantec reads as interactive (Symantec, 2026-10-20).

The operators then pushed an SSH private key onto the host and at once opened an outbound SSH session to their own server with host-key checking disabled, legacy RSA algorithms enabled and a background remote port forward, a persistent route into the internal network; separately a short PowerShell script ran an HTTP listener on loopback and net use against it, forcing the host to authenticate to itself so the NTLM handshake could be captured (Symantec, 2026-10-20). On 2026-07-31 they ran a previously undocumented reflective loader, which decrypts an encrypted file in memory; the payload was not recovered, and the launcher was last seen on 2026-09-24 (Symantec, 2026-10-20).

Triage: the distinctive sequence is an Office document's script host, then Edge killed and relaunched as a one-pixel off-screen window carrying an inline script instead of a URL; the Edge launch alone is not the signal.

Swallowtail (aka APT28, Fancy Bear, Forest Blizzard), a Russian espionage group, targeted organizations in two NATO member states, including a law enforcement agency, a naval shipbuilder, and a manufacturer of military aircraft engines.

Hookedge is delivered through macro-enabled Word documents and communicates entirely through the webhook.site service, using it to stage tasks and to receive their output.

Organizations that identify Hookedge indicators in their environment should treat the intrusion as potentially ongoing rather than concluded

Symantec Threat Hunter Team 2026-10-20

Organizations should prioritize blocking macro execution from internet-originated documents and implementing detection coverage for scheduled task abuse, headless Microsoft Edge execution, and outbound connections to webhook services.

Recorded Future Insikt Group 2026-08-27
threat21 Oct 03:44Zmulti-sourceOpen finding →

2026-09-10 · view entry permalink →

HIGHCVE-2026-85046 +2exploitedupdatedNATOB1

BlueMoon: six separate state-nexus actor clusters independently weaponize a shared Chrome V8 + Windows kernel zero-day chain

Proofpoint documents BlueMoon, a newly named exploit kit chaining a Chrome V8 JIT type-confusion bug (CVE-2026-85046) with an uncredentialed V8 sandbox escape and a Windows kernel ALPC/WNF heap-overflow local-privilege-escalation flaw (CVE-2026-85880) into a single click-to-SYSTEM chain (Proofpoint, 2026-09-08). The V8 bugs were a patch-gap zero-day: "the change containing the fix for CVE-2026-85046 was committed on 7 August 2026 but was not rolled into the general stable Chromium build until 3 September 2026" (Proofpoint, 2026-09-08), a nearly four-week window during which the public upstream diff let an exploit developer reverse-engineer and weaponize the bug before Chrome's stable channel shipped it; CVE-2026-85880 was separately patched by Microsoft as part of its September 2026 Patch Tuesday updates (The Hacker News, 2026-09-09); the referenced 2026-09-09 Windows entry covers Microsoft's own MSRC confirmation that it was exploited in the wild. After the browser-side chain achieves code execution and escapes the renderer sandbox, a reflectively loaded DLL fingerprints the host to decide whether to run the kernel LPE against a specific list of Windows builds, Proofpoint's own table names Windows 10 1809/2004/20H2/21H1/21H2/22H2, Windows 11 21H2's initial release build, and Server 2019/2022, a wider list than Microsoft's own advisory for this CVE, which describes the legacy line only and states it does not affect Windows 11 (Contradiction, unresolved here), then a process-injection stub runs an operator-supplied command inside the Chrome broker process, by default a plain curl download-and-execute, a deliberately crude step Proofpoint reads as evidence the developer traded stealth for speed. Four distinct espionage clusters adopted the identical kit within days of each other by Proofpoint's original count (a fifth, documented below, started 2026-09-01, within that same one-week span), each with its own delivery and payload: TA412/APT31 (from 2026-08-28) used student-internship and academic-conference spearphishing against US NGOs, mining and commodity-trading firms to install a malicious Chromium extension disguised as "Google Gemini" (GemStone), using an HMAC-forgery technique, named GhostChrome-X by outside researchers (The Hacker News, 2026-09-09), against Chrome's Secure Preferences integrity check so the extension survives the browser's own unauthorized-extension protection; GemStone keylogs, steals cookies/session storage, screenshots on keyword match and polls its C2 every 30 seconds to 60 minutes. UNK_LateNight (from 2026-09-02) targeted US aerospace/defense firms with B2B/RFQ lures to sideload the ShadowPad backdoor via a scheduled task. UNK_DoubleCheck (from 2026-09-02) phished a Vietnamese manufacturer from a compromised Southeast Asian government mailbox, obfuscating its loader and staging a second DLL from a Cloudflare R2 bucket. UNK_QuietRacket (from 2026-09-03) targeted government, consulting and financial-sector organizations in Indonesia and Singapore with conference-themed lures, resolving C2 entirely through DNS-over-HTTPS TXT-record lookups to a Cloudflare Worker. A Proofpoint researcher assessed the kit as shared rather than independently developed: "There's no way that this is parallel development," and "The code is practically identical, even the variable naming, the commentary. It's the same kit. One hundred percent." How the groups obtained it is undetermined, since Proofpoint could not say whether it came from a common contractor, was distributed by the state or spread through another shared channel (Mark Kelly, Proofpoint, via The Record, 2026-09-09). Patching Chrome and Windows closes the entry vector but removes nothing already installed, the GemStone extension, ShadowPad's DLL-sideload persistence, and the other clusters' scheduled tasks all survive a patch untouched.

Triage: a process tree rooted at the browser (browser → command shell → curl or a download utility → a newly dropped executable) is the chain's own crude final stage and a strong discriminator on its own; a scheduled task created immediately following a browser-initiated download narrows it further, since legitimate browser activity does not normally create scheduled tasks.

The change containing the fix for CVE-2026-85046 was committed on 7 August 2026 but was not rolled into the general stable Chromium build until 3 September 2026.

Proofpoint Threat Research 2026-09-08

While CVE-2026-85046 was patched by Google last week, CVE-2026-85880 was addressed by Microsoft as part of its September 2026 Patch Tuesday updates.

The Hacker News 2026-09-09

There’s no way that this is parallel development

The code is practically identical, even the variable naming, the commentary. It’s the same kit. One hundred percent.

The Record (Recorded Future News) 2026-09-09

Targets so far: NGO, Government, Consulting, Finance, Mining, Commodity Trading

NCSC Switzerland (GovCERT.ch) Cyber Security Hub 2026-09-12

The exploit first gains arbitrary read/write within the V8 sandbox through the Type confusion vulnerability (CVE-2026-85046), then combines a separate WebAssembly defect to escape the V8 sandbox (CVE-2026-87491). It then exploits a third vulnerability in the Windows kernel (CVE-2026-85880)

Volexity tracks this malware as GRIMWEDGE.

constructing a victim-specific URL using the victim device’s hostname

with a tab-delimited body containing the victim’s domain, username, and any command output from the loop’s previous run. HTTP responses to POST requests are evaluated as JScript code.

Volexity 2026-09-09
Updaterun 2026-09-13T0409Z-inteltitleheadlinesummarycvesentitiestechniquesreferencessourcesclassificationsourcing_notebody

NCSC Switzerland's own Cyber Security Hub advisory lists this chain's targets so far as "NGO, Government, Consulting, Finance, Mining, Commodity Trading" while stating no case has yet been reported in Switzerland (NCSC Switzerland, 2026-09-12). Volexity's own technical write-up, cited in that advisory, supplies the exploit chain's previously missing middle link: "the exploit first gains arbitrary read/write within the V8 sandbox through the Type confusion vulnerability (CVE-2026-85046), then combines a separate WebAssembly defect to escape the V8 sandbox (CVE-2026-87491)," before the Windows kernel flaw completes the escape to full code execution in the browser process (Volexity, 2026-09-09). Volexity names a fifth operator, UTA0560, which reached the chain through a reflected cross-site-scripting flaw on a legitimate US university website, unlike JungleBamboo's own delivery via attacker-registered domains fronted by Cloudflare Tunnels, and deployed GRIMWEDGE, an in-memory JScript backdoor under 250 lines that runs as an evaluated string inside msiexec.exe. Delivery chains through a dropper (msgbox.exe) that sideloads wsc.dll; wsc.dll beacons to a per-victim URL keyed on hostname to fetch and launch the next-stage MSI payload via msiexec.exe, and GRIMWEDGE itself, once running, instead sends HTTP POST requests carrying the victim's domain, username and prior command output to a single fixed command-and-control URL, with server responses evaluated as script; GRIMWEDGE supports ten commands including file read/upload, process control and command execution. Volexity separately documents JungleBamboo's (APT31/TA412) own payload chain: a loader it names SUPERSTOMP tampers with Chrome's Secure Preferences file, stripping and forging the per-preference integrity values to smuggle in a malicious extension impersonating "Google Gemini" past Chrome's own tamper checks; the resulting extension, LONGTALE, keylogs every keystroke and form or clipboard value across all open tabs, steals cookies and web-storage tokens, and takes keyword-triggered screenshots, exfiltrating collected data roughly every 30 seconds. This mechanism and disguise match Proofpoint's own GemStone/GhostChrome-X description of the same actor's tooling closely enough that the two vendor names may describe the same artifact rather than two distinct ones; neither vendor's own report confirms this directly, so both names are carried here without merging them.

An unexpected process loading wsc.dll and beaconing outbound over HTTPS to a per-hostname URL path, followed shortly by an msiexec.exe process installing whatever that beacon returned, is UTA0560's dropper-stage signature; a msiexec.exe process making repeated outbound HTTP POST requests to the same fixed destination with no corresponding user-initiated software installation is the discriminator for the GRIMWEDGE backdoor stage that follows it. A Chrome extension whose Secure Preferences integrity hash was set by a process other than Chrome itself, or that requests clipboard and all-tab permissions while impersonating a well-known AI-assistant name, is JungleBamboo's LONGTALE signature. Both persistence mechanisms, like the original entry's, survive the underlying browser and OS patches untouched.

Updaterun 2026-09-27T1308Z-audittitleheadlinesummaryentitiestechniquessourcesbody

A sixth cluster has been documented running this chain. Volexity's follow-up reporting names UTA0565, a China-nexus actor that exploited all three flaws on 3 and 4 September 2026, while every one of them was still unpatched (Volexity, 2026-09-21). The exploit kit itself is essentially unchanged: the embedded stage binaries are identical to the previously reported payloads, and the core exploit logic, version checks and stage sequencing are the same.

What differs is the delivery, and it is the part worth hunting on. Rather than the redirect-through-a-legitimate-site route the earlier operators used, UTA0565 sent phishing mail linking to domains it had registered itself to impersonate China Digital Times and the Center for American Progress, one lure urging support for an imprisoned Hong Kong activist and sent to Asian government entities, the other masquerading as the US policy institute. The one page still live when Volexity analysed it loaded most of its content from the legitimate site it copied and added the exploit components in a hidden, zero-sized iframe, so the page a victim saw was the real organization's content. The other site was already offline by then and is confirmed only as a visual clone of the outlet it impersonated, from a cached scan of the host that served it, so the same delivery mechanism is inferred there rather than observed. The final stage also changed: instead of a shell command that fetched and ran the payload, the kit now downloads the executable in-process, strips its Mark of the Web, and launches it through the Windows shell using COM, which removes both the command-line artifact and the zone-identifier evidence that earlier variants left behind.

The payload is a family Volexity had not previously documented and names CLEANGULP: a C binary obfuscated with control-flow flattening and indirect calls, installed under the user's local application-data path and persisted by a scheduled task, both named after a Microsoft input-method-editor component. Volexity assesses with high confidence that it supports command execution, process listing, file upload and download, and execution of beacon object files. Its command-and-control traffic runs over plain HTTP to a domain typosquatting a news publisher, with request and response bodies encrypted with AES-256-GCM and then encoded in a custom Base64 alphabet, the encryption key being derived from that alphabet string itself. Volexity pivoted on the registration pattern of the domains involved and assesses with medium confidence that several further domains, spanning spoofed media organizations, halal restaurant search sites and corporate training organizations, belong to the same campaigns.

For defenders the hunt moves one step earlier in the chain than the previous coverage suggested. A scheduled task and an executable both carrying an input-method-editor name under the user's local application-data tree, with no corresponding software deployment, is the on-host artifact; outbound HTTP carrying opaque binary bodies to a domain that is one transposition away from a news publisher the organization actually reads is the network one. Because the payload is launched through COM after an in-process download, process-lineage detections keyed on a browser spawning a command interpreter will not see this variant.

Correctionrun 2026-09-29T2134Z-auditevidencecvesbody

Proofpoint's researcher says the six clusters used the same kit, not that it was deliberately handed out. The Record reports that how the groups obtained the exploit within days of each other remains unclear, and that Proofpoint could not determine whether it came from a common contractor, was distributed by the state or spread through another shared channel (Mark Kelly, Proofpoint, via The Record, 2026-09-09). The analysis had described the adoption as deliberate distribution and now describes it as a shared kit reaching the clusters through an undetermined channel.

Builds on: Google ships an emergency Chrome update for a V8 flaw it says is already being exploited · Microsoft names two exploited Windows privilege-escalation zero-days, splitting the newest and… · Google ships an emergency Chrome fix for a seventh actively exploited V8 zero-day this year

threat10 Sep 04:50Zmulti-sourceOpen finding →

2026-09-24 · view entry permalink →

ROUTINEupdatedNATOB2

CLOSEDQUORUM: Cisco Talos documents what it calls, to its knowledge, the first publicly documented Windows implant that lets a panel of four commercial LLMs vote on its next action instead of a human operator

Cisco Talos disclosed CLOSEDQUORUM on 2026-09-22, a 16.4MB, 64-bit Go-compiled Windows implant it calls, "to our knowledge, the first publicly documented Windows implant to apply this model to tactical command and control" (Cisco Talos, 2026-09-22). Instead of a dedicated attacker-operated server, its ModelOrchestrator component queries up to four commercial LLM providers (DeepSeek, Qwen, Mistral and Google Gemini) each cycle, with a system prompt instructing each model to "provide ONLY executable decisions" alongside host context (hostname, OS version, admin status) and the current target process. Each provider must respond with a fixed JSON schema naming one of four actions; interModelDiscussion() tallies the providers' decisions by plurality vote and executes the winner, discarding any malformed or off-schema response. On a tie, a hardcoded preference order settles it: "DeepSeek holds the deciding vote in any tie" (Cisco Talos, 2026-09-22), followed by Qwen and then Mistral; if every provider fails to return a usable decision, the implant sleeps and retries rather than falling back to a default action.

The four possible actions are steal (simultaneous LSASS memory dumping via SeDebugPrivilege and MiniDumpWriteDump, Chrome/Edge/Firefox saved-credential harvesting, and MetaMask/Exodus/Ethereum wallet data collection), inject (Early Bird APC injection into a suspended process by default, or PEB-walk process hollowing when a model selects that exploit type), persist (establishes three mechanisms: a Windows-Update-themed Registry Run-key value, a scheduled task, and a permanent WMI event subscription that fires a script every 60 seconds), and move, which has no handler in the public build. The implant suppresses ETW telemetry by overwriting EtwEventWrite with a single RET instruction (Cisco Talos, 2026-09-22). Every model decision, its stated reasoning, and staged or stolen data are relayed to the operator through a Discord webhook, with exfiltrated files AES-256-GCM encrypted, base64-encoded and posted in roughly 1,900-byte chunks at one-second intervals. Talos found the binary via CAIRN, an open-source research toolkit for tracking AI-integrated malware that it released the same day, and its static analysis is dated 2026-06-17, under a prior alias, BALZAK, that was renamed on 2026-07-03. Talos's CAIRN toolkit is not the autonomous exploitation engine also named Cairn that Gambit Security documented in a separate 2026 campaign against online retailers (Gambit Security, 2026-09-22). Talos states plainly "we do not have confirmation of in-the-wild deployment," though artifacts in the binary connect its developer to carding-forum postings dating back to 2025 (Cisco Talos, 2026-09-22). The publicly distributed build ships with placeholder API keys and a dummy Discord webhook, so Talos has not observed a complete end-to-end execution; Talos assesses the actual distribution model puts a developer generating a customised binary with an individual operator's credentials injected at compile time, meaning any live deployment would run on infrastructure Talos has not seen.

Talos frames the finding as evidence of "effort displacement": an entire phase of an intrusion handed to a model rather than merely AI-assisted tooling. The Hacker News, reporting on the disclosure, draws its own comparison to LAMEHUG, malware Ukraine's CERT-UA reported in July 2025 that asked an AI model to write commands for a task already set in its code, contrasting it with CLOSEDQUORUM asking the models to choose the task itself (The Hacker News, 2026-09-23). Talos adds that handing the decision to models introduces weaknesses: "Provider refusals, rate limits, malformed output, predictable tie-breaking, constrained action schemas, and dependence on commercial APIs all create failure modes and defensive opportunities"; of these, only the tie behavior is one it calls "fully deterministic" (Cisco Talos, 2026-09-22).

exhibits fully autonomous command and control (C2). While we do not have confirmation of in-the-wild deployment, artifacts from the binary were used to connect the developer to postings on criminal forums related to carding, dating back to 2025.

CLOSEDQUORUM represents a shift in effort displacement for attackers, in which expanding portions of the attack chain can be executed without operator involvement.

CLOSEDQUORUM is, to our knowledge, the first publicly documented Windows implant to apply this model to tactical command and control (C2). After deployment, it delegates the selection of its next action to a panel of commercial large language models (LLMs) and executes the resulting decision, with the intent of harvesting user credentials and crypto wallets. It does not require continued commands from a human operator or tasking from a dedicated, attacker-operated C2 server; the complete dynamic operation is delegated to the AI.

DeepSeek holds the deciding vote in any tie

Provider refusals, rate limits, malformed output, predictable tie-breaking, constrained action schemas, and dependence on commercial APIs all create failure modes and defensive opportunities.

The tie behavior is fully deterministic and biased toward DeepSeek.

Cisco Talos 2026-09-22
Correctionrun 2026-10-11T1307Z-audittitlebodyclassificationverificationtechniquesreferencessources

Talos calls CLOSEDQUORUM, "to our knowledge", the first publicly documented Windows implant to apply this model to tactical command and control; the superlative is Talos's hedged assessment. The 2026-06-17 date is that of Talos's static analysis, not of a build. Talos says only that the implant suppresses ETW telemetry by overwriting EtwEventWrite with a single RET instruction, and it adds a five-minute initial delay and randomized 5 to 15 minute polling intervals to evade short-lived sandbox analysis (Cisco Talos, 2026-09-22).

Correctionrun 2026-10-20T0835Z-auditbodyevidencesummary

Talos does not call the implant's failure modes deterministic, and it does not present the sleep-and-retry response to total provider failure as a defender opportunity. Its list of weaknesses is "Provider refusals, rate limits, malformed output, predictable tie-breaking, constrained action schemas, and dependence on commercial APIs", which it says "all create failure modes and defensive opportunities"; the only behavior it calls "fully deterministic" is the tie-break, biased toward DeepSeek (Cisco Talos, 2026-09-22).

Builds on: Three off-the-shelf AI agents ran almost the entire card-theft campaign, from discovery to…

threat24 Sep 04:45Zsingle-sourceOpen finding →

Earlier coverage (3)

2026-09-21NOTABLENATOB2REF9334/KREMLIN forges Chromium's own Secure Preferences integrity hashes to silently install a banking-fraud browser extension outside the Web Store, resolving C2 through an Ethereum smart contractElastic Security Labs tracked REF9334, a Brazilian-banking-focused operation active across seven campaigns since May 2025, whose KREMLIN toolkit recovers Chromium's App-Bound encryption key directly from browser process memory, uses it to forge the HMACs and hashes Chromium's Secure Preferences integrity mechanism requires, and manually installs a malicious extension into the browser profile exactly as if a user had approved it through the Chrome Web Store, with no user interaction and no visible warning. The toolkit resolves its payload configuration through an Ethereum smart contract and abuses a legitimate SentinelOne binary for DLL sideloading.2026-09-10HIGHexploitedNATOA2CVE-2026-87491, Google Chrome: V8 out-of-bounds write exploited in the wild, patched in Chrome 153 (seventh exploited Chrome zero-day of 2026)Google's Chrome 153 stable release (2026-09-08) fixes CVE-2026-87491, an out-of-bounds write in the V8 JavaScript engine that Google confirms is already being exploited via a crafted HTML page. CERT-FR and NCSC-NL both flagged the CVE within a day of release; every Chromium-derived browser needs the equivalent update.2026-07-28NOTABLENATOB2MedusaHVNC: a malware-as-a-service RAT that drives the victim's own logged-in browser on an invisible second Windows desktopBlackFog analysed MedusaHVNC (2026-07-27), a Windows remote-access trojan sold as malware-as-a-service whose hidden-VNC module opens Chrome, Edge or Firefox on a separate, invisible Windows desktop using the victim's existing browser profile, so the operator drives live, already-authenticated sessions from the victim's own machine while the user sees nothing. The five-stage chain runs from an obfuscated JScript launcher through an AutoIt interpreter that XOR-decrypts a loader and injects it into charmap.exe, then unpacks the final payload behind repeating-XOR and ChaCha20 layers. Because the session originates from the real device with the real profile, controls that key on device fingerprint and session continuity see nothing unusual.

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Threats5
  • Vulns1

Source distribution

  • thehackernews.com3 (14%)
  • cisa.gov2 (9%)
  • volexity.com2 (9%)
  • advisories.ncsc.nl1 (5%)
  • blackfog.com1 (5%)
  • blog.talosintelligence.com1 (5%)
  • cert.ssi.gouv.fr1 (5%)
  • chromereleases.googleblog.com1 (5%)
  • other10 (45%)
All cited sources (22)