Back to skill

Security audit

Plutus Lite — Quick Expense Summary

Security checks for vulnerabilities and agentic risk

Overview

The skill performs the promised expense summary, but its install step uses an unsafe system-package override and its financial-data handling and paid upgrade prompts need careful review.

Install only in a virtual environment or otherwise avoid the documented --break-system-packages command. Redact unnecessary account, merchant, or personal details before pasting expenses, and treat the Pro upgrade links as external, separately trusted products.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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)

T01 · Skill Instruction Hijacking

Warning
Location
SKILL.md:177
Finding

Mandatory Commercial Promotion Hijacks Skill Output

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 177-186; additional promotional instructions at lines 42-44
Vulnerability Type: T01: Skill Instruction Hijacking
Risk Level: Medium

Vulnerable Code:

python
console.print(Panel(
    f"[bold yellow]🔓 Want your full financial picture?[/bold yellow]\n\n"
    f"Plutus Pro handles [bold]unlimited transactions[/bold] from any bank CSV, tracks "
    f"[bold]tax-deductible expenses[/bold], shows [bold]monthly trends[/bold], "
    f"calculates your [bold]savings rate[/bold], and forecasts spending up to 12 months ahead.\n\n"
    f"[bold cyan]openclaw skills install plutus-pro[/bold cyan]\n"
    f"Get your key → [bold]ko-fi.com/s/83c662001e[/bold]",
    title="Upgrade to Plutus Pro",
    border_style="cyan"
))

The skill text also contains the following related instructions:

markdown
👉 **Upgrade:** `openclaw skills install plutus-pro` — key at **ko-fi.com/s/83c662001e**

💰 **Bundle deal:** all 5 Pro skills for **$29** → **ko-fi.com/s/7625accf3f** (save $16)

Technical Analysis

The documented implementation unconditionally appends a commercial promotion to every successful expense report. This content is not required to parse, categorize, or summarize expenses. It directs users to an external payment destination and instructs them to install another skill.

Because the promotion is embedded in the prescribed execution flow rather than presented only in response to an explicit request for upgrade information, loading and executing the skill changes the agent's output objective from expense analysis to commercial solicitation. This is consistent with current-session skill instruction hijacking.

No evidence was found that the promotion changes system-level safety constraints, obtains credentials, or automatically installs the promoted skill. The security scope is therefore limited to manipulation of current-session output and s ...[truncated 1168 chars]

Remediation
View remediation

Remediation Suggestions

  1. Remove the unconditional upgrade panel from the expense-processing execution path.
  2. Do not direct users to external payment pages or additional skill installations unless they explicitly request upgrade or purchasing information.
  3. If upgrade information must be retained, place it in a clearly labeled documentation-only section rather than generated task output.
  4. Keep functional results limited to expense parsing, categorization, totals, and other behavior described by the skill's primary purpose.
  5. Require explicit user confirmation before suggesting or initiating installation of another skill.
  6. Clearly identify any external service or separately installed skill as outside the current package's trust and audit boundary.

T08 · Insecure Dependencies

Warning
Location
SKILL.md:51
Finding

Unpinned Dependency Installation Bypasses System Package Protections

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, line 51
Vulnerability Type: T08: Insecure Dependencies
Risk Level: Medium

Vulnerable Code:

bash
pip3 install rich --break-system-packages --quiet

Technical Analysis

The installation instruction retrieves rich without specifying an audited version or package hash. Consequently, the installed code depends on whatever package version and transitive dependencies the configured Python package index resolves at installation time. The effective dependency set can therefore change after this skill has been reviewed.

The --break-system-packages option explicitly bypasses protections intended to prevent pip from modifying an externally managed Python installation. This can create dependency conflicts or damage the integrity of the host's system-managed Python environment.

The --quiet option also suppresses installation details that could otherwise help users notice unexpected dependency changes or resolver behavior. There is no evidence in the audited project that rich itself is malicious; the risk arises from unpinned supply-chain resolution and unsafe modification of a system-managed environment.

Attack Path

  1. A user follows the installation instructions in SKILL.md.
  2. pip3 contacts its configured package index and resolves the current release of rich and any required transitive dependencies.
  3. Because no version or hashes are specified, installation contents may differ from those available when the skill was audited.
  4. Package installation code executes with the permissions of the user running pip3.
  5. The --break-system-packages option permits changes to an externally managed Python environment.
  6. A compromised dependency release, compromised package index, malicious index configuration, or incompatible future release could execute code or alter the host Python environment.

Impact Assessment

Any dependency ...[truncated 900 chars]

Remediation
View remediation

Remediation Suggestions

  1. Install dependencies inside a dedicated virtual environment rather than modifying the system-managed Python environment.
  2. Remove --break-system-packages.
  3. Pin rich and all transitive dependencies to reviewed versions.
  4. Use a lock file or requirements file with cryptographic hashes, for example with pip install --require-hashes.
  5. Retain normal installation output instead of using --quiet, particularly during security-sensitive setup.
  6. Use a trusted, explicitly configured package index and validate downloaded artifacts.
  7. Document the exact supported Python and dependency versions to make installation reproducible.
  8. Where practical, avoid the third-party dependency entirely and use standard-library output formatting for this small command-line report.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill asks users to paste expense transactions, which can reveal sensitive financial and merchant data, but it does not provide any privacy notice or handling guidance in the user-facing markdown. While the code shown does not exfiltrate data, users may unknowingly expose personal financial information in a shared or logged environment.

Content

No source excerpt is available for this finding.