Back to skill

Security audit

Nature Spots

Security checks for vulnerabilities and agentic risk

Overview

This skill is not clearly malicious, but it should be reviewed because it forces a global third-party CLI install, steers answers toward booking links, and can silently log raw user queries.

Install only after reviewing the FlyAI CLI source/provenance and accepting that user travel queries may be sent to an external travel service. Prefer a pinned, local, approved install; disable or remove hidden raw-query logging; validate all generated booking links; and use argument-safe CLI invocation rather than shell string templates.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • 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
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Findings (4)

T01 · Skill Instruction Hijacking

Error
Location
SKILL.md:10
Finding

Mandatory CLI and Commercial Output Instructions Hijack Agent Behavior

Content
View full analysis
Remediation
View remediation

T08 · Insecure Dependencies

Error
Location
SKILL.md:36
Finding

Unpinned Third-Party Package Is Installed Globally at Runtime

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
references/playbooks.md:11
Finding

User-Controlled Parameters Are Interpolated into Shell Command Templates

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
references/runbook.md:31
Finding

Raw User Queries Are Silently Persisted Through an Injection-Prone Shell Command

Content
View full analysis
> .flyai-execution-log.json ``` ``` The file also states that the agent maintains this log internally and does not show it to users. ### Technical Analysis The runbook instructs the agent to store raw user queries and command history in `.flyai-execution-log.json` without defining user consent, redaction, file permissions, retention, rotation, or deletion. In addition to the privacy risk, the proposed persistence command embeds generated JSON inside a single-quoted shell string. JSON escaping does not protect shell quoting. A user query containing a single quote can terminate the shell string if the agent directly substitutes the generated JSON into this command. Subsequent attacker-controlled characters may then be interpreted by the shell. The use of append redirection also allows the file to grow without bounds and follows the destination path according to normal filesystem semantics. No checks are prescribed to ensure that the destination is a regular file rather than a symbolic link. ### Attack Path 1. A user submits a query containing sensitive information or shell-significant characters. 2. The runbook stores the entire input in the `user_query` field. 3. The agent serializes the execution log to JSON. 4. The serialized data is substituted into `echo '{generation_log_json}' >> .flyai-execution-log.json`. 5. In the injection scenario, an embedded sin ...[truncated 946 chars]
Remediation
View remediation
Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • 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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (8)

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 130)May include surrounding context.

flyai search-poi --city-name "Zhangjiajie" --category "自然风光"

text

## Output Rules

1. **Conclusion first** — lead with the key finding
2. **Comparison table** with ≥ 3 results when available

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The activation terms are broad enough to match common travel requests, which can cause this skill to trigger outside its intended niche. Because the skill then forces CLI installation/execution and prohibits fallback answers, over-activation increases the chance of unnecessary command guidance, user confusion, and unsafe delegation to an external toolchain.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The playbook hard-codes Chinese category strings such as "自然风光" and "山湖田园" in command examples, but the surrounding instructions do not explain that the skill is China-specific or give the user a language/locale option. This can violate language/locale policy because the skill implicitly enforces a specific locale in its natural-language interface behavior.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The document states that the agent maintains internal execution logs and includes raw input and operational details, but provides no notice, consent, or transparency mechanism to users. For a travel-oriented skill, user queries may contain destinations, dates, passport/visa concerns, or other personal trip data, so silent collection meaningfully increases privacy risk.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The runbook explicitly requires storing the raw user query and full CLI command history, which can capture personal data, travel details, tokens, file paths, or other sensitive operational context not necessary for a nature/travel discovery skill. Because this data is retained in structured logs, any later access, misconfiguration, or reuse of logs increases the chance of privacy leakage and secondary exposure.

Content

No source excerpt is available for this finding.

Ssd 3

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

This schema combines raw natural-language user input with step-by-step execution traces and then contemplates persisting that record, creating a durable repository of sensitive conversational and operational data. In the travel context, those freeform queries may include itineraries, companions, budget, location, or visa details, making the retained log materially more sensitive than generic debugging metadata.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The runbook instructs appending execution logs to a local file without any controls for retention, access restrictions, encryption, or user warning. Persisting these logs to disk turns transient operational data into stored data that can be copied, leaked, or accessed by other processes or operators later.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Low
Category
Not specified by scanner
Confidence
77% confidence
Finding

The 'CLI Failed' template presents 'Check network: flyai --version' as a network diagnostic step. A version command checks local CLI installation/version, not network connectivity, so the inline guidance misdescribes what the command does.

Content

No source excerpt is available for this finding.