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

Mozilla Firefox

product · product:mozilla-firefox single-source

Coverage
4
first 2026-07-17 → last 2026-10-20
Latest activity
2026-09-24
A malware implant treats commercial AI chatbot endpoints as its command-and-control infrastructure, no…
Peak priority
high
1 high · 2 notable · 1 routine
Targets
public-sector
sectors: public-sector, defense, telco · regions: middle-east, apac
Sources cited
9
9 hosts

Action items (1)

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

  • Expedite the Firefox 152.0.6 update across managed and Firefox-ESR desktop fleets rather than waiting on the normal auto-update cadence, public exploit code for the CVE-2026-15718/-15719 chain raises the exploitation window now, even though no in-the-wild abuse is yet confirmed.
    2026-07-17CVE-2026-15718 +1

Defender insights

What each entry about Mozilla Firefox tells a defender to do, newest first.

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

Triage · detection

2026-08-16HIGHA hack-for-hire group hit 15+ government webmail tenants with one script tag, then escaped the browser via a fake Edge helper

Triage

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

Triage

2026-07-17NOTABLEMozilla patches a WebAssembly memory bug and a site-isolation bypass in Firefox 152.0.6; exploit code is public, no confirmed in-the-wild abuse

Story timeline

  1. 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
  2. 2026-08-16Jewelbug: one script tag in a shared government webmail template put a watering hole on 15+ ministry tenants at once, and the browser extension it drops escapes the sandbox through a native-messaging host named after Microsoft Edge
    deep-diveA hack-for-hire group hit 15+ government webmail tenants with one script tag, then escaped the browser via a fake Edge helper
  3. 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
  4. 2026-07-17Firefox 152.0.6, chained WebAssembly memory-safety and DOM-navigation site-isolation flaws with public exploit code (CVE-2026-15718, CVE-2026-15719)
    trending-vulnerabilitiesMozilla patches a WebAssembly memory bug and a site-isolation bypass in Firefox 152.0.6; exploit code is public, no confirmed in-the-wild abuse
ATT&CK techniques (29 across 11 tactics)

29 techniques observed across 4 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)

  • Initial AccessDrive-by Compromise
  • ExecutionScheduled Task/Job: Scheduled Task · Command and Scripting Interpreter: Windows Command Shell · Command and Scripting Interpreter: JavaScript · Exploitation for Client Execution · User Execution: Malicious File
  • PersistenceScheduled Task/Job: Scheduled Task · Software Extensions: Browser Extensions · Event Triggered Execution: Windows Management Instrumentation Event Subscription · Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder · Modify Authentication Process: Pluggable Authentication Modules
  • Privilege EscalationScheduled Task/Job: Scheduled Task · Process Injection · Process Injection: Asynchronous Procedure Call · Process Injection: Process Hollowing · Event Triggered Execution: Windows Management Instrumentation Event Subscription · Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder
  • StealthRootkit · Process Injection · Process Injection: Asynchronous Procedure Call · Process Injection: Process Hollowing · Deobfuscate/Decode Files or Information · Virtualization/Sandbox Evasion: Time Based Checks · Hide Artifacts: Hidden Window
  • Defense ImpairmentModify Authentication Process: Pluggable Authentication Modules · Disable or Modify Tools
  • Credential AccessOS Credential Dumping: LSASS Memory · Input Capture: Web Portal Capture · Steal Web Session Cookie · Credentials from Password Stores: Credentials from Web Browsers · Modify Authentication Process: Pluggable Authentication Modules
  • DiscoveryVirtualization/Sandbox Evasion: Time Based Checks
  • CollectionInput Capture: Web Portal Capture · Screen Capture · Clipboard Data · Browser Session Hijacking
  • Command and ControlProxy · Web Service: Dead Drop Resolver · Web Service: Bidirectional Communication
  • ExfiltrationExfiltration Over Web Service: Exfiltration Over Webhook

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-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · 2026-07-17/firefox-152-0-6-wasm-site-isolation-public-exploit · ATT&CK page ↗

