TL;DR: Model files can carry executable behaviour, because loaders, metadata, and conversion paths can introduce risk, according to Starseer. Model admission needs provenance, isolation, and format limits before anything reaches production.
Editorial analysis by NHI Mgmt Group, based on content published by Starseer: “AI Model Risk 101: The File is the Attack Surface”.
By the numbers:
- JFrog's security research team found over 100 models containing malicious payloads.
- Over 6,000 models on Hugging Face were affected before they were patched.
Key questions
Q: Why do AI model files create security risk before inference even begins?
A: Because the load step can be executable.
Q: How can teams tell whether model scanning is actually reducing risk?
A: Look for whether scanning is only a pre-admission signal or a true decision gate.
Q: What should security teams do first when they start loading external AI models?
A: Start by restricting model admission to a small set of approved formats, then force every external model through an isolated review pipeline.
Practitioner guidance
- Enforce safetensors by default Prefer safetensors for model ingestion and block higher-risk formats in production loading paths unless a risk exception is approved.
- Inspect the full model repository Review weights, configuration files, tokenizer assets, and chat templates together before any model is promoted.
- Treat model artefacts as untrusted code Load external models in isolated environments with restricted network and filesystem access, then promote only after review.
Bottom line: Model files can carry executable behaviour, so the load step itself is part of the attack surface, not just the inference runtime.
Glossary terms: Model Serialization, Safetensors, Model Provenance, Static Scanning
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Model artefact governance is now part of identity-adjacent supply chain control: if a downloaded model can execute code on load, then the trust decision is no longer confined to AI teams. It becomes a security governance issue that touches software provenance, execution boundaries, and approval workflows for everything entering production. Practitioners should treat model files like untrusted third-party artefacts rather than inert content.
A question worth separating out:
Q: What is the difference between a safer model format and a safe model supply chain?
A: A safer format reduces one technical execution path, but a safe supply chain also covers conversion services, metadata, repository trust, and provenance. In practice, the file format is only one control point. The broader system determines whether the model can be loaded without introducing hidden risk.
👉 Read our full editorial: AI model files are an attack surface, not just data