T08 · Insecure Dependencies
- Location
SKILL.md:34- Finding
Mutable Third-Party CLI Is Downloaded and Executed Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 34-68
Additional Locations:SKILL.md, lines 225-228;references/cli-commands.md, lines 10-155;references/token-setup.md, lines 31-37 and 154-185
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: HighVulnerable Code:
bash npx daxiapi-cli@latest config get token # If not configured: npx daxiapi-cli@latest config set token YOUR_TOKENbash # 1. Market structure npx daxiapi-cli@latest market compass # 2. Turnover npx daxiapi-cli@latest turnover # 3. Market-cap style npx daxiapi-cli@latest market style # 4. Sector heatmap npx daxiapi-cli@latest sector heatmap # 5. Price-limit pool npx daxiapi-cli@latest zdt # 6. Concept rankings npx daxiapi-cli@latest hotrank concept # 7. Industry rankings npx daxiapi-cli@latest hotrank boardTechnical Analysis
The mandatory workflow invokes
daxiapi-cli@latestthroughnpx. Thelatesttag is mutable, so the code executed by the Skill can change after the Skill itself has been reviewed. If the package is absent locally,npxcan download it from the npm registry and execute its package code, including applicable lifecycle behavior.No exact package version, lockfile, integrity hash, provenance requirement, or sandbox restriction is specified. Consequently, compromise of the npm package, its publisher account, or its transitive dependencies could turn an otherwise legitimate Skill invocation into arbitrary code execution.
The risk is elevated because the same CLI is given access to the DaxiAPI token and is expected to perform network operations. The audit did not establish that the current package is malicious; the vulnerability is the unsafe trust and execution model.
Attack Path
- An attacker compromises the
daxiapi-clinpm package, its publisher account, or a dependency used by a future release. - The attacker pu ...[truncated 975 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace every
daxiapi-cli@latestreference with a reviewed, exact version such asdaxiapi-cli@X.Y.Z. - Install the dependency through a committed lockfile and use a reproducible installation mechanism such as
npm ci. - Verify package provenance, publisher identity, registry source, and integrity hashes before execution.
- Review direct and transitive dependencies whenever the pinned version is updated.
- Avoid automatic package installation during Skill execution. Provision the approved CLI separately and verify its version before use.
- Disable package lifecycle scripts where compatible with the CLI.
- Run the CLI in a restricted environment with minimum filesystem access, a network allowlist, and a narrowly scoped token.
- Ensure failures in dependency verification stop execution rather than falling back to the newest available release.
- Replace every
