T01 · Skill Instruction Hijacking
- Location
SKILL.md:10- Finding
Provider-Controlled Instruction and Output Hijacking
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This travel-booking skill is not clearly malicious, but it requires broad unpinned CLI execution, provider-only booking output, and raw local logging that users should review before installing.
Install only if you are comfortable with a third-party travel CLI receiving your travel queries and with the agent installing global npm tooling. Prefer a pinned, reviewed CLI version, disable or delete .flyai-execution-log.json logging, and avoid entering sensitive itinerary, identity, payment, or account details until privacy and retention behavior is clarified.
SKILL.md:10Provider-Controlled Instruction and Output Hijacking
SKILL.md:67Shell Command Injection Through User-Derived Query Interpolation
references/runbook.md:7Raw User Data Persistence and Shell Injection in Execution Logging
SKILL.md:41Unpinned Global Installation and Execution of 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 manifest frames this as an airport transfer booking skill, but the README says it wraps flyai-cli to provide 'real-time travel data with booking links,' which is a broader travel capability. This materially exceeds the narrow airport-pickup purpose described elsewhere and suggests behavior beyond just transfer booking.
The README promotes booking services and generating booking links via external travel tooling without warning that user itinerary details, locations, and possibly personal travel metadata may be transmitted to third-party services. In a travel-booking context, that omission matters because users may disclose sensitive trip information without informed consent or understanding of where their data goes.
The README instructs users to execute npx skills ... without pinning a specific package version, which can cause retrieval and execution of whatever version is current at install time. That creates a supply-chain risk because a compromised or unexpected upstream release could be pulled and run by users or agents without review.
The skill asserts that all user-facing data must come from CLI output, yet later embeds standalone travel advice and price ranges for 'output enrichment.' That contradiction weakens provenance guarantees and can cause the agent to mix unverified prompt content with tool-derived results, creating a prompt-level data integrity issue and making policy bypass or hallucinated advice more likely.
The activation conditions include generic phrases like "pickup" and "drop off," which are common in everyday speech and not specific to airport-transfer bookings. This can cause unintended skill activation for unrelated requests such as picking up items or dropping someone off outside an airport context.
The runbook explicitly logs user_query as raw input and records full CLI command history, then states the log may be appended to a local file. This creates a real privacy and retention risk because travel-related requests can contain personal, financial, or itinerary data that may be stored without minimization, consent, redaction, or access controls.
The schema combines natural-language user_query, step-by-step operational metadata, and optional filesystem persistence via echo ... >> .flyai-execution-log.json. In a travel-booking context, this is especially sensitive because user queries may include names, flight details, hotels, visa info, and other personal trip data, increasing the chance of local data leakage, over-retention, or secondary exposure.
The manifest frames this as an airport-pickup booking skill, while the 'Domain Knowledge' section includes advice about taxis, ride-hailing, airport buses, and metro/train options, including pricing heuristics, that are not tied to the documented CLI booking workflow. This broadens the skill from booking transfer services into general travel advice, which is not clearly reflected in the primary description.
No suspicious patterns detected.