T08 · Insecure Dependencies
Error
- Location
- SKILL.md:34
- Finding
- Unpinned Package Execution Through npx## Vulnerability Details **File Location**: `SKILL.md`, lines 34-36 **Vulnerability Type**: Unpinned third-party package execution **Risk Level**: High **Vulnerable Code Snippet**: ```markdown Or run: ```bash npx zambo install ``` ``` ### Technical Analysis The installation instructions execute the `zambo` package through `npx` without specifying an exact version, integrity hash, trusted package source, or reviewed artifact. If the package is not already cached locally, `npx` can resolve and download the current package version from the configured registry before executing it. Because package resolution is mutable, the code executed at installation time may differ from the code available when this Skill was audited. A compromised package release, registry account, publisher account, dependency, or package-resolution configuration could consequently introduce arbitrary code. Package lifecycle scripts and the CLI itself may execute with the permissions of the user running the command. ### Attack Path 1. An attacker compromises the package publisher, registry entry, package dependency chain, or another component involved in package resolution. 2. The attacker publishes a malicious version under the package name resolved by `npx`. 3. A user follows the documented command without pinning a known-safe version. 4. `npx` downloads the mutable package release and executes its CLI or lifecycle code. 5. The malicious package performs arbitrary actions under the invoking user's account. ### Impact Assessment Successful exploitation could provide arbitrary code execution with the privileges of the user invoking `npx`. Depending on that user's permissions and environment, the malicious package could access local source code, configuration files, environment variables, authentication tokens, SSH material, MCP client configuration, and other user-readable data. It could also modify user-owned files or establish additional mali ...[truncated 230 chars]
- Remediation
- ## Remediation Suggestions - Pin the command to a specific, reviewed package version, such as `npx zambo@<reviewed-version> install`. - Verify the package publisher, registry source, release provenance, and cryptographic integrity before recommending execution. - Publish expected checksums or signed release metadata and provide verification instructions. - Avoid package lifecycle scripts where possible; consider `--ignore-scripts` if compatible with the installer. - Prefer downloading and reviewing a versioned artifact before execution rather than resolving and running the latest registry release automatically. - Document the local files, commands, permissions, and configuration changes performed by the installer. - Recommend running installation with the minimum required user privileges and never with administrator or root privileges unless strictly necessary.