Cisco Talos Unveils CLOSEDQUORUM, an Autonomous AI-Driven Malware

CLOSEDQUORUM: First Malware Found Using AI Panel for C2 Decisions

HIGH
September 23, 2026
5m read
MalwareThreat IntelligenceCloud Security

Related Entities

Products & Tech

Google GeminiDeepSeekQwenWindows CAIRN

Other

CLOSEDQUORUMDiscord

Full Report

Executive Summary

Cisco Talos has published research on a novel Windows malware implant, dubbed CLOSEDQUORUM, which represents what is believed to be the first publicly documented instance of malware using a panel of commercial Large Language Models (LLMs) for command and control (C2). This Go-based malware is designed to operate autonomously after deployment, removing the need for a human operator and traditional C2 infrastructure. It queries a 'quorum' of four AI models—Google Gemini, DeepSeek, Alibaba's Qwen, and Mistral—to determine its next action, which includes credential theft, code injection, and persistence. The sample analyzed contained placeholder API keys, suggesting it is a malware kit being sold to other criminals, and there is no evidence of its use in live attacks yet.

Threat Overview

CLOSEDQUORUM marks a significant evolution in malware design, shifting from static, human-driven commands to dynamic, autonomous decision-making powered by AI. After initial infection, the 16.4MB binary periodically (every 5-15 minutes) queries the four hardcoded LLMs. It provides them with the current host state and a system prompt instructing them to act as an "advanced malware strategist." The LLMs are constrained to choose from a predefined set of actions. The malware tallies the 'votes' from the AI panel and executes the majority decision, with the DeepSeek model acting as a tie-breaker. This decentralized, consensus-based C2 mechanism makes the malware resilient to the takedown of any single AI service and harder to predict.

Technical Analysis

To aid in the detection of similar threats, Talos has released an open-source toolkit called CAIRN (Cognitive Artifact Intelligence Research Network), which helps researchers hunt for AI-integrated malware.

Impact Assessment

While CLOSEDQUORUM has not been observed in the wild, its architecture represents a significant threat. Autonomous malware reduces the operational burden on attackers, allowing them to scale campaigns more effectively. The use of commercial LLM APIs for C2 makes attribution and takedown more difficult, as traffic blends in with legitimate API calls. If deployed successfully, this type of malware could react dynamically to a target environment without human intervention, potentially bypassing static defenses and responding to security measures in real-time. The sale of this as a kit could put sophisticated, autonomous attack capabilities into the hands of less-skilled threat actors.

Cyber Observables — Hunting Hints

The following patterns could indicate activity related to CLOSEDQUORUM or similar AI-driven malware:

Type
url_pattern
Value
generativelanguage.googleapis.com, api.mistral.ai
Description
Repetitive outbound connections from unexpected processes to known commercial LLM API endpoints.
Context
Web proxy logs, DNS logs, Firewall logs
Type
network_traffic_pattern
Value
Periodic (5-15 min) outbound connections to multiple LLM APIs
Description
The malware's beaconing behavior to its AI panel would create a regular, observable traffic pattern.
Context
Netflow analysis, SIEM correlation
Type
url_pattern
Value
discord.com/api/webhooks/
Description
Outbound POST requests to Discord webhooks from non-browser processes are a strong indicator of data exfiltration.
Context
Web proxy logs, EDR process monitoring
Type
process_name
Value
Unusual Go-based binaries making network connections
Description
A large, statically-linked Go binary making connections to LLM APIs and Discord would be highly anomalous on a typical user workstation.
Context
EDR, Process execution logs

Detection & Response

  1. Egress Traffic Filtering: The most effective control is to restrict and monitor outbound web traffic. By default, deny connections to commercial LLM APIs and services like Discord from servers and non-essential workstations. Create explicit allow rules for legitimate use cases. This is a core tenet of Outbound Traffic Filtering.

  2. API and DNS Query Logging: Log all DNS queries and web proxy traffic. Hunt for patterns of requests to multiple LLM API domains (generativelanguage.googleapis.com, api.mistral.ai, api.deepseek.com, etc.) from a single host in a short time frame. This aligns with Network Traffic Analysis.

  3. Process Monitoring: Use an EDR solution to monitor for suspicious process behavior. A Go binary that does not have a legitimate business purpose and is observed performing credential dumping, process injection, or making outbound connections to LLM APIs should be immediately investigated. This is an example of Process Analysis.

Mitigation

  1. Application Allowlisting: Implement application allowlisting to prevent the execution of unauthorized binaries, such as a novel Go-based implant. This is a form of Executable Allowlisting.

  2. Credential Access Protection: Employ modern credential protection mechanisms like Windows Credential Guard to make it more difficult for malware to dump credentials from memory. Enforce MFA on all critical accounts to mitigate the impact of stolen credentials.

  3. AI Governance Policy: Establish a clear corporate policy on the use of generative AI tools. Use security tools to discover and control the use of these services, blocking access where necessary and monitoring data flows to prevent sensitive information from being sent to external models.

Timeline of Events

1
September 23, 2026
This article was published

MITRE ATT&CK Mitigations

Block outbound connections to known LLM APIs and services like Discord from general-purpose systems to disrupt C2 and exfiltration.

Mapped D3FEND Techniques:

Use application allowlisting to prevent unknown Go binaries from running.

Mapped D3FEND Techniques:

Enable features like Windows Credential Guard to protect credentials stored in memory.

D3FEND Defensive Countermeasures

The most direct way to counter CLOSEDQUORUM's C2 and exfiltration channels is through strict outbound traffic filtering. Organizations should implement a default-deny policy for connections to external web services, especially from servers and sensitive workstations. Specifically, create rules on perimeter firewalls and web proxies to block all traffic to known commercial LLM API endpoints (e.g., generativelanguage.googleapis.com, api.mistral.ai) and data exfiltration destinations like discord.com/api/webhooks/. Legitimate business use of these services should be managed through explicit allow rules for specific user groups or source IPs, forcing all such traffic through a monitored and inspected channel. This containment strategy effectively blinds the malware, preventing it from receiving commands or exfiltrating stolen data.

To prevent the initial execution of the CLOSEDQUORUM implant, organizations should deploy application allowlisting solutions like AppLocker or third-party tools. On critical servers and user workstations, configure policies to only allow known, signed, and approved executables to run. Since CLOSEDQUORUM is an unsigned Go-based binary, a properly configured allowlisting policy would block it from executing in the first place. This proactive defense is highly effective against novel malware that does not have a known signature. While initial setup requires baselining the environment, it provides a powerful defense against unauthorized code execution.

Utilize an Endpoint Detection and Response (EDR) tool to perform continuous process analysis. Create detection rules that correlate multiple suspicious behaviors. For example, a rule could trigger an alert for any process that is 1) an unsigned executable, 2) makes network connections to multiple distinct LLM API domains within a 15-minute window, and 3) attempts to access memory of processes like lsass.exe or read files from browser profile directories. This behavioral, multi-faceted detection approach is more resilient than relying on single indicators and is well-suited to identifying the unique activity pattern of an AI-driven implant like CLOSEDQUORUM.

Sources & References

The Closed Quorum: Inside the first reported autonomous AI C2 implant
Cisco Talos (blog.talosintelligence.com) September 22, 2026
New malware lets commercial AI models call the shots: Talos
iTnews (itnews.com.au) September 22, 2026
Researchers uncover malware that uses AI to choose its next move
Help Net Security (helpnetsecurity.com) September 22, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

AIMalwareCisco TalosLLMC2AutonomousGoWindows

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.