T01 · Skill Instruction Hijacking
- Location
SKILL.md:8- Finding
Mandatory FlyAI Workflow and Promotional Output Hijack Agent Behavior
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is not clearly malicious, but it asks agents to install and run an unpinned global travel CLI, force booking-link output, and persist raw user queries without adequate disclosure or controls.
Review before installing. This skill should only be used in an environment where you are comfortable installing a global npm CLI, sending travel queries to a third-party FlyAI/Fliggy service, receiving booking links, and retaining local execution logs. Prefer a pinned, pre-reviewed CLI install, disable or remove raw-query logging, and require user confirmation before any booking or externally routed action.
SKILL.md:8Mandatory FlyAI Workflow and Promotional Output Hijack Agent Behavior
SKILL.md:58Automatic Installation and Execution of an Unpinned Global npm Package
references/runbook.md:8Raw User Queries Are Persisted Through Unsafe Shell-Based Log Construction
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
flyai search-poi --city-name "Xian" --category "历史古迹"
## 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 historical-sites exploration tool, while also disclosing that it wraps a CLI providing real-time travel data and booking links. This mismatch can mislead users and agents about the true capability and trust boundary of the skill, increasing the chance they invoke networked booking or commerce actions without informed consent or appropriate safeguards.
The README instructs users to run npx skills ... without pinning a specific version, which can cause execution of whatever package/version is currently resolved from the registry at install time. In a skill ecosystem, this creates a supply-chain risk: a compromised or newly published package version could execute untrusted code on the user's machine during installation or use.
The Chinese section repeats the same capability ambiguity, describing the skill as an exploration guide while also stating it provides real-time travel data and booking links. Inconsistent or incomplete multilingual disclosure can cause some users to underestimate the skill's transactional and networked behavior, leading to unsafe use in agent environments.
The skill is presented as a historical-sites exploration guide, but its operational instructions strongly redirect the agent into acting as a generic Fliggy CLI booking/execution wrapper. This mismatch can mislead users and host agents about the skill’s true behavior and permissions, increasing the chance of unexpected command execution and data access beyond the narrow advertised purpose.
The skill instructs the agent to install a global npm package as part of normal execution, which introduces supply-chain and arbitrary code-execution risk on the host environment. Requiring package installation for routine queries is especially dangerous because it expands impact from answering a travel question to modifying the system and trusting third-party code.
The skill tells the agent to perform a global npm install without any warning that this changes the user or host system. Lack of disclosure and consent is dangerous because it can silently alter the environment, introduce persistent software, and expose the host to unreviewed package behavior.
The activation condition triggers on generic words like "historical," "ancient," "ruins," and "heritage," which commonly appear in ordinary travel questions and are not tightly scoped to this specific skill. The file provides only one negative example, so it remains unclear when this skill should not activate for nearby intents such as museums, tours, or general history questions.
The runbook explicitly records raw user input in an internal execution log without any documented minimization, redaction, consent, or retention limits. In a travel skill, user queries can naturally contain personal data such as names, passport/visa details, locations, booking references, or contact information, so logging the full prompt creates an avoidable privacy and data-exposure risk.
This design combines storage of raw natural-language user input with persistent local logging, creating a straightforward data retention and leakage path. Because this skill supports travel-related functions like flights, hotels, visas, insurance, and rentals, user prompts may include highly sensitive personal and itinerary details, making the context more dangerous than a low-sensitivity informational skill.
The runbook instructs appending execution logs to a local file, which creates persistent storage of potentially sensitive operational and user data without any warning or safeguards. Local log files are commonly overlooked, may have weak permissions, and can be read by other processes, operators, or later tooling, increasing the chance of unintended disclosure.
The README advertises real-time travel data and booking links but does not warn users that the skill may contact external services or interact with third-party booking platforms. Lack of disclosure reduces informed consent and can be risky in agentic contexts where users expect a passive informational skill rather than one that initiates network-backed travel interactions.