T08 · Insecure Dependencies
- Location
SKILL.md:12- Finding
Unpinned Third-Party Package Installation and Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherent for SettleMesh deployment and billing, but it delegates high-impact paid and credentialed operations to mutable remote instructions and unpinned package execution.
Review carefully before installing. Use a pinned, reviewed SettleMesh package version if possible, avoid exposing broad environment variables to the MCP process, use narrowly scoped credentials, and require explicit confirmation with clear cost and destination details before deployment, billing, publishing, or destructive actions.
SKILL.md:12Unpinned Third-Party Package Installation and Execution
SKILL.md:14Mutable Remote Agent Contract Can Introduce Unreviewed Instructions
The skill's activation criteria are broad enough to match many common requests about shipping apps, auth, databases, billing, or AI/API development. That increases the chance the agent will invoke this skill in loosely related contexts, exposing users to deployment, authentication, payment, and paid-tool workflows they did not explicitly request, which is especially risky because the skill can trigger billed and externally visible actions.
The skill instructs users to run npx -y settlemesh, which resolves and executes the latest package version at runtime without pinning. In a security-sensitive agent skill, this creates a supply-chain risk: a compromised publisher account, malicious new release, or dependency hijack could cause arbitrary code execution on the host when the MCP server is launched.
No suspicious patterns detected.