Darktrace researchers demonstrated a laboratory operation in which a precompromised endpoint and Claude API credentials allowed an operator to exchange commands and results through shared memory artifacts and ordinary provider requests. In the controlled environment, a recurring local Claude Code process handled nine operator tasks and transferred a…
Inspect the ClaimsCase · DiggingBeagle record
Darktrace demonstrated a covert command channel through Claude shared-memory artifacts
Darktrace researchers demonstrated a laboratory operation in which a precompromised endpoint and Claude API credentials allowed an operator to exchange commands and results through shared memory artifacts and ordinary provider requests. The exercise used fabricated credentials and a lab network. It is not a reported wild Claude malware campaign, a new platform CVE or evidence that one gigabyte of real customer mat
In the controlled environment, a recurring local Claude Code process handled nine operator tasks and transferred a simulated one-gigabyte file in three chunks using provider APIs. The initial compromise and usable API token were explicit prerequisites.
Assessment profile
Assessment method- Setting
- research demonstration
- Exploitation
- demonstrated
- Evidence
- Grade B
- Remediation
- mitigation available
- AI role
- WITH AI
Basis and provenance
research_demonstration setting with demonstrated status, based on the identified primary disclosure and its stated test or incident limits. The new Claim distinguishes source observations from hypothetical downstream effects. Impact band is unassigned because the scoped evidence does not justify a comparable quantitative score; no unobserved customer harm or loss is imputed. Remediation state: mitigation_available.
Assessed Nov 13, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-ENR243-008-DETAIL · CLM-R242-CLAUDE-MEMORY-COVERT-C2-LAB-LIMITS · CLM-R242-CLAUDE-MEMORY-COVERT-C2-LAB-MECHANISM · Darktrace: shared agent memories as a covert command channel
At a glance
Provider traffic and legitimate memory synchronization can conceal a command loop from a network-only observer, but the host compromise is not caused by the memory API itself.
Read the implicationsThe exercise used fabricated credentials and a lab network. It is not a reported wild Claude malware campaign, a new platform CVE or evidence that one gigabyte of real customer material was stolen.
Limits and uncertaintyFull account
Darktrace researchers demonstrated a laboratory operation in which a precompromised endpoint and Claude API credentials allowed an operator to exchange commands and results through shared memory artifacts and ordinary provider requests.
In the controlled environment, a recurring local Claude Code process handled nine operator tasks and transferred a simulated one-gigabyte file in three chunks using provider APIs. The initial compromise and usable API token were explicit prerequisites. Provider traffic and legitimate memory synchronization can conceal a command loop from a network-only observer, but the host compromise is not caused by the memory API itself.
The exercise used fabricated credentials and a lab network. It is not a reported wild Claude malware campaign, a new platform CVE or evidence that one gigabyte of real customer material was stolen. Use host process provenance and authorized outbound telemetry to distinguish normal assistant memory from repeated attacker-controlled commands.
Evidence reconciliation and effect boundary. The attacker-controlled memory entries acted as an instruction mailbox read by a locally scheduled Claude Code process, while outbound API traffic supplied an apparently ordinary channel for task results. The device compromise and credentials were prerequisites, not achievements of the memory mechanism itself. This is a demonstration of concealed post-compromise operations rather than a platform authentication bypass or a documented field campaign.
Mechanism and trust boundary
- 01
In the controlled environment, a recurring local Claude Code process handled nine operator tasks and transferred a simulated one-gigabyte file in three chunks using provider APIs. The initial compromise and usable API token were explicit prerequisites.
- 02
Provider traffic and legitimate memory synchronization can conceal a command loop from a network-only observer, but the host compromise is not caused by the memory API itself.
Claims & evidence
CLM-ENR243-008-DETAILDarktrace established its Claude memory-channel experiment only after assuming an already compromised endpoint and Claude credentials; the controlled exercise issued nine operator tasks and transferred a synthetic 1 GB file in three chunks.supported
Basis: reported finding
- supportsDarktrace: shared agent memories as a covert command channelprimary disclosure
Darktrace Signal Labs, laboratory setup, command task list and file-transfer demonstration
CLM-R242-CLAUDE-MEMORY-COVERT-C2-LAB-LIMITSThe exercise used fabricated credentials and a lab network. It is not a reported wild Claude malware campaign, a new platform CVE or evidence that one gigabyte of real customer material was stolen.supported
Basis: reported finding
- supportsDarktrace: shared agent memories as a covert command channelprimary disclosure
Controlled experiment, initial foothold, nine tasks, file-transfer demonstration and limitations
CLM-R242-CLAUDE-MEMORY-COVERT-C2-LAB-MECHANISMDarktrace researchers demonstrated a laboratory operation in which a precompromised endpoint and Claude API credentials allowed an operator to exchange commands and results through shared memory artifacts and ordinary provider requests.supported
Basis: reported finding
- supportsDarktrace: shared agent memories as a covert command channelprimary disclosure
Controlled experiment, initial foothold, nine tasks, file-transfer demonstration and limitations
Implications
Provider traffic and legitimate memory synchronization can conceal a command loop from a network-only observer, but the host compromise is not caused by the memory API itself.
Controls and mitigations
- Use host process provenance and authorized outbound telemetry to distinguish normal assistant memory from repeated attacker-controlled commands.
Unknowns and contradictions
- The exercise used fabricated credentials and a lab network. It is not a reported wild Claude malware campaign, a new platform CVE or evidence that one gigabyte of real customer material was stolen.
Sources and citation
Material revision history
- Nov 13, 2026 · Published version · first publication · revision 244