ClawHub
Back to skill

Security audit

Timestamp Converter

Security checks for vulnerabilities and agentic risk

Overview

The skill is a simple timestamp conversion reference with no hidden execution or sensitive access; its only notable issue is an unnecessary unpinned optional dependency instruction.

This skill is reasonable to install for timestamp conversion help. Prefer Python 3.9 or newer with the built-in `zoneinfo` module, and avoid running the optional `pip install pytz` command unless legacy `pytz` support is specifically needed from a trusted package index.

A.I.G

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

Note
Location
SKILL.md:166
Finding

Unnecessary and Unpinned Third-Party Dependency Installation

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 166-170
Vulnerability Type: Unpinned third-party dependency and avoidable supply-chain exposure
Risk Level: Low

bash
## Dependencies

```bash
pip install pytz
text

### Technical Analysis

The documentation instructs users to install `pytz` without specifying an exact version or verifying package hashes. However, the provided implementation uses Python's built-in `zoneinfo` module and does not import or otherwise require `pytz`.

Installing an unpinned and unused dependency unnecessarily expands the project's supply-chain attack surface. Package resolution can change over time, and installation may execute package build or installation hooks with the privileges of the invoking user. No evidence was found that the legitimate `pytz` package is malicious; the risk arises from avoidable installation and the absence of version and integrity controls.

### Attack Path

1. A user follows the documented dependency instructions.
2. `pip` resolves `pytz` from the user's configured package index without an exact version or hash requirement.
3. If the configured index, package account, network path, or resolved distribution is compromised, attacker-controlled package content may be downloaded.
4. Package installation or build hooks execute under the invoking user's account.
5. Attacker-controlled code could consequently access or modify resources available to that account.

This path requires an upstream package, repository, distribution, or package-resolution compromise; the audited project itself does not provide or retrieve a known malicious payload.

### Impact Assessment

Exploitation could execute code with the privileges of the user running `pip`. Potential scope includes that user's files, environment variables, credentials accessible to the process, and writable Python environments. Administrative impact would occur only if the installation command
...[truncated 144 chars]
Remediation
View remediation

Remediation Suggestions

  1. Remove the pip install pytz instruction because the examples use the standard-library zoneinfo module.
  2. State that Python 3.9 or later is required for the documented implementation.
  3. If support for older Python releases genuinely requires pytz, declare an audited exact version in a dependency file rather than using an unconstrained installation command.
  4. Use hash verification, such as pip install --require-hashes -r requirements.txt, and record approved distribution hashes.
  5. Install dependencies only from a trusted package index and avoid running package installation with administrative privileges.
  6. Add automated dependency review and vulnerability monitoring if a third-party dependency is retained.

SkillSpector

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