Back to skill

Security audit

MLOps Validation CN

Security checks for vulnerabilities and agentic risk

Overview

This skill provides disclosed MLOps validation templates, with ordinary but real supply-chain risk from third-party pre-commit hooks.

Before installing, review the pre-commit configuration and consider pinning hook revisions and additional dependencies to reviewed immutable versions. Install it only in repositories where automatic linting, formatting, type checking, and security scans on commit are desired.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
Location
references/pre-commit-config.yaml:4
Finding

Pre-commit Hooks and Additional Dependencies Are Not Immutably Pinned

Content
View full analysis
Remediation
View remediation
``` 3. Where the package installation mechanism supports it, require verified package hashes and use a controlled dependency lock file or constraints file. 4. Configure package installation to use a trusted, controlled package index rather than arbitrary or unintended indexes. 5. Review automated dependency updates before merging them. Ensure updates modify pinned SHAs or exact package versions through auditable pull requests. 6. Run pre-commit hooks in an isolated CI environment with least-privilege credentials, restricted filesystem access, and limited outbound network access. 7. Avoid exposing production secrets or broadly scoped repository tokens to jobs that install and execute third-party hooks. 8. Periodically verify pinned commits against upstream release provenance and security advisories. ]]>
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The manifest-style header names the skill mlops-validation-cn, which implies a specific country or locale constraint. The file does not explain what cn means, offer a language/locale choice, or justify a region-specific scope, which can violate the policy against forcing a locale without opt-in.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
78% confidence
Finding

The package name includes the suffix "-cn", which suggests a China-specific language or locale constraint. In this manifest there is no accompanying documentation that offers user opt-in or explains why a locale-specific restriction is required, which may conflict with language/locale policy expectations.

Content

No source excerpt is available for this finding.