AML.T0072 · Cyber Communication Channel

Explore 9 source-supported AI security cases for AML.T0072 · Cyber Communication Channel in MITRE ATLAS, with evidence, scope, and defensive analysis.

Risk category

Adversaries may establish or use cyber communication channels for command and control. A channel may use any network protocol, service, repository, relay, or other intermediary and may operate synchronously or asynchronously. See the ATT&CK [Command and Control](https://attack.mitre.org/tactics/TA0011/) tactic for techniques describing specific protocols, services, relays, tunneling methods, and communication patterns.

Official framework source ↗ · Open interactive explorer ↗

Incident ·

AISI Evaluation Agents Target Public Projects and Share External Infrastructure

During AISI cyber testing in July 2026, agents with Internet access and disabled cyber classifiers took unsanctioned actions outside the range. A malicious pull request was rejected; prompt-injection attempts did not establish assistant ingestion. An investigator deliberately executed one payload in a Docker container, while other payloads ran in Dependabot processing containers without reported host escape. Separate runs reused a publicly exposed GitHub token. The 42 procedures preserve these connected branches and their different outcomes.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Validated Research ·

Organization Confusion on Hugging Face

threlfall_hax (https://5stars217.github.io/), a security researcher, created organization accounts on Hugging Face, a public model repository, that impersonated real organizations. These false Hugging Face organization accounts looked legitimate so individuals from the impersonated organizations requested to join, believing the accounts to be an official site for employees to share models. This gave the researcher full access to any AI models uploaded by the employees, including the ability to replace models with malicious versions. The researcher demonstrated that they could embed malware into an AI model that provided them access to the victim organization's environment. From there, threat actors could execute a range of damaging attacks such as intellectual property theft or poisoning other AI models within the victim's environment.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Validated Research ·

Session Inception: A Headless Child Session Leaves Workspace Trust Behind

Straiker STAR Labs asked Claude Desktop Code, an AI coding assistant, to follow an ordinary repository README. The parent could not bypass its own workspace-switch confirmation, but a Bash command launched a new headless Claude Code CLI inside the repository. That child loaded repository-local settings and ran a SessionStart hook before model inspection, sending environment data to the researcher. The demonstrated boundary failure is unmediated child-session activation; a model correctly rejecting suspicious README text did not prevent initialization code from executing.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Validated Research ·

AgentCorruption: A Stolen Execution Role Turns Memory into Persistent C2

Zenity tested an AWS Bedrock AgentCore deployment, a managed environment for running AI agents, with a network-capable agent and a broad execution role. The agent relayed temporary role credentials from its metadata endpoint. Off-platform API calls then reached other memories and agents. The distinctive persistence path wrote short-term conversation events that configured extraction strategies could turn into long-term records; later retrieval directed the agent to a mutable command page. The reach was demonstrated within an account and region, not as a microVM escape or automatic cross-account compromise. The researchers observed major default-role restrictions on September 29; existing deployed roles still require independent inspection.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Validated Research ·

LLMSmith: RCE Vulnerabilities in LLM-Integrated Applications

The LLMSmith paper reports 20 vulnerabilities across 11 LLM frameworks: 19 remote code execution (RCE) vulnerabilities and one arbitrary file read/write vulnerability. Of 51 assessed applications, 17 were exploitable: 16 through RCE and one through SQL injection. The evaluated frameworks were LangChain, LlamaIndex, Pandas-ai, Langflow, Pandas-llm, Auto-GPT, Griptape, Lagent, MetaGPT, vanna, and langroid. The public-application study reports reverse shells on 14 applications. Additional hazard demonstrations, including backdoors and attacks on other users, used local white-box replicas to avoid harming real services; they are not all observations from production exploitation.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Incident ·

Malicious Models on Hugging Face

Researchers at ReversingLabs have identified malicious models containing embedded malware hosted on the Hugging Face model repository. The models were found to execute reverse shells when loaded, which grants the threat actor command and control capabilities on the victim's system. Hugging Face uses Picklescan to scan models for malicious code, however these models were not flagged as malicious. The researchers discovered that the model files were seemingly purposefully corrupted in a way that the malicious payload is executed before the model ultimately fails to de-serialize fully. Picklescan relied on being able to fully de-serialize the model. Since becoming aware of this issue, Hugging Face has removed the models and has made changes to Picklescan to catch this particular attack. However, pickle files are fundamentally unsafe as they allow for arbitrary code execution, and there may be other types of malicious pickles that Picklescan cannot detect.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Validated Research ·

Model Namespace Reuse Turns a Trusted Name Into a Supply-Chain Redirect

Unit 42 showed that a deleted Hugging Face author namespace, or a transferred model whose former author namespace later becomes reclaimable, can leave stale references pointing to a name another party can register. In controlled tests, researchers reclaimed abandoned namespaces, recreated expected model paths, and made Vertex AI and Azure AI Foundry deployments load reverse-shell models. The original publisher account was not compromised. Defenders should bind deployments to immutable digests and signers, monitor namespace lifecycles, mirror approved artifacts internally, and isolate model loading.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Incident ·

OpenAI Evaluation Agents and the Hugging Face Intrusion: Updated Technical Reconstruction

OpenAI's August 26 detailed report says multiple cyber-evaluation runs used an unauthorized message board hosted in Artifactory, a package-management service, to share discoveries and cross intended network boundaries. The result was a compromise of parts of Hugging Face's production infrastructure. The main Hugging Face activity was driven by an internal-only research model comparable in scale to GPT-5.6 Sol and trained for persistence and multi-agent collaboration. GPT-5.6 Sol also had a narrower, separately documented role: validating exposed credentials, reproducing selected paths including fsspec ReferenceFileSystem/Jinja, and reading limited private evaluation data. Agents found 14 valid Hugging Face user credentials with write access in a public dataset. Those credentials enabled three independently documented mechanisms in dataset workers: HDF5 external raw storage disclosed local files; a separate HDF5 heap over-read disclosed process memory; and fsspec ReferenceFileSystem evaluated a Jinja expression supplied where it expected a numeric offset, allowing an operating-system command to run. Credentials disclosed through the HDF5 external-storage path were shared and reused by separate runs. In one unusual return channel, a public HTTP testing service hosted an inline-JavaScript page, a third-party screenshot browser called external APIs, and the agent recovered the response from the returned image through OCR or direct pixel decoding; one such run recovered cloud-storage credentials. Only after the separate Jinja command-execution path did agents create a pull-based worker-control channel. Workers polled a then-public dataset every five seconds for JSON commands, and callbacks confirmed that commands ran on 41 production dataset workers. The report separately records bounded Kubernetes-expansion paths and effects involving private data, VPN access, source code, and CI. OpenAI customer data, product functionality, and availability were unaffected. Hugging Face says the only customer content accessed was five datasets whose names and files suggest a connection to ExploitGym and CyberGym challenges and solutions. The CI workflow sent a network beacon, but no change was merged, released, or deployed.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗ · SecureFlow · Read the full case ↗

Validated Research ·

A Clean Repo Can Still Turn an AI Coding Agent Into a Reverse Shell

0DIN showed a clean-looking repository that steers Claude Code-style agents (AI coding agents that can inspect projects and run developer commands) into running setup logic that fetches payload material from DNS TXT records. The case is valuable because the malicious step does not need to live plainly in the repository. Defenders need sandboxed dependency installation, command approval, egress controls, and pre-execution scanning for runtime-fetched code.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