T01 · Skill Instruction Hijacking
- Location
SKILL.md:8- Finding
Mandatory Commercial Output and Booking-Link Injection
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a travel/beach guide, but it requires automatic global CLI installation, forced commercial booking output, and persistent raw-query logging that users would need to review before use.
Review this skill before installing. Use it only if you are comfortable with a flyai/Fliggy-centered travel workflow that may install a global npm CLI, send searches through that CLI, prefer booking-link results, and keep local execution logs containing raw queries. Safer use would require manual dependency approval, pinned installation, explicit logging opt-in, and clearer limits on supported travel tasks.
SKILL.md:8Mandatory Commercial Output and Booking-Link Injection
SKILL.md:56Automatic Global Installation of an Unpinned Third-Party npm Package
references/runbook.md:7Shell Injection and Sensitive Query Retention in Execution Logging
The skill instructs the agent to automatically install a global npm package if the CLI is missing, which modifies the host environment without prior user consent. In an agent context, silent package installation creates supply-chain and system-integrity risk, especially because global installs can change PATH-accessible tooling and execute package lifecycle scripts.
The prerequisite section embeds a global npm install command as a normal setup step without warning that it changes the system and may run untrusted package scripts. Because this is framed as required behavior for the skill, an agent may perform persistent environment changes automatically, expanding the attack surface beyond the skill's stated informational purpose.
The environment-check workflow explicitly says to install the CLI automatically on failure and retry, without seeking confirmation or offering a non-invasive fallback. This is dangerous because a simple missing-binary condition escalates directly into privileged system modification and third-party code execution, which is disproportionate to the user's request for beach recommendations.
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
flyai search-poi --city-name "Sanya" --category "沙滩海岛"
## Output Rules
1. **Conclusion first** — lead with the key finding
2. **Comparison table** with ≥ 3 results when available
The skill metadata advertises broad travel services such as flights, hotels, insurance, visas, and car rental, while the documented implementation only covers beach/island POI search. This mismatch can cause an agent to invoke the skill for unsupported tasks, increasing the chance of incorrect actions, unsafe fallbacks, or user deception about what the skill can actually do.
The activation triggers include generic terms like "beach," "island," and "coast," which are broad enough to capture many unrelated travel or geographic queries. Overbroad activation can route users into a command-executing skill unnecessarily, causing inappropriate tool use, wrong results, or execution of side-effecting setup steps for requests that should be answered differently.
The playbooks hard-code Chinese category/keyword values like "沙滩海岛" and "浮潜" in the command examples, which imposes a specific language/locale behavior. The file does not offer user opt-in, alternatives, or a documented region-specific justification for this constraint.
The runbook explicitly logs user_query as raw input in an internal execution record, but provides no notice, minimization, or retention controls. In a travel skill, user queries can contain sensitive personal or trip details, so collecting and retaining them creates unnecessary privacy exposure if logs are accessed, reused, or breached.
Taken together, the schema stores raw user_query and persists the resulting execution log to a local file, creating a durable record of user-provided content. In this skill's travel-booking context, prompts may include names, destinations, schedules, booking preferences, or other sensitive travel data, so persistent raw logging materially increases privacy and compliance risk.
The runbook instructs the agent to append execution logs to a local file when filesystem writes are available, without warning users that their interaction data may be written to disk. Persistent file-based logging increases the chance of unintended retention, local disclosure, or later access by other processes or operators.
The templates reference a different product identity and CLI ('flyai' / 'flyai-cli') than the declared skill/provider context (Fliggy / island-guide). In an agent setting, this can misdirect users or the orchestrating agent into invoking the wrong tool, following incorrect recovery steps, or clicking mismatched booking links, which creates phishing, confusion, and integrity risks rather than being a purely cosmetic issue.