ClawHub
Back to skill

Security audit

Timestamp Tool

Security checks for vulnerabilities and agentic risk

Overview

This is a small local timestamp utility with documentation and behavior mismatches, but no evidence of malicious or high-impact activity.

This skill appears safe to install from a security perspective, but users should verify its command syntax and timestamp output before relying on it for logs, audits, or automation because the README and script behavior do not fully agree.

A.I.G

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • 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
Findings (1)

Tp4

High
Category
MCP Tool Poisoning
Confidence
87% confidence
Finding

The code mostly aligns with a timestamp/date utility and supports date arithmetic via add/subtract offsets. However, there is a material behavior mismatch: the '--to-unix' option suggests converting a human-readable date into a Unix timestamp, but the implementation only parses the input date into a datetime object and then prints it using strftime, producing another human-readable string rather than a Unix timestamp. This means one half of the declared bidirectional conversion is not actually implemented. The current-time feature is a minor undeclared capability, but the main reason for mismatch is the inaccurate representation of date-to-Unix conversion behavior.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.