Back to skill

Security audit

cargo-observability

Security checks for vulnerabilities and agentic risk

Overview

This Cargo observability skill is coherent for creating scheduled alerts, but it should be reviewed because it installs a mutable npm CLI and can create scheduled actions that run agents, tools, or connectors.

Review the dependency policy before installing: prefer a pinned, reviewed @cargo-ai/cli version, use a Cargo token limited to observability permissions where possible, preview alerts before creating them, and be careful with actions because breaches can trigger paid connector, tool, or agent runs on a schedule.

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
SKILL.md:14
Finding

Unpinned npm CLI Dependency Allows Mutable Upstream Code Execution

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger phrases are very broad and overlap with normal conversational requests such as 'notify me if', 'let me know when', and 'set up monitoring'. In an agent-routing context, that can cause the skill to activate unexpectedly on ambiguous prompts, leading to unintended monitoring configuration, writes to observability resources, or scheduled actions being created without the user clearly intending to use this specific skill.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
86% confidence
Finding

The skill explicitly recommends running the CLI via npx @cargo-ai/cli without a pinned version, which can fetch whatever package version is current at execution time. That creates supply-chain and reproducibility risk: a compromised or breaking upstream release could be pulled into a user workflow unexpectedly, especially because this skill is centered on operational automation and alerting.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.