Back to skill

Security audit

TikTok And Reels Script Writer

Security checks for vulnerabilities and agentic risk

Overview

This is a prompt-only content writing skill with a supply-chain caution in its README installation command, but no artifact evidence of malicious behavior.

Before installing, consider pinning or verifying the ClawHub installer version instead of relying on `@latest`. Once installed, the skill itself is a prompt-only script-writing helper and does not ask for sensitive access.

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

Unpinned npm Package Execution Through npx

Content
View full analysis

Vulnerability Details

File Location: README.md, line 43
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: Medium

Vulnerable Code:

bash
npx clawhub@latest install tetsuakira-vk/tiktok-script-writer

Technical Analysis

The documented installation command instructs users to execute the mutable latest release of the third-party clawhub npm package. When the package is not already available locally, npx can retrieve it from the configured npm registry and execute its CLI code under the installing user's account.

The latest tag is not immutable and can be reassigned to a different release after this project has been audited. The project does not provide an exact reviewed version, lockfile, package integrity hash, or other mechanism that allows users to verify that the downloaded package is the version expected by the project author.

This does not establish that the current clawhub package is malicious. The risk arises if the package, its publisher account, the package distribution channel, or the mutable tag is compromised or changed unexpectedly.

Attack Path

  1. An attacker compromises the package publisher account, package release process, or relevant registry distribution channel.
  2. The attacker publishes a malicious package version and causes the latest tag to resolve to it.
  3. A user follows the installation instructions and runs the documented npx clawhub@latest ... command.
  4. npx downloads and executes the attacker-controlled package code.
  5. That code runs with the privileges and environmental access of the user who launched the command.

Impact Assessment

Successful exploitation could permit arbitrary code execution with the installing user's privileges. Depending on that user's permissions and environment, the malicious package could read or alter user-accessible files, inspect environment variables and credentials, modify development ...[truncated 375 chars]

Remediation
View remediation

Remediation Suggestions

  1. Replace @latest with an exact package version that has been reviewed, for example:
    bash
    npx clawhub@X.Y.Z install tetsuakira-vk/tiktok-script-writer
    
  2. Document the expected npm registry and package publisher so users can detect registry or namespace substitution.
  3. Publish and verify package integrity metadata or checksums where the installation workflow supports them.
  4. Review version updates before changing the documented pin, and use automated dependency monitoring to identify compromised or vulnerable releases.
  5. Where practical, recommend running installation in a least-privileged or isolated environment and avoiding administrator or root 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 (1)

Rp1

Medium
Category
MCP Rug Pull
Confidence
97% confidence
Finding

The README instructs users to execute npx clawhub@latest install ..., which fetches and runs the latest published package version at install time rather than a reviewed, pinned release. If the upstream package is compromised, typosquatted, or a malicious update is published, users could execute attacker-controlled code on their system during installation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.