T08 · Insecure Dependencies
- Location
SKILL.md:35- Finding
Execution of an Unpinned Third-Party Billing Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:35-37,SKILL.md:48-52,SKILL.md:68-72, andREADME.md:21
Vulnerability Type: Unpinned third-party package execution
Risk Level: HighThe skill repeatedly instructs users or agents to execute
vibe-billingthroughnpxwithout specifying a package version or integrity value.Complete relevant code snippets:
SKILL.md:35-37:markdown Runs `npx vibe-billing scan` against the user's local OpenClaw logs and API proxy data. Returns:SKILL.md:48-52:markdown ```bash npx vibe-billing scantext `SKILL.md:68-72`: ```markdown ### Step 4 — Set up ongoing monitoring (optional) ```bash npx vibe-billing setuptext `README.md:21`: ```markdown Or run directly: `npx vibe-billing scan`Technical Analysis
Running an unpinned package through
npxmay cause npm to retrieve and execute the package version currently selected by the package registry. The executable code is not included in this repository, and the project contains no package lockfile, integrity digest, or reviewed implementation tying the documented behavior to a specific artifact.This creates a supply-chain trust gap: the two audited Markdown files remain unchanged even if the remotely distributed
vibe-billingpackage changes after review. The risk is particularly significant because the documented scan processes local OpenClaw logs and API proxy data, which may contain sensitive prompts, request metadata, endpoint details, or credentials. The optionalsetupoperation reportedly installs a proxy, but the files, configuration, network destinations, and system changes involved are not documented.Attack Path
- An attacker compromises the npm package, its publisher account, or another component of the package publication process.
- A malicious package version becomes the version resolved by the unpinned
npx vibe-billingcommand. - A ...[truncated 1102 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
vibe-billingto an exact reviewed version rather than relying on registry version resolution. - Verify the downloaded package using an integrity digest or another authenticated artifact-verification mechanism.
- Include the executable implementation in the reviewed project, or provide a reproducible source repository and build process that maps source code to the published package.
- Commit an appropriate lockfile where package-manager workflows are used.
- Document all files, environment variables, logs, and network destinations accessed by the scan.
- Run scanning in read-only mode with the minimum filesystem and network permissions necessary.
- Separate proxy installation from log analysis and require explicit informed consent before running setup.
- Document every configuration, proxy, certificate, startup, and network change made by the setup operation, including a complete rollback procedure.
- Avoid automatically executing the command from agent instructions; present the exact pinned command and request user confirmation first.
- Pin