Execution TA0002

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

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-09-24/closedquorum-llm-orchestrated-c2-implant · 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-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · 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×1

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-07-17/firefox-152-0-6-wasm-site-isolation-public-exploit · ATT&CK page ↗

T1204.002User Execution: Malicious File×1

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-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · ATT&CK page ↗

Persistence TA0003

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

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-09-24/closedquorum-llm-orchestrated-c2-implant · ATT&CK page ↗

T1176.001Software Extensions: Browser Extensions×1

Adversaries may abuse internet browser extensions to establish persistent access to victim systems. Browser extensions or plugins are small programs that can add functionality to and customize aspects of internet browsers. They can be installed directly via a local file or custom URL or through a browser's app store - an official online platform where users can browse, install, and manage extensions for a specific web browser. Extensions generally inherit the web browser's permissions previously granted.

Evidence: 2026-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · 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 ↗

T1556.003Modify Authentication Process: Pluggable Authentication Modules×1

Adversaries may modify pluggable authentication modules (PAM) to access user credentials or enable otherwise unwarranted access to accounts. PAM is a modular system of configuration files, libraries, and executable files which guide authentication for many services. The most common authentication module is <code>pam_unix.so</code>, which retrieves, sets, and verifies account authentication information in <code>/etc/passwd</code> and <code>/etc/shadow</code>.

Evidence: 2026-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · ATT&CK page ↗

Privilege Escalation TA0004

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

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-09-24/closedquorum-llm-orchestrated-c2-implant · ATT&CK page ↗

T1055Process Injection×1

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-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 ↗

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

T1014Rootkit×1

Adversaries may use rootkits to hide the presence of programs, files, network connections, services, drivers, and other system components. Rootkits are programs that hide the existence of malware by intercepting/hooking and modifying operating system API calls that supply system information.

Evidence: 2026-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · ATT&CK page ↗

T1055Process Injection×1

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-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 ↗

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 ↗

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×1

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-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

Defense Impairment TA0112

T1556.003Modify Authentication Process: Pluggable Authentication Modules×1

Adversaries may modify pluggable authentication modules (PAM) to access user credentials or enable otherwise unwarranted access to accounts. PAM is a modular system of configuration files, libraries, and executable files which guide authentication for many services. The most common authentication module is <code>pam_unix.so</code>, which retrieves, sets, and verifies account authentication information in <code>/etc/passwd</code> and <code>/etc/shadow</code>.

Evidence: 2026-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · 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.003Input Capture: Web Portal Capture×1

Adversaries may install code on externally facing portals, such as a VPN login page, to capture and transmit credentials of users who attempt to log into the service. For example, a compromised login page may log provided user credentials before logging the user in to the service.

Evidence: 2026-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · 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-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

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

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-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

T1556.003Modify Authentication Process: Pluggable Authentication Modules×1

Adversaries may modify pluggable authentication modules (PAM) to access user credentials or enable otherwise unwarranted access to accounts. PAM is a modular system of configuration files, libraries, and executable files which guide authentication for many services. The most common authentication module is <code>pam_unix.so</code>, which retrieves, sets, and verifies account authentication information in <code>/etc/passwd</code> and <code>/etc/shadow</code>.

Evidence: 2026-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · ATT&CK page ↗

Discovery TA0007

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.003Input Capture: Web Portal Capture×1

Adversaries may install code on externally facing portals, such as a VPN login page, to capture and transmit credentials of users who attempt to log into the service. For example, a compromised login page may log provided user credentials before logging the user in to the service.

Evidence: 2026-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · 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-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · ATT&CK page ↗

T1115Clipboard Data×2

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

Evidence: 2026-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

T1185Browser Session Hijacking×2

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-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · 2026-07-28/medusahvnc-hidden-desktop-browser-session-hijacking · ATT&CK page ↗

Command and Control TA0011

T1090Proxy×1

