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