T08 · Insecure Dependencies
- Location
SKILL.md:56- Finding
Unpinned Third-Party Package Execution in a Credential-Bearing Context
- Content
View full analysis
\ --safe \ --to \ --value-eth \ --nonce \ --human-signer-passkey-x \ --human-signer-passkey-y \ --recovery-signer ``` The same unversioned executable is also used for transaction, nonce, and gas-price queries: ```bash npx nodpay txs --safe npx nodpay nonce --safe --chain npx nodpay gasprice --chain ``` ### Technical Analysis The Skill repeatedly invokes `npx nodpay` without specifying an exact package version, lockfile, package integrity hash, or other immutable artifact identifier. In an environment where the package is not already installed, `npx` may resolve and download the package currently published under the `nodpay` name. Consequently, the code executed during a future Skill invocation can differ from the code that was reviewed. The metadata identifies a GitHub source repository, but the documented commands resolve through the npm ecosystem and do not verify that the retrieved npm artifact corresponds to a reviewed source revision. This dependency executes in a particularly sensitive context. According to the Skill specification, the CLI reads the agent signing key from `~/.nodpay/.env` and creates signed cryptocurrency payment proposals. A compromised dependency would therefore execute with both the operating-system permissions of the Agent user and access to wallet-related credentials. ### Attack Path 1. An att ...[truncated 1611 chars]- Remediation
View remediation
