Back to skill

Security audit

Trades Longevity Training

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed occupational fitness planning aid, but users should understand it stores health-adjacent notes locally.

Before installing, consider whether you are comfortable with local files such as user_profile.md, workout_log.md, and pain_tracker.md containing pain, injury, age, and activity details. Keep those files in a private location, delete them when no longer needed, and use a trusted or pinned installer source where possible.

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 (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:16
Finding

Unpinned Package Execution Through npx

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 16–24
Vulnerability Type: Unpinned third-party package execution
Risk Level: Medium

Vulnerable Code

markdown
  openclaw:
    requires:
      tools: [filesystem]
    install: "npx clawhub install trades-longevity-training"
---

# Trades Longevity Training

`npx clawhub install trades-longevity-training`

Technical Analysis

The installation instructions invoke the clawhub npm package through npx without specifying an exact version, integrity hash, lockfile, or trusted registry. Depending on the local npm and npx configuration, the command may download and execute the package version currently selected by the package registry.

Because the resolved package can change after this Skill has been reviewed, the effective installation code is not fully represented by the audited project. Compromise of the upstream package, its publishing account, or the configured package registry could therefore turn this documented installation step into a supply-chain execution vector.

The audit did not establish that the current clawhub package is malicious. The issue is that the command executes mutable, externally supplied package code without a mechanism that binds installation to a specifically reviewed artifact.

Attack Path

  1. An attacker compromises the clawhub package, its publisher account, or a package registry used by the victim.
  2. The attacker publishes a malicious package version that can be selected by the unpinned npx command.
  3. A user or automation system follows the installation instruction in SKILL.md.
  4. npx resolves and downloads the attacker-controlled package version.
  5. Package lifecycle behavior or the invoked CLI executes with the privileges of the user running the command.
  6. The malicious package can access resources available to that user, subject to operating-system and sandbox restrictions.

Impact Assessment

Successful exploitation could ...[truncated 543 chars]

Remediation
View remediation

Remediation Suggestions

  1. Pin the installer to an exact, reviewed version, for example:

    sh
    npx --yes clawhub@<reviewed-exact-version> install trades-longevity-training
    
  2. Verify the selected package artifact against a trusted integrity digest or signed provenance before execution.

  3. Explicitly use the intended official package registry and prevent fallback to untrusted registries or mirrors.

  4. Prefer installing dependencies from a lockfile and then invoking the locally installed binary rather than allowing transient resolution at execution time.

  5. Disable or carefully review dependency lifecycle scripts where compatible with the installation process.

  6. Run installation in a least-privileged, isolated environment without unnecessary credentials or access to sensitive files.

  7. Document the reviewed package version and update it only through a controlled dependency-review process.

Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (4)

Rp1

Medium
Category
MCP Rug Pull
Confidence
94% confidence
Finding

The skill instructs users to run npx clawhub install trades-longevity-training without pinning a specific package version. This can lead to non-reproducible installs and creates supply-chain risk if a newer or compromised package version is published under the same name. The health/fitness context does not reduce the technical risk because the command still causes code retrieval and execution.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
94% confidence
Finding

A second unpinned npx clawhub install trades-longevity-training command repeats the same supply-chain exposure. If the package or its transitive dependencies change unexpectedly, users may execute unreviewed code simply by following the skill documentation. Repetition increases the chance a user will copy-paste it.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
83% confidence
Finding

In this markdown file, the 'When to Use This Skill' section defines activation in broad situational terms such as working a physically demanding job, having aches, or wanting a longer career in trades, but it does not provide specific trigger phrases, scope constraints, or exclusion examples. That ambiguity could cause the skill to be invoked in general wellness or pain-related conversations beyond the intended occupational training context.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill explicitly directs the agent to maintain filesystem logs containing health-related information such as pain, injuries, and activity status, but it does not provide a clear privacy warning, consent flow, retention policy, or access restrictions. In skill context, this is more sensitive because the data concerns medical-adjacent personal information, so unnecessary storage can expose users to privacy harm if the local environment is shared, synced, or later accessed by other tools.

Content

No source excerpt is available for this finding.