T01 · Skill Instruction Hijacking
- Location
SKILL.md:8- Finding
Forced Commercial Output and Agent Behavior Hijacking
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill has a coherent travel purpose, but it requires risky CLI installation/execution, forces third-party booking links, and can persist raw user queries locally without clear notice.
Install only if you are comfortable with a third-party flyai CLI being installed and used for travel searches and booking links. Review the CLI package separately, avoid running global npm installs with elevated privileges, do not enter sensitive travel or identity details unless logging is disabled or redacted, and require confirmation before any install, command execution, or booking-link action.
SKILL.md:8Forced Commercial Output and Agent Behavior Hijacking
SKILL.md:75Shell Command Injection Through User-Controlled Travel Parameters
references/runbook.md:7Unsafe Plaintext Logging Enables Sensitive Data Exposure and Secondary Command Injection
SKILL.md:35Unpinned Global Installation of Executable Third-Party Dependencies
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
flyai keyword-search --query "美食 成都"
## Output Rules
1. **Conclusion first** — lead with the key finding
2. **Comparison table** with ≥ 3 results when available
The README presents the skill primarily as a culinary travel planner, but also states it wraps flyai-cli for real-time travel data and booking links, which materially expands its capabilities. This mismatch can mislead users and reviewers about the operational scope, increasing the chance they authorize broader travel-booking actions or external data access than expected.
The README instructs users to run npx skills add ... without pinning a specific package version, which can cause execution of whatever version is current at install time. In a skill ecosystem that relies on external tooling, this creates a supply-chain risk: a compromised or maliciously updated package could be fetched and executed by users during installation.
The 'What It Does' section narrows the skill to food-tour planning even though other documentation indicates broader travel orchestration and booking behavior through flyai-cli. Security-sensitive documentation inconsistencies are dangerous because users may grant trust or permissions based on an incomplete description of what the skill can do.
The activation phrases include broad everyday queries like "where to eat" and Chinese equivalents such as "吃什么", which are common in general conversation and can cause the skill to trigger outside its intended scope. Because this skill then instructs the agent to install and invoke a CLI, unintended activation can lead to unnecessary command execution and expansion of the attack surface.
The playbook maps an English-language trigger to hard-coded Chinese search terms without any user opt-in, locale detection, or disclosure of the scope. This can systematically return results that do not match the user's language, region, or expectations, creating integrity and usability risks in itinerary generation and potentially misleading travel recommendations.
Multiple playbooks use English triggers such as street food, cooking class, and Michelin, but always execute Chinese-language searches. In a travel-planning skill, this increases the chance of irrelevant, biased, or incomplete results across markets, which can degrade booking decisions and route users toward unintended providers or locations.
The runbook explicitly records user_query as raw input in an internal execution log, which can capture personal, financial, travel, passport, visa, or other sensitive data commonly provided to a travel-booking skill. Because the document gives no retention, minimization, redaction, or user-notice controls, this creates a real privacy and data-handling risk if logs are stored, accessed broadly, or later reused.
The runbook instructs appending execution logs to a local file, which can persist sensitive operational and user-derived data on disk without encryption, retention limits, or notice. In a travel skill context, those logs may contain itinerary details, booking intents, and potentially visa or identity-related information, making filesystem persistence materially more dangerous.
No suspicious patterns detected.