T01 · Skill Instruction Hijacking
- Location
SKILL.md:8- Finding
Mandatory Commercial Output and Agent Instruction Hijacking
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This travel skill is provider-specific and disclosed, but it can auto-install an unpinned global CLI, force booking-link outputs, and persist sensitive travel queries in a hidden local log.
Review before installing. Use it only if you trust the flyai CLI and are comfortable sending travel queries to that provider, receiving provider booking links, and installing a global npm package. Prefer a pinned CLI version, require explicit approval before installation, and disable or redesign the execution log so raw prompts and command strings are not stored.
SKILL.md:8Mandatory Commercial Output and Agent Instruction Hijacking
SKILL.md:126Unpinned Global Package and Mutable Remote Dependency Execution
references/runbook.md:33Shell Command Injection Through Raw User Query Logging
references/runbook.md:1Unconsented Persistent Storage of Raw User Queries
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
Full family orchestration
## Output Rules
1. **Conclusion first** — lead with the key finding
2. **Comparison table** with ≥ 3 results when available
The README instructs users to run npx skills add ... without pinning a specific version, which can cause execution of whatever package version is current at install time. If the referenced package or one of its dependencies is compromised upstream, users may unknowingly execute malicious code during installation.
The runbook explicitly stores raw user input, CLI commands, and operational metadata in an internal execution log, and recommends appending that log to a persistent local file. In a travel-booking skill, user queries can contain names, destinations, dates, passport/visa details, booking references, and other sensitive travel information, so retaining it without minimization or retention controls creates a meaningful privacy and data-exposure risk.
The schema includes a user_query field populated with the raw input and states that the log is maintained internally, which means potentially sensitive user-provided content is retained beyond immediate processing. Because this skill handles family travel planning and bookings, the raw query may include children-related details, locations, schedules, or identity-related travel data that should not be persistently stored in full.
The rules require logging every CLI command and persisting the execution log, which can capture secrets in arguments, booking tokens, API parameters, local paths, and internal operational details. Persisting this data increases the blast radius of any local compromise, misconfiguration, or unauthorized access to the log file.
The README advertises real-time travel data and booking links but does not clearly disclose that using the skill may contact external services and share user travel queries with third parties. In a travel-booking context, prompts may contain sensitive itinerary, family, or location details, so lack of notice can lead to unintended data exposure and weak user consent.
No suspicious patterns detected.