Back to skill

Security audit

Korean Daily Drill

Security checks for vulnerabilities and agentic risk

Overview

This is a text-only Korean study skill whose behavior matches its stated purpose, with a normal but mutable installer command users should treat cautiously.

This skill appears safe for normal use as a Korean practice prompt. Before installing, consider whether you are comfortable running a mutable `npx ...@latest` installer; using a pinned ClawHub installer version or installing from a trusted environment would reduce supply-chain exposure.

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

Unpinned npm Package Execution in Installation Instructions

Content
View full analysis

Vulnerability Details

File Location: README.md:44
Vulnerability Type: T08: Insecure Dependencies
Risk Level: Medium

Vulnerable Code

bash
npx clawhub@latest install tetsuakira-vk/korean-daily-drill

Technical Analysis

The installation command directs npx to download and execute the package associated with the mutable latest tag. Because the documentation does not specify an exact reviewed version or integrity value, the code executed by users can change after this skill has been audited.

The repository does not include the installer source, a dependency lockfile, or package integrity metadata that would allow the remotely supplied CLI implementation to be verified against the audited artifact. If the npm package, publisher account, release process, or mutable tag is compromised, malicious package or lifecycle code could execute during installation.

This is a supply-chain exposure rather than evidence that the current clawhub package is malicious.

Attack Path

  1. An attacker compromises the clawhub publisher account, package release process, npm distribution channel, or another component capable of controlling the latest release.
  2. The attacker publishes a malicious package version and assigns or causes the latest tag to resolve to it.
  3. A user follows the documented installation command.
  4. npx retrieves the attacker-controlled version because the command explicitly requests @latest.
  5. The downloaded CLI or applicable package lifecycle code executes with the permissions of the user running the command.
  6. The malicious code can access resources available to that user before, during, or instead of installing the intended skill.

Impact Assessment

Successful exploitation could provide arbitrary code execution with the privileges of the invoking user. Depending on the local environment, the attacker could read or modify user-accessible files, steal credentials exposed to the process, access configu ...[truncated 376 chars]

Remediation
View remediation

Remediation Suggestions

  1. Replace the mutable @latest reference with an exact version that has been reviewed:
    bash
    npx clawhub@X.Y.Z install tetsuakira-vk/korean-daily-drill
    
  2. Document the expected npm registry and package publisher so users can detect dependency-confusion or source-substitution issues.
  3. Publish and document the expected package integrity digest or signed provenance information, and provide a verification procedure before execution.
  4. Update the pinned version only after reviewing the new release and its transitive dependencies.
  5. Where practical, install dependencies through a lockfile-backed workflow and use npm ci to enforce resolved versions and integrity metadata.
  6. Recommend executing installation with an unprivileged account and without unnecessary credentials in the environment.
  7. Consider offering a non-executing download and verification workflow so users can inspect the package before running its installer.
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 (2)

Rp1

Medium
Category
MCP Rug Pull
Confidence
93% confidence
Finding

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

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
86% confidence
Finding

The skill is presented as a Korean practice tool and the usage guidance assumes Korean-only interaction, but the document does not state that the user may choose the explanation or interface language. This can be a language/locale policy concern because it implicitly forces a specific language without explicit opt-in or alternatives.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.