T08 · Insecure Dependencies
Error
- Location
SKILL.md:15- Finding
Unpinned Third-Party Package Execution
- Content
View full analysis
`). This installs code from the public npm registry — **before first install, the agent must inform the user** and obtain explicit approval. Users should review: [npm package](https://www.npmjs.com/package/naracli), [GitHub source](https://github.com/nara-chain/nara-cli) - **Security**: Open-source, auditable on GitHub. The package does not upload, collect, or transmit wallet secrets — all key material stays local on disk - Run `npx naracli help` and `npx naracli --help` to learn all available commands and options before use - **Updates**: Use `npx naracli@latest` to ensure the latest CLI version ``` ### Technical Analysis The Skill instructs the agent to execute a mutable npm package without pinning an exact reviewed version or verifying an integrity digest. Both `npm install -g naracli` and ordinary `npx naracli` resolve package content through the public npm registry. The explicit recommendation to use `npx naracli@latest` ensures that future, potentially unreviewed releases are executed. User approval informs the user that external code will run, but it does not establish that the registry artifact is identical to the reviewed GitHub source. It also does not protect against compromise of the npm package, maintainer account, release pipeline, or transitive dependencies. Because the CLI manages cryptocurrency wallets and transactions, it is likely to operate in a context where wallet files and other sensitive local data are accessible. The package implementation is not included in the audited artifact, so the statement that secrets remain local cannot be independently verified. ### Attack Path 1. An attacker compromises the npm package, a maintainer account, the release pipeli ...[truncated 1138 chars]- Remediation
View remediation