ClawHub
Back to skill

Security audit

cooking-timer

Security checks for vulnerabilities and agentic risk

Overview

This kitchen timer skill is very small, but it asks for an unexplained API key and points to a missing timer script, so it should be reviewed before installation.

Review this skill before installing. It does not include the script it tells the agent to run, and you should not provide a TIMER_API_KEY unless the publisher clearly explains what service receives it, why it is needed, what permissions it has, and how it is protected.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The activation guidance is overly broad for a narrowly scoped cooking timer, especially phrases like 'Automating timer tasks' and 'Food operations,' which could cause the skill to be invoked in contexts beyond a harmless timer function. Overbroad triggering increases the chance of unintended execution and, combined with the unexplained API-key requirement, makes misuse or unnecessary credential exposure more likely.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

A simple kitchen timer should not normally require an external API key, so documenting a required secret without explaining the need is suspicious and expands the attack surface unnecessarily. This can mislead users into provisioning credentials to an untrusted or unnecessary backend, enabling secret collection, external telemetry, or misuse of user accounts.

Content

No source excerpt is available for this finding.