T08 · Insecure Dependencies
- Location
reference/core-workflow.md:3- Finding
Mandatory Installation and Execution of an Unpinned Third-Party Package
- Content
View full analysis
Vulnerability Details
File Location:
reference/core-workflow.md:3-12; related package identity inconsistency atreference/tools.md:26-34
Vulnerability Type: Supply-chain exposure through mutable dependency installation
Risk Level: HighVulnerable Code:
markdown ### Prerequisite: Install/Upgrade FlyAI CLI Before executing any search, the installation command must be executed first, regardless of whether the package is already installed, to ensure the latest version: ```bash npm install -g @fly-ai/flyai-cli@latest --registry=https://registry.npmjs.orgAfter installation, verify it:
bash flyai --helptext The related tool documentation identifies a different package: ```markdown ## FlyAI Core Capabilities Use `npx @anthropic-ai/flyai-cli@latest` to access travel data.Technical Analysis
The workflow mandates installation and execution of the mutable
latestversion of a third-party npm package. Becauselatestcan resolve to different code after the Skill has been audited, the effective executable payload is not fixed by the reviewed artifact.npm installation may execute package lifecycle scripts, including
preinstall,install, andpostinstall. A compromised package release, maintainer account, registry response, or package name could therefore introduce arbitrary local code execution.The project also identifies the CLI using two different package names:
@fly-ai/flyai-cliand@anthropic-ai/flyai-cli. This inconsistency increases the likelihood that an unintended or spoofed package will be installed or executed.Attack Path
- An attacker compromises the referenced npm package, its publisher account, or the package resolution process.
- The attacker publishes a malicious version and assigns it to the
latesttag. - A user activates the Skill and initiates a travel search.
- The mandatory prerequisite runs `npm install -g ...@late ...[truncated 820 chars]
- Remediation
View remediation
Remediation Suggestions
- Select and document one verified package identity; resolve the discrepancy between
@fly-ai/flyai-cliand@anthropic-ai/flyai-cli. - Pin an exact audited version rather than using
@latest. - Lock and verify the package integrity hash through a lockfile or equivalent trusted manifest.
- Do not automatically install or upgrade the package when the Skill is invoked.
- Require explicit informed user approval before installing any executable dependency.
- Prefer a project-local installation in an isolated environment rather than a global package.
- Review package contents and lifecycle scripts before approving upgrades.
- Where practical, disable npm lifecycle scripts and execute the CLI inside a restricted container or sandbox.
- Select and document one verified package identity; resolve the discrepancy between
