Back to skill

Security audit

cargo-diagnostics

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent Cargo diagnostics skill with disclosed Cargo CLI use; the main caution is its unpinned npm CLI install path.

Install only if you trust the Cargo CLI publisher and are comfortable letting the agent inspect Cargo workflow run data and billing metrics. Prefer pinning @cargo-ai/cli to a reviewed version instead of using @latest, and use the least-privileged Cargo token needed; reserve admin tokens for billing attribution only.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
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 (1)

Rp1

Medium
Category
MCP Rug Pull
Confidence
93% confidence
Finding

The skill instructs users to run npx @cargo-ai/cli without pinning an exact version, which allows whatever package version is latest at execution time to be fetched and executed. In a security-sensitive CLI context, this creates a supply-chain risk: a compromised or maliciously updated package could execute arbitrary code on the user's machine under the user's privileges.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.