The AI malware CLOSEDQUORUM makes its own attack decisions. Instead of waiting for an operator, it asks four public AI models to vote on its next move, then steals credentials, injects code, or sets up persistence based on the winner. Researchers first documented it on September 23, 2026, and no confirmed victims exist yet.
What Is the AI Malware CLOSEDQUORUM?
Most malware still needs a human operator. Ransomware crews run command and control (C2) servers precisely because their payloads need real time instructions on what to do next and when to trigger. However, that same infrastructure is where defenders catch them. Disrupt the C2 channel, and the attack stalls.
Therefore, the AI malware CLOSEDQUORUM was built to remove that dependency. Rather than calling back to an attacker controlled server, the implant queries public AI models and lets them vote on the next move. The operator configures it once, deploys a customized copy, and then the software makes its own tactical choices through commercial AI services that developers reach every day.
Security researchers first documented the implant on September 23, 2026. Its significance is not the damage it has caused, because no confirmed victims exist. Instead, its significance is the design principle it proves and the detection gap that principle opens for every enterprise that still leans on signature based or C2 blocking defenses. This builds on the pattern we recorded in our 2026 Mid-Year Threat Pattern Report, which ranked AI augmented attacks as the fourth dominant threat pattern of 2026 and 14 percent of confirmed incidents in our dataset from January to August.
How Does the AI Malware CLOSEDQUORUM Use AI Models to Choose Its Attacks?
When CLOSEDQUORUM runs on an infected Windows machine, it first collects basic host details: the operating system version, the processor count, and whether it holds administrator rights. Then it sends that context as a structured prompt to as many as four AI models at once.
The four models are DeepSeek, Qwen, Mistral and Gemini. Importantly, each one receives a limited menu of choices rather than an open invitation to invent any attack. This is deliberate. By constraining the AI to a fixed list, the author keeps the output predictable enough to parse and act on automatically, while still handing the tactical decision to an outside reasoner.
Each model returns a structured choice, and the malware tallies the votes. The most popular choice wins. When two or more models agree, that action runs. When no clear winner appears, a tie breaking order applies, and it starts with DeepSeek. If no usable response arrives, the implant pauses and retries instead of acting on its own. Moreover, the retry loop runs at irregular intervals of five to fifteen minutes after an initial delay, a timing pattern that mimics legitimate background application behavior.
What Can CLOSEDQUORUM Actually Do Once It Lands?
The votes choose from a short menu. Specifically, the AI malware CLOSEDQUORUM can steal credentials from Windows login stores, saved browser passwords and cryptocurrency wallet files, inject executable code into another running process to hide under a legitimate program, or set up a persistence mechanism that restarts the malware after a reboot.
A fourth listed action, lateral movement across a network, has no working handler in the build that researchers analyzed. That qualification matters. The current public build cannot spread on its own. The operator still chooses where to place a customized copy and still supplies the API keys that reach the AI models. In short, the autonomous element is the tactical decision loop once the implant runs, not the initial compromise or the deployment.
Stolen material travels out through a Discord webhook. The implant also uses a date derived encryption key for its traffic. Researchers noted that this choice creates an extra complication, because a developer who knows the derivation method could decode any operator’s collected data. In effect, that would give the author a view into what every operator steals.
Here are the confirmed facts at a glance.
| Item | Detail |
|---|---|
| Name | CLOSEDQUORUM |
| Type | Windows malware implant that uses AI for tactical decisions |
| First documented | September 23, 2026 |
| AI models queried | DeepSeek, Qwen, Mistral, Gemini |
| Autonomous element | The decision loop after deployment, not the initial compromise |
| Lateral movement | Listed as an action, but not implemented in the analyzed build |
| Confirmed victims | None in the public build |
| Exfiltration | Discord webhook with a date derived encryption key |
Why Does the AI Malware CLOSEDQUORUM Evade Traditional Detection?
Traditional detection leans on two overlapping methods. First, signature detection matches known malicious code patterns, file hashes or behavioral sequences against a database of confirmed threats. Second, C2 blocking finds and cuts the network connections that malware uses to receive orders. Both methods share one assumption, that malicious traffic is identifiable either by what it looks like or by where it goes.
The AI malware CLOSEDQUORUM breaks both assumptions in a practical way. The code itself may match no known signature, because the operator configures each deployed copy differently and the public build ships with placeholder values that change before real use. Meanwhile, the network traffic looks like legitimate API calls to commercial AI services, because it is legitimate API calls to commercial AI services. A firewall rule that blocks DeepSeek or Mistral would break a large amount of normal developer and business work across the organization.
How Do You Detect CLOSEDQUORUM in Your Environment?
The detection that works against the AI malware CLOSEDQUORUM correlates the sequence of behaviors rather than hunting for one indicator. For example, a Windows process that makes rapid successive connections to several AI provider APIs, then reaches Windows credential memory such as LSASS or the Windows Credential Manager, then injects into a second process, then writes a registry Run key for persistence, is a behavior chain that no legitimate application matches. No single link in that chain is malicious. The sequence is.
The published indicators for the AI malware CLOSEDQUORUM confirm the exact file paths and registry locations. Use the table below to tune your rules.
| Indicator | Detail |
|---|---|
| Platform | Windows |
| Firefox credentials | logins.json |
| Chrome and Edge credentials | Login Data database |
| Cryptocurrency wallet | exodus.wallet |
| Persistence | Run key value named WindowsUpdate under the current user’s Run key |
| Staging folder | C:\Windows\Temp\ before transmission |
| Exfiltration | Discord webhook |
The persistence value hides in plain sight under this key, so flag it when any non system process creates it.
Where Does CLOSEDQUORUM Sit in the Digital Warfare AI Classification?
Our AI Augmentation Classification, built from confirmed incidents in our 2026 dataset, sets out three maturity levels of AI assisted attacks. The AI malware CLOSEDQUORUM lands between the second and the third.
- Level One, AI assisted tool generation: a human uses a large language model to write custom scripts or malware code. Our analysis of a vibe coded Active Directory enumeration PowerShell script is a Level One example, because the attacker wrote the prompt, the AI wrote the tool, and a human still ran the attack in real time
- Level Two, AI accelerated decision support: AI helps a human attacker analyze reconnaissance data, compress timelines or rank targets faster than manual review. Members of TeamPCP have said they used AI this way to speed up their lateral movement scripting
- Level Three, autonomous execution: the malware runs a full multi step attack, including self correction, with no human in the loop
CLOSEDQUORUM uses AI for real time tactical decisions during the attack itself, not in the planning phase. The operator sets the menu and deploys the implant, but from that point the AI models drive moment to moment behavior. JADEPUFFER, which we confirmed as the only Level Three case in our 2026 mid year dataset, showed fully autonomous multi step execution with self correction. CLOSEDQUORUM does not reach that bar yet, because it constrains the action menu, the lateral movement handler is missing, and the operator still chooses the first target. It is best read as an early Level Three prototype that shows the architecture of fully autonomous AI malware without achieving it. For the full framework, see our AI Augmentation Classification and JADEPUFFER analysis in the Digital Warfare threat intelligence archive.
How Strong Is the Evidence Behind the AI Malware CLOSEDQUORUM?
We separate confirmed facts from noted observations, so you can judge the risk yourself.
- Confirmed by analysis of the sample: the vote based decision loop, the four models queried, the constrained action menu, the missing lateral movement handler, and the indicators such as the credential file paths, the WindowsUpdate Run key, the temp staging folder and the Discord webhook
- Noted by researchers: the five to fifteen minute retry timing that mimics background applications, and the date derived encryption key that could let the author decode any operator’s stolen data
- Still open: no confirmed victims, placeholder credentials and a dummy reporting address in the public build, and whether a weaponized variant with working lateral movement will appear
One point deserves emphasis. CLOSEDQUORUM is a malware implant, not a software vulnerability, so it carries no CVE or CVSS score. Judge it by the design it proves and the detection gap it opens, not by a severity number.
What Should Security Teams Do About the AI Malware CLOSEDQUORUM Today?
The absence of victims does not make this a future problem. Researchers have documented the design, the code exists, and the operator model is clear. Therefore, teams have a short window to tune detection before a weaponized variant circulates or another actor copies the architecture with working lateral movement. Work through these steps.
- Tune behavioral rules for the AI decision loop. Ask your EDR and SIEM vendors to correlate rapid outbound connections to several AI provider APIs with later credential access, process injection or persistence in the same process context. No single indicator is malicious, but the sequence is
- Update credential store monitoring. Alert immediately when any process that is not a browser or a known credential manager reads logins.json, the Login Data database used by Chrome and Edge, or exodus.wallet
- Flag the specific persistence value. Treat a registry value named WindowsUpdate under the current user’s Run key as suspicious when any non system process creates it, because the name is chosen to survive a casual review
- Review Discord webhook egress. Investigate Discord webhook traffic from processes that are not the Discord desktop client, and treat staging in the Windows Temp folder as a supporting signal
- Do not block AI provider domains at the perimeter. Blocking DeepSeek, Mistral, Gemini or similar services disrupts legitimate work without stopping an attacker who can use a proxy or switch providers. Behavioral correlation is the right answer
Above all, test whether your current controls would catch this behavior chain. Our team runs penetration testing and red team assessments with scenario modules built from confirmed 2026 AI attack techniques, including agentic malware decision loops. In addition, our PTaaS platform keeps that testing continuous, so a new technique like this one does not sit undetected between annual reviews.
Key Takeaways
- The AI malware CLOSEDQUORUM queries DeepSeek, Qwen, Mistral and Gemini, tallies their votes, and runs the winning action, with no operator command after deployment
- Researchers documented it on September 23, 2026, and found no confirmed victims in the public build
- Its traffic looks like normal API calls to commercial AI services, so provider level blocking cannot stop it without breaking legitimate work
- Detection depends on correlating the behavior chain of AI API calls followed by credential access, process injection or persistence
- Our classification places it between Level Two and Level Three, an early prototype of fully autonomous AI malware that has not yet reached the JADEPUFFER threshold
- Tune behavioral detection now, before a variant with working lateral movement appears
Frequently Asked Questions About the AI Malware CLOSEDQUORUM
What is CLOSEDQUORUM?
CLOSEDQUORUM is a Windows malware implant that uses commercial AI models to decide its next move. After an operator deploys it, the AI malware CLOSEDQUORUM queries DeepSeek, Qwen, Mistral and Gemini, tallies their votes, and runs the winning action on its own.
How does CLOSEDQUORUM avoid command and control detection?
Instead of calling an attacker server for orders, it asks public AI models what to do. Because the AI malware CLOSEDQUORUM sends traffic that looks like ordinary API calls to commercial AI services, it does not match the command and control patterns that defenders normally block.
Has CLOSEDQUORUM caused any confirmed damage?
No. Researchers found no confirmed victims of the AI malware CLOSEDQUORUM, and the public build carries placeholder credentials and a dummy reporting address. Its importance is the design it proves, not the harm it has done so far.
Can CLOSEDQUORUM spread across a network?
Not yet. Lateral movement appears on the action menu, but the analyzed build of the AI malware CLOSEDQUORUM has no working handler for it. The operator still picks where to place each customized copy.
Should we block DeepSeek, Mistral or Gemini to stop CLOSEDQUORUM?
No. Blocking AI provider domains breaks legitimate developer work and does not stop the AI malware CLOSEDQUORUM once an attacker can switch providers or use a proxy. Behavioral detection of the attack sequence is the correct response.
How do we detect CLOSEDQUORUM in our environment?
Correlate the behavior chain rather than one indicator. To catch the AI malware CLOSEDQUORUM, alert when a single process makes rapid calls to several AI provider APIs and then reaches credential stores, injects into another process, or writes a registry Run key for persistence.

