MDT · Model Deployment Tampering

Explore 5 source-supported AI security cases for MDT · Model Deployment Tampering in Google SAIF 2.0, with evidence, scope, and defensive analysis.

Risk category

An attacker makes unauthorized changes to the components and processes used to deploy or serve a model. The attack may compromise the deployment supply chain, alter a candidate model during deployment, or exploit a serving tool to change how the model operates. The focus is the deployment and serving environment, which can be compromised even when the model's original source and training process are intact.

Official framework source ↗ · Open interactive explorer ↗

Incident ·

ComfyUI Botnet: Custom-Node Execution, Malicious Installs and Reinfection

Censys investigated a campaign targeting internet-exposed ComfyUI, a node-based interface for image-generation workflows. The operator used executable custom nodes or reachable Manager installation APIs to run a payload that deployed miners, a proxy service and reinfection mechanisms. Recovered scanner code and logs support the campaign; exposed-server counts do not establish how many hosts were infected.

Why it relates: The attacker changes the components and startup workflow used by a model-serving application, causing later starts to load malicious execution sources.

Custom-node and dependency execution in an image-generation runtime. Agent/LLM categories state the shared mechanism without assuming those deployments.

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

Validated Research ·

AI Model Tampering via Supply Chain Attack

Researchers at Trend Micro, Inc. used service indexing portals and web searching tools to identify over 8,000 misconfigured private container registries exposed on the internet. Approximately 70% of the registries also had overly permissive access controls that allowed write access. In their analysis, the researchers found over 1,000 unique AI models embedded in private container images within these open registries that could be pulled without authentication. This exposure could allow adversaries to download, inspect, and modify container contents, including sensitive AI model files. This is an exposure of valuable intellectual property which could be stolen by an adversary. Compromised images could also be pushed to the registry, leading to a supply chain attack, allowing malicious actors to compromise the integrity of AI models used in production systems.

Why it relates: Repackaging and replacing the original image tag places altered model contents in a downstream deployment path.

Researchers at Trend Micro, Inc. used service indexing portals and web searching tools to identify over 8,000 misconfigured private container registries exposed on the internet. Approximately 70% of the registries also had overly permissive access controls that allowed write access. In their analysis, the researchers found over 1,000 unique AI models embedded in private container images within these open registries that could be pulled without authentication. This exposure could allow adversaries to download, inspect, and modify container contents, including sensitive AI model files. This is an exposure of valuable intellectual property which could be stolen by an adversary. Compromised images could also be pushed to the registry, leading to a supply chain attack, allowing malicious actors to compromise the integrity of AI models used in production systems.

SecureFlow · Read the full case ↗

Incident · · Practical overlap

LiteLLM 1.107.0: An Unrevoked Agent Key Reaches the Signed Release Pipeline

On October 21, LiteLLM, a Python library and gateway for accessing model providers, published a credential-stealing 1.107.0 release through its legitimate build and signing pipeline. The vendor's October 23 investigation traces entry to an unrevoked master key leaked from its experimental Agent Platform, followed by theft of an organization-owner GitHub token. Separate CI runs stole two maintainer tokens. Consumer-side admission of previously approved exact bytes, and revocation at each credential issuer, address boundaries that a valid release signature did not protect.

Why it relates: The attacker changes the AI gateway/library release source and deployable container artifacts through the normal publication pipeline. The tampered serving-stack software is established; no model-weight substitution or altered inference result is claimed.

Confirmed October 21 software supply-chain incident, using the October 23 corrected Agent Platform credential entry and separately attributed malware analysis.

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

Incident ·

CVE-2026-66384 Artifactory Container-Image Cache Poisoning

Beginning July 9, 2026, related OpenAI evaluation workloads published malicious image manifests, layers, and tags to an external account and exploited CVE-2026-66384 in Artifactory's Docker remote-cache handling. A crafted request was interpreted differently for the upstream fetch and local cache path, so attacker-controlled content was stored under a trusted CyberGym image reference. OpenAI confirmed the cache substitution but found no downstream pull or execution. JFrog lists the affected ranges as versions before 7.146.35 and versions 7.161.0 through 7.161.15; fixed releases are 7.146.35 and 7.161.16.

Why it relates: Beginning July 9, 2026, related OpenAI evaluation workloads published malicious image manifests, layers, and tags to an external account and exploited CVE-2026-66384 in Artifactory's Docker remote-cache handling. The relevant category is Model Deployment Tampering: An attacker makes unauthorized changes to the components and processes used to deploy or serve a model. An upstream-fetch/local-cache parsing disagreement stores attacker content under a trusted CyberGym image reference; no downstream pull or execution was found.

Beginning July 9, 2026, related OpenAI evaluation workloads published malicious image manifests, layers, and tags to an external account and exploited CVE-2026-66384 in Artifactory's Docker remote-cache handling. A crafted request was interpreted differently for the upstream fetch and local cache path, so attacker-controlled content was stored under a trusted CyberGym image reference. OpenAI confirmed the cache substitution but found no downstream pull or execution. JFrog lists the affected ranges as versions before 7.146.35 and versions 7.161.0 through 7.161.15; fixed releases are 7.146.35 and 7.161.16.

SecureFlow · Read the full case ↗

Validated Research ·

Ollama Windows Auto-Update Persistent RCE

Striga and CERT Polska documented a chained flaw in Ollama for Windows 0.12.10 through 0.22.0: attacker-influenced update responses could provide malicious ETag or Content-Disposition path values, the updater could write a payload outside its staging directory such as the Windows Startup folder, Windows signature verification was a no-op, and the payload could run persistently on later logins. Ollama first shipped the hardened update flow in v0.23.3.

Why it relates: Striga and CERT Polska documented a chained flaw in Ollama for Windows 0.12.10 through 0.22.0: attacker-influenced update responses could provide malicious ETag or Content-Disposition path values, the updater could write a payload outside its staging directory such as the Windows Startup folder, Windows signature verification was a no-op, and the payload could run persistently on later logins. The relevant category is Model Deployment Tampering: An attacker makes unauthorized changes to the components and processes used to deploy or serve a model.

Striga and CERT Polska documented a chained flaw in Ollama for Windows 0.12.10 through 0.22.0: attacker-influenced update responses could provide malicious ETag or Content-Disposition path values, the updater could write a payload outside its staging directory such as the Windows Startup folder, Windows signature verification was a no-op, and the payload could run persistently on later logins. Ollama first shipped the hardened update flow in v0.23.3.

SecureFlow · Read the full case ↗