Back to skill

Security audit

Vibe Billing Scan

Security checks for vulnerabilities and agentic risk

Overview

The skill is coherent, but it asks users to run unpinned remote commands against sensitive billing/log data and optionally install an underdocumented monitoring proxy.

Review carefully before installing. Prefer a pinned, reviewed version of the billing package, run it in a restricted environment, and do not enable the optional setup/proxy mode unless the publisher documents exactly what it changes and how to undo it.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (2)

T08 · Insecure Dependencies

Error
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, and README.md:21
Vulnerability Type: Unpinned third-party package execution
Risk Level: High

The skill repeatedly instructs users or agents to execute vibe-billing through npx without 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 scan
text

`SKILL.md:68-72`:

```markdown
### Step 4 — Set up ongoing monitoring (optional)

```bash
npx vibe-billing setup
text

`README.md:21`:

```markdown
Or run directly: `npx vibe-billing scan`

Technical Analysis

Running an unpinned package through npx may 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-billing package 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 optional setup operation reportedly installs a proxy, but the files, configuration, network destinations, and system changes involved are not documented.

Attack Path

  1. An attacker compromises the npm package, its publisher account, or another component of the package publication process.
  2. A malicious package version becomes the version resolved by the unpinned npx vibe-billing command.
  3. A ...[truncated 1102 chars]
Remediation
View remediation

Remediation Suggestions

  1. Pin vibe-billing to an exact reviewed version rather than relying on registry version resolution.
  2. Verify the downloaded package using an integrity digest or another authenticated artifact-verification mechanism.
  3. 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.
  4. Commit an appropriate lockfile where package-manager workflows are used.
  5. Document all files, environment variables, logs, and network destinations accessed by the scan.
  6. Run scanning in read-only mode with the minimum filesystem and network permissions necessary.
  7. Separate proxy installation from log analysis and require explicit informed consent before running setup.
  8. Document every configuration, proxy, certificate, startup, and network change made by the setup operation, including a complete rollback procedure.
  9. Avoid automatically executing the command from agent instructions; present the exact pinned command and request user confirmation first.

T08 · Insecure Dependencies

Error
Location
README.md:4
Finding

Mutable Installer Execution Through the Latest Release Tag

Content
View full analysis

Vulnerability Details

File Location: README.md:4-8
Vulnerability Type: Mutable installer dependency
Risk Level: High

Complete code snippet:

markdown
## Install

```bash
npx clawhub@latest install vibe-billing-scan
text

### Technical Analysis

The installation command explicitly uses the mutable `@latest` distribution tag. As a result, the code executed by this command is determined at installation time rather than being tied to the version reviewed during this audit.

`npx` can retrieve and execute the selected `clawhub` installer package. No exact version, integrity digest, lockfile, or local installer implementation is provided. Consequently, a later compromised or malicious release selected by `@latest` could execute even though the repository documentation itself has not changed.

### Attack Path

1. An attacker compromises the `clawhub` package, publisher credentials, registry publication process, or a dependency incorporated into a new release.
2. The compromised release is assigned to the `latest` distribution tag.
3. A user copies and executes the documented installation command.
4. `npx` retrieves and runs the compromised installer with the user's privileges.
5. The installer can access user-readable data and modify files or application configuration permitted to the invoking account.

### Impact Assessment

Exploitation can result in arbitrary code execution with the invoking user's privileges during installation. Potential scope includes user-owned files, application configuration, environment variables, and credentials accessible to the process. An installer may also introduce additional packages or modify the installed skill.

There is no evidence in the reviewed files that the current `clawhub` release is malicious. The issue is that `@latest` makes the effective installer mutable and prevents the documented command from being reliably associated with a reviewed artifact.
Remediation
View remediation

Remediation Suggestions

  1. Replace clawhub@latest with an exact, reviewed package version.
  2. Publish and verify an integrity digest for the installer artifact.
  3. Provide a reproducible mapping between the installer's public source code and its published npm package.
  4. Document the files, directories, dependencies, and configuration modified by installation.
  5. Require explicit confirmation before the installer executes lifecycle scripts or installs additional executable dependencies.
  6. Recommend installation in a restricted environment without unnecessary credentials or elevated privileges.
  7. Establish a controlled update procedure so newer versions are reviewed before users execute them.
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (11)

Rp1

Medium
Category
MCP Rug Pull
Confidence
87% confidence
Finding

The README instructs users to execute npx clawhub@latest install vibe-billing-scan, which pulls and runs code at install time without a pinned version. Using @latest makes the executed package mutable over time, so a compromised or malicious upstream release could cause arbitrary code execution on user machines during installation.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The trigger phrase scan my api spend / why is my bill so high is broad and resembles normal conversation a user might naturally have with an agent. In an agent ecosystem, this can cause accidental skill invocation in unrelated contexts, potentially exposing API usage logs or causing unintended execution of the billing-scan workflow when the user did not explicitly intend to run this skill.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
83% confidence
Finding

The direct-run instruction npx vibe-billing scan invokes a package without specifying an exact version, so users may fetch and execute whatever version is currently published. If the package is later hijacked, typosquatted, or updated with malicious behavior, this README becomes an execution vector for untrusted code.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The manifest description lists triggers such as "check my costs" and "why is my bill high," which are broad phrases a user could say in many contexts unrelated to this specific OpenClaw billing skill. The file does not provide exclusion conditions or negative examples to distinguish when the skill should activate versus when a general finance or troubleshooting skill should handle the request.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The "When to Use" section says to activate when the user asks about "token usage, spending, or waste," which is broad enough to match many unrelated optimization or finance discussions. Because the section lacks clear boundaries or exclusions, the invocation criteria could cause unintended triggering outside the intended OpenClaw log-analysis context.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
97% confidence
Finding

The skill instructs users to run npx vibe-billing scan without pinning a package version or verifying package integrity, which can fetch and execute whatever code is currently published under that name. Because npx executes remote package code locally, a compromised maintainer account, dependency takeover, or malicious update could lead to arbitrary code execution on the user's machine.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
97% confidence
Finding

This command uses npx vibe-billing scan without a pinned version, causing the tool to resolve and execute the latest published package at runtime. That creates a supply-chain execution risk where users may run attacker-controlled code if the package or its dependencies are hijacked.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
97% confidence
Finding

The skill advertises npx vibe-billing setup without version pinning, which can execute newly published package code during setup on the user's local environment. Setup flows are especially sensitive because they often modify proxying, configuration, or system behavior, increasing the blast radius of a malicious package update.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
96% confidence
Finding

Using npx vibe-billing status without an exact version still causes remote package resolution and execution, exposing the user to arbitrary code execution if the package source changes maliciously. Even read-only seeming commands are dangerous because the code must execute locally to produce output.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
97% confidence
Finding

The explicit instruction to run npx vibe-billing scan directly in a terminal is a true supply-chain risk because it encourages immediate execution of unverified code from a package registry. In the context of a skill, this lowers user caution and increases the chance of unsafe execution on developer workstations containing secrets and source code.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
97% confidence
Finding

The optional ongoing monitoring step again invokes npx vibe-billing setup without version pinning, compounding the risk by encouraging persistent installation or proxy configuration from untrusted latest code. Because this step appears to alter future runtime behavior, exploitation could provide durable access to API traffic or local telemetry.

Content

No source excerpt is available for this finding.