T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned npm Package Is Downloaded and Executed Through npx
- Content
View full analysis
[args...] npx @builtbyecho/trustlog summarize .trustlog/latest.json npx @builtbyecho/trustlog verify .trustlog/latest.json ``` ### Technical Analysis The instructions invoke `@builtbyecho/trustlog` through `npx` without specifying an exact package version, lockfile, or integrity hash. Depending on the local npm configuration and cache state, `npx` can retrieve the current package release from the npm registry and immediately execute it. Consequently, the code executed by the Skill can change after the Skill itself has been audited. If the package, one of its transitive dependencies, or its publisher account is compromised, a malicious release could execute with the same operating-system privileges and environment access as the agent. The wrapper also runs in the target project root. This gives the downloaded package an opportunity to inspect project files, environment variables, configuration files, generated receipts, and command arguments before or while launching the requested test or build command. ### Attack Path 1. An attacker compromises the npm publisher account, package, or a transitive dependency associated with `@builtbyecho/trustlog`. 2. The attacker publishes a malicious release under the expected package name. 3. An agent follows `SKILL.md` and runs the unversioned `npx @builtbyecho/trustlog` command. 4. `npx` retrieves and executes the malicious package release. 5. The package reads accessible source files, credentials, environment variables, or command output, and may modify files or transmit ...[truncated 767 chars]- Remediation
View remediation