Adversaries may use a connection proxy to direct network traffic between systems or act as an intermediary for network communications to a command and control server to avoid direct connections to their infrastructure. Many tools exist that enable traffic redirection through proxies or port redirection, including HTRAN, ZXProxy, and ZXPortMap. Adversaries use these types of proxies to manage command and control communications, reduce the number of simultaneous outbound network connections, provide resiliency in the face of connection loss, or to ride over existing trusted communications paths between victims to avoid suspicion. Adversaries may chain together multiple proxies to further disguise the source of malicious traffic.

Evidence: 2026-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · 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-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · 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-09-24/closedquorum-llm-orchestrated-c2-implant · 2026-08-16/jewelbug-pdf-viewer-extension-native-messaging-webmail-hole · 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 Mozilla Firefox (4)

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 →

2026-08-16 · view entry permalink →

HIGHNATOB2

Jewelbug: one script tag in a shared government webmail template put a watering hole on 15+ ministry tenants at once, and the browser extension it drops escapes the sandbox through a native-messaging host named after Microsoft Edge

Symantec's Threat Hunter Team has published the results of a months-long investigation into Jewelbug, a China-based hack-for-hire group that runs two missions from one set of hands: espionage against government ministries and militaries across the Middle East, Southeast Asia and South Asia, and a for-profit cryptocurrency-fraud business aimed at Chinese-speaking victims. Both are administered from a single control panel called XG-Web, a browser-centric remote-access and information-stealing framework built as a React panel over a Node.js backend with a MySQL database that doubles as the rendezvous point for victim implants; its developers describe it in their own documentation as a "penetration-testing platform", while its internal function names include browser hijacking, data theft and man-in-the-middle attack (Symantec, 2026-08-13). Symantec assesses with high confidence that the fraud and search-engine-optimisation arm is run by the sole legal representative of a registered Changsha company, on the basis of government-issued identity documents, a business licence and a signed authorisation letter recovered from the operators, and considers it most likely that the SEO business supplied access, infrastructure and delivery to the espionage operation rather than one person performing both roles (Symantec, 2026-08-13).

The access pattern is the finding. In its largest espionage operation, Jewelbug did not attack ministries individually. It compromised the shared web-hosting platform run by a Middle Eastern state telecommunications provider and national network-services agency, obtained write access to the common webmail installation, and added one script tag, planting a watering hole on every government tenant on that platform at once, in a single campaign that spanned more than 15 tenants (Symantec, 2026-08-13). Symantec infers the tag sat in the shared template rather than being delivered per user because the hook fired on the login page and on every mailbox view. The group also hooked the hosting provider's own administrators to harvest the credentials that granted that write access, which closes the loop: the platform operator's identity was the key to every tenant behind it.

The chain that follows is short and entirely conventional in its parts, which is what makes it worth mapping. When a ministry staff member logged in, the injected script opened a WebSocket to command-and-control, completed a handshake and reported in; a cookie module exfiltrated the page's cookies, and a labelling module read the username straight out of the webmail interface and tagged the new victim with their government email address. Only then did the operators push a lure module, which checked that the address ended in one of nine targeted government domains, that the account was not already compromised, and that the host was Windows, before overlaying a fake Adobe Flash update prompt (Symantec, 2026-08-13). That server-side qualification step is a defensive problem in itself; the malicious behaviour a visiting analyst or a sandbox sees is a cookie read and a WebSocket, because the payload stage never fires for a visitor who fails the filter.

Clicking the prompt downloaded the Antino backdoor, delivered as a fake Adobe Flash or Adobe installer and using the Microsoft Graph API as its command-and-control channel so its traffic sits inside legitimate Microsoft cloud services. Antino also side-loaded the "PDF Viewer" extension into the victim's browser profile, dropped a native-messaging helper and wrote the registry value that enabled it (Symantec, 2026-08-13). The extension is the group's primary implant and requested, in Symantec's words, effectively every dangerous permission the browser exposes, cookies, scripting, debugger access, web-request interception, download monitoring and native messaging across all sites. A background service worker gave the operator a full bridge into the browser API: any Chrome or Firefox function invocable by name, arbitrary JavaScript injected into any page, credentials harvested by hooking login forms, the full cookie jar exfiltrated, live cookie-change events subscribed to so new session tokens are stolen in near real time, plus history, bookmarks, screenshots, clipboard and intercepted traffic. A clipboard module able to swap a copied cryptocurrency address for the attacker's was present and active on victims, but Symantec records that no address-replacement rules were deployed, so the swap was not used during the observed period.

