Case · 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

Scope

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.

At a glance

Mechanism and trust boundary

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

  2. 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

Link to claim
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

Link to claim
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

Link to claim

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

  1. Nov 13, 2026 · Published version · first publication · revision 244