Back to skill

Security audit

Cycling Tracker Pro

Security checks for vulnerabilities and agentic risk

Overview

This is a simple cycling-tracker skill whose behavior is disclosed, but users should be aware that its README suggests an unpinned npx install command.

Before installing, consider using a pinned or trusted ClawHub installer version instead of `@latest`, and note that the documentation is primarily in Chinese. The inspected skill content itself is narrow and purpose-aligned.

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

Unpinned Package Execution Through npx

Content
View full analysis

Vulnerability Details

File Location: README.md, line 6
Vulnerability Type: T08: Insecure Dependencies
Risk Level: Medium

bash
npx clawhub@latest install cycling-tracker-pro

Technical Analysis

The documented installation command instructs users to retrieve and execute the mutable latest release of the clawhub npm package. The project does not pin a reviewed package version, provide an integrity hash, or identify a verified distribution source.

Because npx can download and immediately execute a package, the code executed during installation is not limited to the contents of the audited project. The effective installation behavior can change whenever the package publisher updates the latest tag. Exploitation requires the resolved package or its publishing infrastructure to be compromised, maliciously modified, or otherwise made untrustworthy.

Attack Path

  1. An attacker compromises the npm package, a maintainer account, or another component of the package-distribution chain.
  2. The attacker publishes a malicious release and assigns it to the latest distribution tag.
  3. A user follows the installation command from README.md.
  4. npx retrieves and executes the attacker-controlled package release.
  5. Malicious package lifecycle or command code runs with the privileges of the user performing the installation.

Impact Assessment

Successful exploitation could permit arbitrary code execution under the installing user's account. The resulting scope may include access to files, environment variables, credentials, network resources, and other assets available to that user. The reviewed artifact itself contains no malicious package implementation, so this risk is conditional on compromise or malicious modification of the external dependency.

Remediation
View remediation

Remediation Suggestions

  • Replace the mutable @latest reference with an explicitly pinned and reviewed version, such as clawhub@X.Y.Z.
  • Document the expected official registry and publisher identity.
  • Verify package provenance and integrity before execution, using registry signatures, trusted provenance attestations, or integrity hashes where supported.
  • Review the pinned package and its dependency tree for lifecycle scripts and known vulnerabilities.
  • Update the pinned version only through a controlled review and testing process.
  • Where practical, install in a restricted environment or container with minimal filesystem, credential, and network access.
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
95% confidence
Finding

The README presents the skill description and all user-facing documentation in Chinese, while the title is in English, and there is no indication that the language choice is optional or region-specific. This can violate a language/locale policy when users are not given an opt-in or alternative language.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
95% confidence
Finding

The installation command uses npx clawhub@latest, which fetches and executes the latest published package version at install time rather than a pinned, reviewed version. This creates a supply-chain risk: if the upstream package is compromised or a breaking/malicious release is published, users may execute untrusted code simply by following the README.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
95% confidence
Finding

The description and introductory text are written in Chinese, and the file does not indicate that the skill is region-specific or provide an opt-in choice for language. This can violate language/locale policy when users are not given a choice of interface language.

Content

No source excerpt is available for this finding.