CLOSEDQUORUM: Cisco Talos Finds the First Malware That Uses Autonomous AI to Decide Its Attacks

By Carlos Montiel | Enterprise AI Specialist
Leer en español →
Published: 2026-09-24 | By: Carlos Montiel | Reading time: ~5 minutes

On September 22, Cisco Talos published the first documented analysis of malware that doesn't wait for orders from a traditional command-and-control server, but instead decides them in real time by consulting four commercial language models. Dubbed CLOSEDQUORUM, the implant puts every tactical decision to a vote among DeepSeek, Qwen, Mistral, and Gemini — with no human operator anywhere in the chain.

How it decides its attacks

CLOSEDQUORUM is a 16.4MB Windows executable compiled in Go, built to steal credentials and cryptocurrency wallets. Instead of taking instructions from an attacker-controlled domain, the implant gathers information from the compromised machine, sends it as structured context to up to four different model providers, and executes whichever action wins the vote from a fixed set of options: steal, inject, persist, or move. In case of a tie, DeepSeek gets tie-breaking priority, followed by Qwen, Mistral, and Gemini.

CAIRN, the toolkit Talos released to hunt it

Alongside the analysis, Talos released CAIRN, an open-source research toolkit built to track AI-integrated malware, using a detection approach based on the metadata of model calls rather than traditional network signatures. This is the first time a threat intelligence team of this size has released tooling specifically for this threat category.

Is it being used in the wild? Talos was explicit: it has no confirmation of active CLOSEDQUORUM deployment. The publicly observed binary contains placeholder API credentials and a fake Discord webhook, making it non-functional as it currently circulates. What matters isn't that this specific sample is attacking companies today — it's that it proves the pattern itself — delegating tactical decisions to a panel of commercial LLMs over API — is already technically viable and reproducible.

Why this changes detection

The conceptual leap is that the malware's "orders" no longer travel as beaconing traffic to a suspicious domain — they arrive as API calls to legitimate AI providers, the same kind of traffic generated by thousands of ordinary corporate applications. That means blocking known C2 domains or IPs is no longer enough: detection has to look at behavior (which process is calling which API, how often, and for what) instead of relying on blocklists.

What this means for your business: if your security team still relies mainly on domain/IP blocking to catch C2 traffic, this case is a signal to add process-level behavioral monitoring — specifically, unrecognized processes making outbound calls to model-provider APIs (OpenAI, Anthropic, DeepSeek, Mistral, Google) outside of IT-approved applications. Check with your EDR/XDR vendor whether they already cover this specific pattern, and start treating LLM API calls as a surface that deserves the same visibility as outbound DNS traffic.
Carlos Montiel
Enterprise AI Solutions Architect
Specialist in LLMs, Agents, and Orchestration
guatemalia.com/#contact · info@guatemalia.com

Need to implement AI in your business?

Carlos Montiel is an enterprise AI solutions architect. He implements LLMs, Agents, RAG, and orchestrators for businesses in Guatemala and Latin America. Reach out for a consultation.

Contact Carlos Montiel

info@guatemalia.com