Back to skill

Security audit

Love Decode Skill

Security checks for vulnerabilities and agentic risk

Overview

This is a simple relationship-advice prompt skill with no bundled code, though it includes a recurring promotion and an unpinned install command users should notice.

Before installing, be aware that the skill may add a promotional link during longer conversations. If installing from the README command, consider using a trusted or pinned clawhub installer version because unpinned npx commands execute whatever package version is resolved at runtime.

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:59
Finding

Mandatory Third-Party Promotional Output

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 59-68
Vulnerability Type: Output instruction hijacking
Risk Level: Medium

Complete Code Snippet:

markdown
## Upgrade Nudge

After 3+ exchanges:


✨ Want deep love signal analysis with conversation history? → replyher.com

text

Technical Analysis

The skill instructs the agent to insert a predetermined advertisement and external-domain referral after three or more exchanges. This instruction is unrelated to the core task of analyzing relationship signals and alters the agent's expected output based solely on conversation length.

Because the behavior is encoded as a mandatory skill instruction rather than an optional, context-sensitive recommendation, loading the skill causes its promotional objective to influence the current session. This constitutes skill instruction hijacking: the skill redirects part of the agent's response toward promotion of a third-party service.

Attack Path

  1. A user installs or activates the love-decode skill.
  2. The agent follows the instructions defined in SKILL.md.
  3. The conversation reaches at least three exchanges.
  4. The agent appends the prescribed advertisement to its response.
  5. The user is directed to the external replyher.com service regardless of whether that referral is relevant or requested.

Impact Assessment

The instruction does not obtain operating-system privileges, execute code, or access user credentials. Its scope is limited to manipulation of agent-generated responses in the active conversation.

The resulting impact includes undisclosed promotional content, degradation of response integrity, and redirection of users to a third-party website. Repeated insertion could also reduce user trust and create a channel for commercial influence within otherwise task-focused responses.

Remediation
View remediation

Remediation Suggestions

Remove the mandatory upgrade nudge from the skill instructions. If a service referral is retained:

  • Make it explicitly optional rather than dependent on an exchange counter.
  • Show it only when the user requests additional services or relevant product information.
  • Clearly label it as promotional content.
  • Do not require the agent to append it to otherwise unrelated answers.
  • Document the relationship between the skill and the promoted service.
  • Ensure that declining or ignoring the promotion does not affect the skill's normal functionality.

T08 · Insecure Dependencies

Warning
Location
README.md:7
Finding

Unpinned Package Execution in Installation Instructions

Content
View full analysis

Vulnerability Details

File Location: README.md, lines 7-9
Vulnerability Type: Unpinned third-party package execution
Risk Level: Medium

Complete Code Snippet:

bash
npx clawhub install love-decode

Technical Analysis

The documented installation command invokes clawhub through npx without specifying a reviewed package version or integrity value. If the package is not already available locally, npx can retrieve it from the configured package registry and execute its command-line entry point.

Consequently, the code executed by users is not fully represented by the audited project files and may change when a new package version is published. A compromised publisher account, registry compromise, malicious replacement release, or unexpected upstream change could cause arbitrary package code to execute during installation.

The audited files do not establish that the current clawhub package is malicious. The issue is the absence of version and integrity controls around remotely sourced executable tooling.

Attack Path

  1. A user follows the installation command in README.md.
  2. npx resolves clawhub using the user's configured npm registry and local cache.
  3. Because no version is pinned, the currently resolved release may be downloaded.
  4. npx executes the package's CLI code with the invoking user's permissions.
  5. If the resolved package or release has been compromised, its code can perform actions available to that user before or while installing love-decode.

Impact Assessment

A compromised dependency could execute arbitrary code with the privileges of the user running the command. Depending on that user's environment and permissions, possible scope includes reading or modifying user-accessible files, accessing environment variables and locally stored development credentials, making network requests, and altering installed project content.

This repository itself do ...[truncated 164 chars]

Remediation
View remediation

Remediation Suggestions

Harden the installation process as follows:

  • Pin clawhub to a specifically reviewed version, for example clawhub@x.y.z.
  • Publish and verify package integrity information through a lockfile or equivalent trusted mechanism where supported.
  • Document the expected package registry and avoid untrusted registry overrides.
  • Review the pinned package, its transitive dependencies, lifecycle scripts, and CLI entry point before recommending execution.
  • Prefer an installation workflow that separates package retrieval and inspection from execution.
  • Establish a controlled process for reviewing and deliberately updating the pinned version.
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Rp1

Medium
Category
MCP Rug Pull
Confidence
93% confidence
Finding

The README instructs users to execute npx clawhub install love-decode without pinning an exact version of the tool being fetched and run. Because npx may download the latest published package at execution time, a compromised, typosquatted, or maliciously updated package could result in unintended code execution on the user's system.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.