T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:10
- Finding
- Unpinned Third-Party Wallet Package Installation and Execution## Vulnerability Details **File Location**: `SKILL.md`, lines 10–17 **Vulnerability Type**: Unpinned npm dependency and direct remote package execution **Risk Level**: Medium ### Vulnerable Code ```bash npm install @mynthai/nova ``` ```text Or run without installing via npx (replace all `nova` usage with `npx @mynthai/nova`) ``` ### Technical Analysis The Skill instructs the Agent to install or execute `@mynthai/nova` without specifying an exact package version, lockfile, integrity hash, or signature. Consequently, npm resolves a mutable registry version at execution time rather than a version whose contents were available during this audit. The `npx @mynthai/nova` alternative is particularly sensitive because it can download and immediately execute remotely supplied package code. npm installation lifecycle scripts may also execute unless separately disabled. Although the documented npm package and GitHub project identities appear consistent, the dependency implementation is not included in this project and could not be reviewed. This is especially security-sensitive because the package operates a cryptocurrency wallet, handles authentication, accesses wallet state, can expose key material through export operations, and can authorize irreversible financial transactions. ### Attack Path 1. An attacker compromises the npm publisher account, registry distribution path, or another component of the package’s release pipeline. 2. The attacker publishes a malicious version under the legitimate package name. 3. An Agent follows the Skill instructions and runs the unpinned `npm install` or `npx` command. 4. npm resolves the attacker-controlled current version. 5. Malicious lifecycle scripts or CLI code execute with the invoking user’s permissions. 6. The package may read accessible wallet data or credentials, alter destinations, initiate unauthorized transactions, or exfiltrate exported private keys and mnemonic phrases. ### Impact Assessment Successful explo ...[truncated 631 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the dependency to an exact, reviewed version rather than relying on the latest registry resolution: ```bash npm install --save-exact @mynthai/nova@<reviewed-version> ``` 2. Provide and enforce a lockfile containing registry integrity metadata. 3. Verify package provenance, signatures, and integrity before installation or execution. 4. Avoid automatic `npx` retrieval. If npx remains supported, require an exact reviewed version and explicit user approval: ```bash npx @mynthai/nova@<reviewed-version> ``` 5. Disable npm lifecycle scripts where compatible: ```bash npm install --ignore-scripts --save-exact @mynthai/nova@<reviewed-version> ``` 6. Run wallet tooling under a dedicated least-privilege account or isolated environment with narrowly scoped filesystem and network access. 7. Require a fresh security review before changing the pinned package version. 8. Document an authenticated release source and a trusted checksum or signature verification procedure.