The sandbox escape is the part defenders should take away. To reach the host, the extension talked to a Windows helper registered as a native-messaging host under the misleading name com.microsoft.runedge, which ran operator commands through the Windows command interpreter and returned output to the panel; Antino wrote the enabling registry value under the current user's own hive (Symantec, 2026-08-13). Native messaging is a documented, legitimate browser feature (it is how password managers and document tools talk to their desktop components) and that is precisely why it works here. For at least one victim the bridge carried authenticated traffic to an internal virtualisation-management interface, so browser access became reach into the network behind it.

The group's toolset extends past the browser. Symantec counts 37 builds of a Rust implant the developers call ClientKing, reaching servers and network devices rather than browsers, supporting five command-and-control transports including a custom DNS tunnel, and offering an interactive shell, SOCKS pivoting and the ability to load kernel modules directly from memory; a companion toolkit adds a kernel-module rootkit and a malicious authentication module hooked into su and sudo to steal credentials, across x86-64 servers, ARM64 devices and consumer routers (Symantec, 2026-08-13). For payload delivery the backend created public Google Documents, wrote an obfuscated payload into the body and had implants fetch and execute it, which resolves to Google-owned infrastructure that reputation filtering is unlikely to block, and the group disguised its command-and-control hostnames as typosquats of common web resources such as font services. A scheduled job checked the group's own domains against a public multi-scanner every twelve hours so operators could rotate away from anything flagged.

Scale, in the group's own bookkeeping: the victim database holds more than one million implant check-in rows, more than 580,000 stolen browser cookies, several thousand captured credentials and more than 2,300 exfiltrated email bodies (Symantec, 2026-08-13). Symantec also notes builds configured to beacon through the internal corporate proxy of a major US aerospace and industrial manufacturer, so the tooling is not confined to government estates.

Triage: a native-messaging host registered under HKCU\SOFTWARE\<browser>\NativeMessagingHosts\<reverse-domain-name> is normal on its own, legitimate password managers, document viewers and enterprise agents use this exact mechanism. Three discriminators separate this from that baseline, and they derive from the mechanics the source describes rather than from any indicator: a host name asserting a Microsoft identity while being written per-user under HKCU by a downloaded executable, where a genuine Microsoft browser component arrives through a signed machine-wide installer; the command interpreter appearing with a native-messaging host executable as its parent, a process-lineage pair that legitimate browser-helper traffic does not produce; and an extension whose manifest requests native messaging together with debugger access, web-request interception and all-sites cookie access, a permission combination a document reader has no use for. The extension side-loads into the browser profile rather than arriving from a store, so an extension inventory built only from store IDs will not see it.

Rather than breach each ministry separately, Jewelbug compromised the shared web-hosting platform run by the state telecommunications provider and national network-services agency, obtaining write access to the common webmail installation, and added a single script tag.

A single campaign spanned more than 15 government webmail tenants, with the hook firing on the login page and every mailbox view, indicating it sat in the shared template rather than being delivered per user.

To escape the browser sandbox, the extension talked to a Windows helper registered as a native-messaging host under the misleading name com.microsoft.runedge, which ran operator commands through the Windows command interpreter and returned the output to the panel.

Masquerading as a document reader, it requested effectively every dangerous permission the browser exposes: cookies, scripting, debugger access, web request interception, download monitoring, and native messaging across all sites.

Symantec Threat Hunter Team
threat16 Aug 04:40Zsingle-sourceOpen finding →

2026-07-28 · view entry permalink →

NOTABLENATOB2

MedusaHVNC: a malware-as-a-service RAT that drives the victim's own logged-in browser on an invisible second Windows desktop

