T08 · Insecure Dependencies
- Location
SKILL.md:49- Finding
Unpinned npm Package Is Downloaded and Executed at Runtime
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 49–71, with repeated invocations at lines 86–91, 208, 215, 224, 235, 243, 250, and 398
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code Snippet:
bash npx daxiapi-cli@latest config get tokenbash # Method 1: Configure through the CLI npx daxiapi-cli@latest config set token YOUR_TOKEN_FROM_DAXIAPI # Method 2: Set an environment variable export DAXIAPI_TOKEN=YOUR_TOKEN_FROM_DAXIAPIbash npx daxiapi-cli@latest marketThe same unpinned execution pattern is prescribed for market analysis:
bash npx daxiapi-cli@latest market index npx daxiapi-cli@latest market temp npx daxiapi-cli@latest sector heatmap npx daxiapi-cli@latest stock limit npx daxiapi-cli@latest market style npx daxiapi-cli@latest stock topTechnical Analysis
The Skill repeatedly instructs the agent or user to invoke
daxiapi-cli@latestthroughnpx. If the package is unavailable locally,npxcan retrieve it from the configured npm registry and immediately execute its code.The
@latestversion selector is mutable. Consequently, the code executed during a future Skill invocation may differ from the code that existed when this Skill was audited. The project does not provide an exact package version, integrity hash, lockfile, vendored copy, or other mechanism that makes the executable dependency reproducible.This creates a supply-chain trust boundary in which a compromised package publisher, npm account, registry, or future package release could introduce arbitrary executable behavior. No evidence establishes that the current package is malicious; the vulnerability is the unsafe, mutable dependency execution model.
Attack Path
- An attacker compromises the npm package publisher account, registry distribution channel, or another component capable of modifyin ...[truncated 1131 chars]
- Remediation
View remediation
Remediation Suggestions
-
Replace
@latestwith an exact, reviewed package version, for example:bash npx --yes daxiapi-cli@X.Y.Z market index -
Verify the selected package version, publisher identity, expected registry, and package provenance before documenting it.
-
Record and validate the expected package integrity hash where the deployment mechanism supports integrity verification.
-
Prefer installing dependencies through a project manifest and lockfile rather than downloading executable code during every invocation.
-
Consider vendoring or wrapping the minimum reviewed functionality so that the executable implementation cannot change independently of the Skill.
-
Run the CLI with least privilege and restrict its access to unrelated files, credentials, and network destinations where practical.
-
Establish a controlled dependency-update process that requires review and security testing before changing the pinned version.
-