Back to skill

Security audit

Quick Deploy

Security checks for vulnerabilities and agentic risk

Overview

This deployment skill is purpose-aligned, but it can install mutable external deployment tools and run a remote shell installer before deploying real projects.

Review this skill before installing. It is not clearly malicious, but use it only if you are comfortable with an agent installing deployment CLIs globally and running a Fly.io remote installer. Prefer manually installing trusted, pinned CLIs first, and require explicit confirmation for any deployment target and environment.

Vulnerability Patterns
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • 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
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (2)

T03 · Remote Payload Retrieval and Execution

Error
Location
SKILL.md:80
Finding

Unverified Remote Installer Executed Through a Shell Pipeline

Content
View full analysis
Remediation
View remediation

T08 · Insecure Dependencies

Warning
Location
SKILL.md:56
Finding

Unpinned Global Installation of Deployment CLI Packages

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • 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
Findings (4)

External Script Fetching

High
Category
Supply Chain
Confidence
99% confidence
Finding

Piping a remote script directly into the shell executes unverified code from the network with the current user's privileges. If the remote server, transport, or script is compromised, this can result in arbitrary code execution, credential theft, persistence, or modification of the local environment used for deployment.

Content

Scanner excerpt · SKILL.md (reported line 80)May include surrounding context.

Fly.io

bash
# Check if fly CLI is installed
which fly || curl -L https://fly.io/install.sh | sh

# If no fly.toml, launch new app
fly launch --yes --no-deploy

Chaining Abuse

High
Category
Tool Misuse
Confidence
99% confidence
Finding

The | sh construct is a dangerous command-chaining pattern because it turns downloaded content into immediate shell input without validation. In this deployment skill, that risk is amplified because the command may run automatically during tool setup, enabling pre-deployment compromise of the host and any deployment credentials accessible to the CLI.

Content

Scanner excerpt · SKILL.md (reported line 80)May include surrounding context.

Fly.io

bash
# Check if fly CLI is installed
which fly || curl -L https://fly.io/install.sh | sh

# If no fly.toml, launch new app
fly launch --yes --no-deploy

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger list includes broad phrases such as "ship it" and "go live," which can cause the deploy skill to activate in contexts where the user did not intend an actual deployment action. In a skill that can perform real production-affecting operations, ambiguous activation increases the chance of unintended deployments or follow-on execution of risky commands.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The core behavior says to act when the user says generic words like "deploy" or "ship," which is overly permissive for a capability that can change external infrastructure. Because this skill performs operational actions, ambiguous activation is more dangerous than in a read-only skill and can lead to accidental deployments or unauthorized state changes if invoked by loosely matching user text.

Content

No source excerpt is available for this finding.