T01 · Skill Instruction Hijacking
- Location
SKILL.md:9- Finding
Mandatory Commercial CLI and Output Instruction Hijacking
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This travel skill has a coherent booking purpose, but it asks agents to install and run an unpinned global third-party CLI and to persist raw user travel queries in a hidden plaintext log.
Review before installing. This skill should only be used if you are comfortable installing and running a third-party travel CLI, sending travel-search details to that service, seeing booking-link-centered results, and potentially leaving raw request logs in the workspace. Prefer requiring explicit approval before any npm install or CLI call, and disable or redact the execution log.
SKILL.md:9Mandatory Commercial CLI and Output Instruction Hijacking
SKILL.md:119Unpinned Global Installation of a Third-Party npm Package
references/runbook.md:7Unredacted User Queries Persisted in a Plaintext Execution Log
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
flyai search-flight --origin "Guangzhou" --destination "Bangkok" --dep-date 2026-11-01 --sort-type 3
## Output Rules
1. **Conclusion first** — lead with the key finding
2. **Comparison table** with ≥ 3 results when available
The skill requires all travel answers to come from the external flyai CLI, which necessarily sends user travel queries and possibly itinerary details to a third-party service, yet the skill description provides no privacy or external-execution warning. This can expose sensitive travel plans, locations, dates, and booking preferences without clear disclosure or consent.
The skill explicitly instructs the agent to install @fly-ai/flyai-cli globally if it is missing, but the skill metadata/description does not warn users that it may modify their system. Automatic package installation is security-relevant because it executes third-party code and changes the host environment without prior informed consent.
The runbook explicitly records user_query as raw input in an internal execution log, which can capture sensitive travel details, personal identifiers, payment-related text, passport/visa data, or other confidential information. Because the log is not shown to users and no notice, minimization, masking, or retention controls are described, this creates a real privacy and data-handling risk if logs are accessed, retained too long, or reused improperly.
The runbook instructs the agent to append execution logs to .flyai-execution-log.json, meaning request data may be persisted to disk beyond the immediate session. In a travel/booking skill context, those logs may contain itinerary requests, identity details, or other sensitive booking-related information, and persisting them without disclosure or safeguards increases exposure to unauthorized access, leakage, and over-retention.
No suspicious patterns detected.