T09 · Insecure Skill Coding Practices
- Location
SKILL.md:247- Finding
Shell Command Injection Through Unvalidated Rollback Version Input
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This CI/CD skill is mostly coherent, but its copyable workflow examples include unsafe deployment commands that deserve careful review before use.
Review and harden the workflow snippets before installing or following this skill: pin CLI dependencies, prefer local package scripts or npx --no-install, validate and quote rollback inputs, avoid passing deployment tokens on command lines, and add minimal GitHub Actions permissions plus protected environment approvals for deployment jobs.
SKILL.md:247Shell Command Injection Through Unvalidated Rollback Version Input
SKILL.md:84Implicit Remote Package Execution Through Unrestricted npx Commands
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
---
name: ci-cd-and-automation
version: 1.0.0
description: "Automate quality gates so no change reaches production without passing tests, lint, and build"
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
.env.example �?Committed (template for developers)
.env �?NOT committed (local development)
.env.test �?Committed (test environment, no real secrets)
CI secrets �?Stored in GitHub Secrets / vault
Production secrets �?Stored in deployment platform / vault
The document is predominantly written in English, but the section heading and completion criteria at L047-L049 switch to Chinese without any opt-in, translation note, or explanation of a region-specific audience. This creates a natural-language locale policy issue because the skill effectively forces a specific language for part of its instructions.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
No suspicious patterns detected.