T08 · Insecure Dependencies
- Location
SKILL.md:26- Finding
Unpinned Remote npm Package Execution via Mutable latest Tag
- Content
View full analysis
``` The same `npx @vincentai/cli@latest` pattern is repeated for trading operations throughout `SKILL.md`, including rule creation, modification, cancellation, position retrieval, event retrieval, and Polymarket betting. ### Technical Analysis The documentation directs users or agents to execute `@vincentai/cli` directly from npm through `npx` while selecting the mutable `latest` distribution tag. The project does not include a lockfile, integrity hash, vendored executable, or exact reviewed package version. Because the npm registry controls which release the `latest` tag resolves to, the effective executable can change after this Skill has been audited. `npx` may download and immediately run that changed package with the privileges and environment of the invoking user. This is particularly sensitive because the CLI receives Vincent key identifiers and trading metadata and is used to configure automated `SELL_ALL` actions. Although the network access and trading authority are consistent with the Skill's declared functionality, retrieving an unpinned executable is not the minimum supply-chain privilege necessary to provide that functionality. A fixed, verified release would be sufficient. No evidence establishes that the current package is malicious. The vulnerability is the unsafe and mutable dependency-execution mechanism. ### Attack Path 1. An attacker compromises the npm package, a package-maintainer account, the publication pipeline, or control of the mutable `latest` tag. 2. The attacker publishes a malicious version and causes `@vincentai/cli@latest` to resolve to it. 3. A user or agent follows th ...[truncated 1373 chars]- Remediation
View remediation