The interesting property of MedusaHVNC is not that it steals credentials (it does, and advertises a "Browser Recovery" feature for passwords, cookies and history across Chrome, Edge, Brave, Firefox and Telegram) but that it makes stealing them partly unnecessary. Its hidden-VNC module opens a real browser on a second, invisible Windows desktop, and because "[t]he browser still runs on the victim's device, so it can load an existing profile, including cookies and session state", the operator inherits whatever the user is already logged into (BlackFog, 2026-07-27). The resulting traffic leaves the victim's machine, from the victim's network, with the victim's browser profile and device characteristics, which is the entire point, since the fraud and risk-engine controls that would normally challenge a session key on exactly those signals. SecurityWeek's account of the same research notes that hidden desktops are a legitimate Windows capability used by specialised software and only occasionally by malware (SecurityWeek, 2026-07-27).

The delivery chain is five stages and leans on trusted components throughout. Windows Script Host executes an obfuscated JScript launcher, which sleeps for just over seven and a half seconds before reconstructing its embedded files into a randomly named subfolder of %TEMP% (an AutoIt interpreter, a configuration file and an extensionless encrypted payload) and dropping a batch file into the Startup folder for persistence. The AutoIt component runs without a visible window, decrypts the payload with a single-byte XOR key to produce a native 64-bit loader, and then launches C:\Windows\System32\charmap.exe, the Character Map utility, into which the loader is injected; BlackFog notes this stage is corroborated by a public sandbox process tree showing charmap.exe as a child of the AutoIt process. Inside that host process two further layers come off (a 16-byte repeating XOR across roughly a megabyte of the .data section, then ChaCha20 with a 32-byte key and 12-byte nonce) yielding an unsigned PE32+ console executable carrying a .pay section and the family string. Alongside the hidden desktop, the seller's own panel advertises a "Mem Exec" feature described as running .NET and native payloads in memory with an AMSI patch and ETW bypass, security-tooling tampering that BlackFog reports from the marketplace listing rather than from the analysed sample, so it should be treated as claimed capability rather than confirmed behaviour. The payload speaks a custom protocol over raw TCP via native Winsock calls to a hardcoded endpoint, and its imported API surface is what BlackFog reads as the HVNC workflow: BitBlt, EnumWindows and PrintWindow for screen and window capture, SendInput and SetWindowsHookExW for synthetic input, and the clipboard functions for moving data into and out of the session (BlackFog, 2026-07-27).

Triage: charmap.exe is the sharpest discriminator in the chain. The Character Map is an interactive accessory a user opens from the Start menu; an instance spawned by a scripting or automation interpreter, running with no window, holding a network socket, or hosting injected code is not a benign variant of that behaviour. Around it, look for the sequence rather than any single event, wscript.exe executing script content that writes an AutoIt interpreter into a %TEMP% subfolder, a Startup-folder write from that same process tree, and an AutoIt binary running from a user-writable path where the organisation does not deploy AutoIt. Legitimate AutoIt use exists in many estates, which is why the parent chain and the write location matter more than the interpreter's presence. The hidden desktop itself is the weakest thing to hunt for, since the capability is a supported Windows feature with genuine software using it.

The browser still runs on the victim’s device, so it can load an existing profile, including cookies and session state.

The AutoIt stage then starts C:\\Windows\\System32\\charmap.exe, the standard Windows Character Map utility. The public sandbox process tree shows charmap.exe as a child of the AutoIt process, and the loader is injected into it, using the trusted system binary as a host for the payload.

BlackFog 2026-07-27

Hidden desktops are a legitimate Windows capability, often used by specialized software, and occasionally used by malware.

SecurityWeek 2026-07-27
threat28 Jul 04:55Zsingle-sourceOpen finding →

Earlier coverage (1)

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

  • Threats2
  • Vulns1
  • Deep dive1

Source distribution

  • advisories.ncsc.nl1 (11%)
  • blackfog.com1 (11%)
  • bleepingcomputer.com1 (11%)
  • blog.talosintelligence.com1 (11%)
  • gambit.security1 (11%)
  • mozilla.org1 (11%)
  • security.com1 (11%)
  • securityweek.com1 (11%)
  • other1 (11%)