Back to skill

Security audit

cargo-flight

Security checks for vulnerabilities and agentic risk

Overview

The skill is a flight-search helper, but it asks agents to install and sometimes sudo-install an unpinned third-party CLI, runs user-derived shell commands, stores raw user queries, and overstates cargo-booking capabilities.

Install only in a sandbox or managed environment where flyai-cli is preinstalled, pinned, and reviewed. Do not let this skill run sudo or global npm installs, avoid entering sensitive shipment or identity details, and treat its results as passenger-flight planning links rather than confirmed cargo-booking capability.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Findings (5)

T01 · Skill Instruction Hijacking

Warning
Location
SKILL.md:9
Finding

Mandatory Commercial Output and Response-Policy Hijacking

Content
View full analysis
Remediation
View remediation

T08 · Insecure Dependencies

Error
Location
SKILL.md:72
Finding

Automatic Global Installation of an Unpinned Third-Party Package

Content
View full analysis
Remediation
View remediation

T05 · Unauthorized Access and Privilege Escalation

Error
Location
references/fallbacks.md:5
Finding

Privilege Escalation Through Suggested Root-Level npm Installation

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
references/fallbacks.md:17
Finding

Shell Command Injection Through Interpolated Travel Parameters

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
references/runbook.md:5
Finding

Raw User-Query Persistence and Shell Injection in Log Writing

Content
View full analysis
> .flyai-execution-log.json ``` ``` ### Technical Analysis The runbook records complete raw user queries, collected parameters, executed commands, and fallback commands in a persistent file. No consent, redaction policy, retention limit, file-permission requirement, or storage location control is specified. Travel requests can contain personal itineraries or other sensitive information, so indiscriminate persistence creates a confidentiality risk. The persistence command introduces a separate command-injection risk. JSON strings do not normally escape apostrophes. If `{generation_log_json}` ...[truncated 1575 chars]
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • System Prompt LeakageDirect Leakage, Indirect Extraction, Tool-Based Exfiltration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
Findings (10)

Direct Prompt Extraction

High
Category
System Prompt Leakage
Confidence
85% confidence
Finding

Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.

Content

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

flyai search-flight --origin "Guangzhou" --destination "Shanghai" --dep-date 2026-05-01 --sort-type 3

text

## Output Rules

1. **Conclusion first** — lead with best cargo-compatible option
2. **Cargo note** — remind user that actual air cargo booking requires contacting the airline's cargo department

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The manifest overstates end-user capabilities by claiming booking support for air cargo and related travel services, while the body of the skill only documents search commands and explicitly disclaims actual cargo booking. In an agent setting, exaggerated capability claims are dangerous because orchestration logic or users may rely on the skill to complete transactions it cannot perform, causing trust failures, bad decisions, or improper handling of logistics requests.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill advertises air cargo booking and freight shipping, but the documented implementation only runs flyai search-flight against scheduled passenger flights and later admits that actual cargo booking requires contacting the airline cargo department. This mismatch can mislead users and downstream agents into treating route-search results as a booking capability, creating deceptive automation behavior and potentially unsafe operational decisions.

Content

No source excerpt is available for this finding.

Sudo/Root Execution

Medium
Category
Privilege Escalation
Confidence
70% confidence
Finding

Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Content

Scanner excerpt · references/fallbacks.md (reported line 10)May include surrounding context.

bash
npm i -g @fly-ai/flyai-cli
flyai --version
# Fails → sudo npm i -g @fly-ai/flyai-cli
# Still fails → STOP. Do NOT answer with training data.
# Tell user: "Please run npm i -g @fly-ai/flyai-cli manually."

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The trigger phrases for the cargo route playbook are broad enough to match common user language about shipping or air cargo, which can cause the skill to activate when the user did not intend to invoke this specific workflow. In an agent setting, unintended activation can lead to incorrect command execution, inappropriate booking/search actions, or leakage of user travel/shipping intent into the wrong tool flow.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

Phrases like 'direct cargo flight' and related shipping terms remain generic enough that ordinary conversation about logistics preferences could activate the direct-route playbook without clear intent to search or book. Because the playbook maps directly to a CLI command, ambiguous triggering increases the risk of unintended external actions and misleading results being presented as if they were explicitly requested.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The runbook explicitly logs user_query as raw input, which can capture personal data, credentials, shipment details, passport or visa information, and other sensitive travel data without any disclosure or minimization. In a travel and cargo-booking skill, users are especially likely to provide high-sensitivity natural-language content, making undisclosed retention a real privacy and compliance risk.

Content

No source excerpt is available for this finding.

Ssd 3

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The file combines two risky behaviors: storing raw user_query content and appending the full execution log to a local file via echo '{generation_log_json}' >> .flyai-execution-log.json. This creates durable retention of sensitive free-form travel data that may include names, contact details, addresses, booking identifiers, visa/passport details, or payment-adjacent information, increasing the chance of later leakage, unauthorized access, or accidental inclusion in backups and support artifacts.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The instruction to never ask for cargo weight or dimensions shows the workflow omits essential shipment attributes required for real cargo and oversized-luggage handling. In a cargo-booking context, this can cause users to receive unusable or dangerously incomplete recommendations, because routing, acceptance, pricing, and feasibility all depend on those constraints.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The template explicitly tells users that results are passenger flights and that actual air cargo booking requires contacting an airline cargo department or freight forwarder. This materially conflicts with the skill’s advertised capability to book air cargo and oversized luggage transport, creating a deceptive capability mismatch that can mislead users into relying on the tool for logistics planning or commercial commitments it cannot actually fulfill.

Content

No source excerpt is available for this finding.