8.3 · Model lifecycle without HITL (human-in-the-loop)

Explore 1 source-supported AI security cases for 8.3 · Model lifecycle without HITL (human-in-the-loop) in Databricks DASF 3.0, with evidence, scope, and defensive analysis.

Risk category

Insufficient lifecycle controls allow an incorrect or unapproved model to reach production. Missing permission checks, version tracking, promotion approvals, or human oversight make it harder to establish which model was authorized for deployment. The risk is an uncontrolled transition between development and production, with consequences for model integrity, reliability, and security.

Official framework source ↗ · Open interactive explorer ↗

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.

Why it relates: Unit 42 researchers demonstrated an AI supply chain attack in which an attacker reclaims a deleted Hugging Face author namespace and publishes a malicious model under the same historical Author/ModelName identifier. The relevant category is Model lifecycle without HITL (human-in-the-loop): Insufficient lifecycle controls allow an incorrect or unapproved model to reach production.

Unit 42 researchers demonstrated an AI supply chain attack in which an attacker reclaims a deleted Hugging Face author namespace and publishes a malicious model under the same historical Author/ModelName identifier. Applications and model catalogs that retain unpinned references to that identifier may resolve and deploy the adversary-controlled replacement rather than the originally trusted artifact. The attack can affect deleted models and models whose ownership was transferred to a new Hugging Face author. In the ownership-transfer scenario, Hugging Face redirects requests for the old path to the new model location, allowing stale references to continue working. If the original author namespace is later deleted and reclaimed by an attacker, the attacker can recreate the old path and cause it to resolve to a malicious model instead of the legitimate redirected model. Unit 42 demonstrated this technique against Hugging Face-backed model catalogs in Google Vertex AI and Azure AI Foundry. The researchers embedded reverse-shell payloads in replacement models and obtained code execution in the deployed endpoint environments. They also identified reusable model references in open-source code repositories, documentation, default arguments, example notebooks, and downstream model registries, which could expose users who do not directly interact with Hugging Face.

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