Back to skill

Security audit

Blood Sugar Tracker

Security checks for vulnerabilities and agentic risk

Overview

This is a small blood-sugar tracking skill with disclosed, purpose-aligned behavior and no evidence of hidden code, persistence, exfiltration, or privilege escalation.

Install only through a ClawHub/npm source you trust, prefer a pinned installer version if available, and remember that blood sugar entries are sensitive health data. Treat any diet or abnormal-range guidance as informational rather than a substitute for medical advice.

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
README.md:5
Finding

Mutable Package Version Executed During Installation

Content
View full analysis

Vulnerability Details

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

bash
npx clawhub@latest install blood-sugar-tracker

Technical Analysis

The documented installation procedure invokes npx with the mutable latest tag. If the package is not already available locally, npx retrieves it from the configured npm registry and executes its command-line entry point. The package may also run lifecycle scripts during installation.

Because latest can be reassigned to a different release at any time, the code executed by this command is not fixed to the version that was reviewed when the documentation was published. No exact version, lockfile, integrity digest, or provenance-verification procedure is supplied. Consequently, compromise of the package publisher, registry account, or a future release could turn this documented installation command into a supply-chain execution vector.

Attack Path

  1. An attacker compromises the clawhub package publisher account, publishing pipeline, or relevant registry distribution channel.
  2. The attacker publishes a malicious release and assigns the mutable latest tag to it.
  3. A user follows the installation command from README.md.
  4. npx downloads the attacker-controlled package release.
  5. Malicious lifecycle scripts or the package's command-line entry point execute under the user's account.
  6. The payload can access resources available to that user and can modify files or invoke additional programs within the user's permission boundaries.

Impact Assessment

Successful exploitation permits arbitrary code execution with the privileges of the user running the documented command. Potential impact includes theft of user-accessible credentials and files, modification of local project or configuration data, execution of additional payloads, and compromise of development environments. T ...[truncated 236 chars]

Remediation
View remediation

Remediation Suggestions

  1. Replace the mutable latest tag with an exact, reviewed version, for example:
    bash
    npx clawhub@1.2.3 install blood-sugar-tracker
    
  2. Review the selected release, including its command-line entry point, transitive dependencies, and npm lifecycle scripts, before recommending it.
  3. Prefer installing the tool as a pinned project dependency and committing the applicable lockfile so dependency versions and integrity values are reproducible.
  4. Configure and document the expected trusted npm registry rather than relying on an arbitrary user-level registry configuration.
  5. Verify package provenance, signatures, and published integrity metadata where supported.
  6. Establish an update process in which the pinned version is changed only after the new release has undergone security review.
  7. Advise users not to execute the installation command with elevated privileges.
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • 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 (3)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The skill description and section headings are written in Chinese, and the file does not indicate that language selection is optional or that the skill is intended only for a Chinese-speaking or region-specific audience. This can violate language/locale policy when users are not given an explicit opt-in or alternative language.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
91% confidence
Finding

The README instructs users to run npx clawhub@latest install blood-sugar-tracker, which pulls a moving package version at execution time rather than a pinned, audited release. This creates a supply-chain risk: if the upstream package is compromised or a breaking/malicious version is published later, users following the documentation may execute unreviewed code on their systems.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The manifest description and user-facing content are written entirely in Chinese, with no indication that the skill supports other languages or that Chinese is required for a region-specific purpose. This creates a language/locale policy concern because it effectively imposes a specific language on users without opt-in.

Content

No source excerpt is available for this finding.