T08 · Insecure Dependencies
- Location
SKILL.md:35- Finding
Execution of an Unpinned Third-Party Package Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:35-45; additional occurrences inreferences/cli-commands.md:10, 58-78, 105-111andreferences/token-setup.md:67-83, 107
Vulnerability Type: Unpinned runtime dependency and software supply-chain exposure
Risk Level: MediumVulnerable Code Snippet:
bash npx daxiapi-cli@latest config get token # If it is not configured: npx daxiapi-cli@latest config set token YOUR_TOKENbash npx daxiapi-cli@latest market styleTechnical Analysis
The documentation repeatedly instructs the Agent to execute
daxiapi-cli@latestthroughnpx. Thelatesttag is mutable and does not identify a fixed, previously audited package version. Depending on the local npm cache and configuration,npxcan download the current package release and execute its code, including applicable package lifecycle behavior, with the permissions of the invoking user.The project does not pin an exact version, provide a lockfile, verify a package integrity hash, or identify a trusted package release. Consequently, the code ultimately executed can change after this Skill has been reviewed. A compromised publisher account, malicious package update, or upstream package compromise could turn the documented command into an arbitrary code-execution path.
Attack Path
- An attacker compromises the npm publisher account or upstream package distribution process for
daxiapi-cli. - The attacker publishes a malicious release and assigns it to the
latestnpm tag. - A user or Agent follows the Skill and runs
npx daxiapi-cli@latest. npxretrieves and executes the malicious release.- The package executes under the user's account and can access resources available to that account.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the user running the Agent. The effective scope may include reading or modifyi ...[truncated 317 chars]
- An attacker compromises the npm publisher account or upstream package distribution process for
- Remediation
View remediation
Remediation Suggestions
- Replace
daxiapi-cli@latestwith an exact, reviewed version such asdaxiapi-cli@X.Y.Z. - Record and verify the package integrity hash using a lockfile or another reproducible dependency-verification mechanism.
- Document the official npm package URL, expected publisher identity, and trusted release source.
- Review package lifecycle scripts and package contents before allowing execution.
- Prefer installing dependencies in an isolated, least-privileged environment rather than downloading and executing them during each Skill invocation.
- Establish a controlled upgrade process in which new versions are reviewed and tested before the pinned version is changed.
- Replace
